wireless wrote:
* /var/log/elog//cross-armv4t-maverick-linux-gnueabi-gcc-stage2.log
The output from the log above would be useful... I have a feeling that they might be due to your USE flags.
The failure is most likely occurring when trying to create the fortran compiler in stage2.
I'm not sure what I missed?
http://perpetual-notion.blogspot.com/2008/02/maverick-crunch-eabi-support-for.html mkdir -p /usr/local/portage/maverick_overlay && SRV="http://vaiprime.visibleassets.com"; \ LOC="~cfriedt/overlays/maverick.tar.bz2" \ wget -O - ${SRV}/${LOC} | \ tar xpjf - -C /usr/local/portage/maverick_overlay && PORTDIR_OVERLAY="/usr/local/portage/crossdev_overlay \ /usr/local/portage/maverick_overlay" \ ECONF_EXTRA="--disable-nls --enable-shared \ --with-system-zlib --without-included-gettext \ --enable-threads=posix --enable-clocale=gnu \ --with-fpu=maverick --with-float-abi=softfp \ --with-cpu=ep9312 --enable-languages=c,c++" \ USE="-gcj -gtk -fortran -mudflap" \ crossdev -S \ --l 2.5-r4 --g 4.1.2 --b 2.17-r1 \ armv4t-maverick-linux-gnueabi
NO doubt I did not add these patches. Could you explain in a little bit more detail, just how to perform any additional patches?
The patches are included already in my ebuild & overlay. Chris -- [email protected] mailing list
