1 |
On Thursday 30 June 2005 03:10 am, Brian Koropoff wrote: |
2 |
> Mike Frysinger wrote: |
3 |
> >On Friday 24 June 2005 08:19 pm, Brian Koropoff wrote: |
4 |
> >>USE="-* arm" ACCEPT_KEYWORDS=arm CBUILD=i686-pc-linux-gnu |
5 |
> >>CHOST=armeb-unknown-linux-gnu CTARGET=armeb-unknown-linux-gnu |
6 |
> >>ROOT=/image/armeb-unknown-linux-gnu-devimage emerge sys-devel/gcc |
7 |
> > |
8 |
> >this looks correct but what you're trying to do isnt something ive tested |
9 |
> > so i havent gotten around to making sure it works ;) |
10 |
> >-mike |
11 |
> |
12 |
> If I wanted to try to get this to work, where should I start looking? |
13 |
> What part of the ebuild/eclass might be at fault? |
14 |
|
15 |
all gcc logic is handled in toolchain.eclass now ... nothing should need to be |
16 |
done in the ebuild |
17 |
|
18 |
the functions you should review is gcc_src_compile() and anything it calls |
19 |
(like gcc_do_configure and gcc_do_make) |
20 |
|
21 |
It seems to work just |
22 |
> fine doing a manual configure with the plain gcc source, so it's likely |
23 |
> some patch or idiosyncrasy of the way the ebuild sets up the build. |
24 |
|
25 |
wouldnt be surprised |
26 |
|
27 |
> My |
28 |
> goal is to be able to populate the root fs entirely with portage, so I'm |
29 |
> willing to poke around a bit to try to get it working. |
30 |
|
31 |
that is a goal i'd like to see attainted too :) |
32 |
|
33 |
if you're working on gcc does that binutils cross built just fine for you ? |
34 |
-mike |
35 |
-- |
36 |
gentoo-embedded@g.o mailing list |