On Thursday 30 June 2005 03:10 am, Brian Koropoff wrote: > Mike Frysinger wrote: > >On Friday 24 June 2005 08:19 pm, Brian Koropoff wrote: > >>USE="-* arm" ACCEPT_KEYWORDS=arm CBUILD=i686-pc-linux-gnu > >>CHOST=armeb-unknown-linux-gnu CTARGET=armeb-unknown-linux-gnu > >>ROOT=/image/armeb-unknown-linux-gnu-devimage emerge sys-devel/gcc > > > >this looks correct but what you're trying to do isnt something ive tested > > so i havent gotten around to making sure it works ;) > >-mike > > If I wanted to try to get this to work, where should I start looking? > What part of the ebuild/eclass might be at fault?
all gcc logic is handled in toolchain.eclass now ... nothing should need to be done in the ebuild the functions you should review is gcc_src_compile() and anything it calls (like gcc_do_configure and gcc_do_make) It seems to work just > fine doing a manual configure with the plain gcc source, so it's likely > some patch or idiosyncrasy of the way the ebuild sets up the build. wouldnt be surprised > My > goal is to be able to populate the root fs entirely with portage, so I'm > willing to poke around a bit to try to get it working. that is a goal i'd like to see attainted too :) if you're working on gcc does that binutils cross built just fine for you ? -mike -- [email protected] mailing list
