Bugzilla Bug 136105

# crossdev -t avr
--------------------------------------------------------------------------------
 * Host Portage ARCH:     amd64
 * Target Portage ARCH:   amd64
 * Target System:         avr
 * Stage:                 3 (C compiler & libc)

 * binutils:              binutils-2.16.1-r2
 * gcc:                   gcc-3.4.6
 * libc:                  avr-libc-[latest]

 * PORTDIR_OVERLAY:       /usr/local/overlays/portage
 * PORT_LOGDIR:           /var/log/portage
 * PKGDIR:                /home/ftp/packages/cross/avr
 * PORTAGE_TMPDIR:        /var/tmp/cross/avr
  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -
 * Forcing the latest versions of binutils-config/gcc-config ...          [ ok
]
 * Log: /var/log/portage/cross-avr-binutils.log
 * Emerging cross-binutils ...                                            [ ok
]
 * Log: /var/log/portage/cross-avr-gcc-stage1.log
 * Emerging cross-gcc-stage1 ...                                          [ ok
]
 * Log: /var/log/portage/cross-avr-avr-libc.log
 * Emerging cross-avr-libc ...

 * avr-libc failed :(
 * If you file a bug, please attach the following logfiles:
 * /var/log/portage/cross-avr-info.log
 * /var/log/portage/cross-avr-avr-libc.log

The log files will be attached in a few minutes.

As reported erroneously in bug# 134738:

Step to obtain a avr-libc emerge success:

crossdev -t avr

building binutils, gcc and then failing avr-libc.

use gcc-config to set avr-3.4.6/vanilla

crossdev -t avr

here you have avr-libc emerged.

It's simply a PATH issue, avr-libc can't find avr-gcc in the PATH, so it fall
back on gcc that fails to produce objects for --target=avr.

Created an attachment (id=88708) [details]
cross-avr-info

I've found the cause of the missing gcc-avr in the path, It was the lack of
eselect-compiler in a fresh system built from stage1. Sorry.