| 1 |
2009/12/2 Peter Stuge <peter@×××××.se> |
| 2 |
|
| 3 |
> Shinkan wrote: |
| 4 |
> > to compile with given versions of glibc/binutils, to be sure that |
| 5 |
> > some bins will run on my target system. |
| 6 |
> > |
| 7 |
> > 1) Is there any other way to do that without emerging a |
| 8 |
> > cross-compiler on my host ? |
| 9 |
> |
| 10 |
> You could do it for the toolchain, and use eselect to pick which one |
| 11 |
> should be active. For libc, I don't think it's possible. |
| 12 |
> |
| 13 |
> |
| 14 |
In fact I noticed I don't really need cross dev. |
| 15 |
So I just emerged GCC 3.4 (my host is compiled with 4.3), gcc-config |
| 16 |
selected it. |
| 17 |
Would that be sufficient to build my target (by doing emerge |
| 18 |
--root=/mytarget --config-root=/myconfig system) en ensure my target will |
| 19 |
run GCC 3.4 compiled binaries ? |
| 20 |
|
| 21 |
I tested it and emerge failed on some ports because installing them use |
| 22 |
binaries that complain about not finding required versions of "CXXABI" or so |
| 23 |
in libstdc++. |
| 24 |
What could I do to fix that ? |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Pierre. |
| 29 |
"Sometimes when I'm talking, my words can't keep up with my thoughts. I |
| 30 |
wonder why we think faster than we speak. Probably so we can think twice." - |
| 31 |
Bill Watterson |
Archives