Created attachment 291615 [details] cross-avr-info.log 1) Add an overlay with sys-devel/gcc of equal version to the one in portage. 2) Add /usr/portage to the PORTDIR_OVERLAY variable as the last item. At this point, it one runs `emerge -v --info` and examines the list of "Repositories", priority for "gentoo" (/usr/portage) should be the highest. 3) Run `crossdev -t avr` without having any cross-avr/* ebuilds in place (can be cleaned up via `crossdev -C avr`). 4) "getting sys-devel/gcc from /var/lib/layman/overlayname" occurs rather than the expected "getting sys-devel/gcc from /usr/portage" The following is actual output from a test run: sudo crossdev -t avr ------------------------------------------------------------------------ * crossdev version: 20111018 * Host Portage ARCH: amd64 * Target Portage ARCH: * * Target System: avr * Stage: 4 (C/C++ compiler) * ABIs: default * binutils: binutils-[latest] * gcc: gcc-[latest] * libc: avr-libc-[latest] * CROSSDEV_OVERLAY: /usr/local/portage * PORT_LOGDIR: /var/log/portage * PORTAGE_CONFIGROOT: _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - * getting sys-devel/binutils from /usr/portage * getting sys-devel/gcc from /var/lib/layman/jmesmon * getting dev-embedded/avr-libc from /usr/portage * getting sys-devel/gdb from /usr/portage * getting dev-util/insight from /usr/portage _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - !!! WARNING - Cannot auto-configure CHOST avr
it is impossible to guess at what the user wants. use the --overlay options to tell crossdev explicitly what overlays you want it to utilize.
