| 1 |
On 13-10-2010 11:21:08 +0200, Al wrote: |
| 2 |
> > I just noticed that bootstrapping on Solaris 64-bits breaks with |
| 3 |
> > binutils, because it happens to find libiberty.a from /usr/sfw/64 |
| 4 |
> > instead of its own internal built in copy. |
| 5 |
> > |
| 6 |
> > I'm not yet sure how to fix it properly, but for now, I applied this |
| 7 |
> > hack/workaround in step 1.7: |
| 8 |
> > |
| 9 |
> > env LDFLAGS="-L$EPREFIX/usr/lib -R$EPREFIX/usr/lib -L$EPREFIX/lib -R$EPREFIX/lib" emerge --oneshot --nodeps binutils |
| 10 |
> > |
| 11 |
> > this worked for me to get binutils built. gcc seems to the next to |
| 12 |
> > break for the same reasons. So you'll also need |
| 13 |
> > |
| 14 |
> > env LDFLAGS="-L$EPREFIX/usr/lib -R$EPREFIX/usr/lib -L$EPREFIX/lib -R$EPREFIX/lib" emerge --oneshot --nodeps "=gcc-4.2*" |
| 15 |
> |
| 16 |
> Hm, strange. |
| 17 |
> |
| 18 |
> 1.) IMHO bootstrap-prefix.sh writes the same LDFLAGS to make.defaults. |
| 19 |
> Why don't they take effect? |
| 20 |
|
| 21 |
For Solaris, x64 bits it writes many more flags. But I already found my |
| 22 |
previous solution wasn't the right one. Follow up mail coming. |
| 23 |
|
| 24 |
> 2.) Why does this issue only occur for two programs? It's always the |
| 25 |
> same linker, isn't it? |
| 26 |
|
| 27 |
Because only binutils provides libiberty, and hence gets this conflict |
| 28 |
with finding the wrong libiberty on the host system. |
| 29 |
|
| 30 |
I think gcc doesn't need any workarounds, I'm testing that now. |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Fabian Groffen |
| 35 |
Gentoo on a different level |
Archives