View previous topic :: View next topic |
Author |
Message |
VoidMage Watchman
Joined: 14 Oct 2006 Posts: 6196
|
Posted: Fri Jan 31, 2014 5:53 pm Post subject: |
|
|
...and that's where things have fallen apart.
Changing CHOST isn't a trivial thing - I've done it once, but it was quite a few years ago.
There's '/usr/portage/scripts/bootstrap.sh' that should help you, but I don't quite recall how it was supposed to be used.
That wiki article about changing CHOST seems a bit inaccurate, but your system should still be in a recoverable state. |
|
Back to top |
|
|
escravana n00b
Joined: 25 Jan 2014 Posts: 9
|
Posted: Sat Feb 01, 2014 5:02 pm Post subject: |
|
|
Ok, update on the subject.
I used the solution above (compiling zlib with LDSHARED="gcc -shared -Wl,-soname,libz.so.1,--version-script,zlib.map") in order to be able to sucessfuly execute the:
Code: |
emerge binutils gcc glibc
|
That fixed the gcc, and made gcc-config report:
Code: |
[1] i686-pc-linux-gnu-4.7.3 *
[2] i686-pc-linux-gnu-4.7.3-hardenednopie
[3] i686-pc-linux-gnu-4.7.3-hardenednopiessp
[4] i686-pc-linux-gnu-4.7.3-hardenednossp
[5] i686-pc-linux-gnu-4.7.3-vanilla
|
after that, unmerged zlib, removed the LDSAHRED hack (the corresponding /etc/portage/env file), and emerged zlib again, without hacks.. it looks OK now.
So I agree with you, it doesn't look like a zlib bug... maybe I messed up something in changing CHOST process that triggered this.. but the only way I found to get out of this, is the one described above.
Thank you very much for your help.
KR |
|
Back to top |
|
|
The_Great_Sephiroth Veteran
Joined: 03 Oct 2014 Posts: 1602 Location: Fayetteville, NC, USA
|
Posted: Wed Feb 04, 2015 3:20 am Post subject: |
|
|
Just so it is known, I am having this issue on a Celeron 2.80GHz system. I have not modified anything. I used the Gentoo install CD (32bit), partitioned, installed, and began emerging things. I normally first emerge things like ftp, openssh-blacklist, ntp, sudo, etc. Then I emerge the X server (xorg-server and mesa-progs). Then I emerge KDE. During my KDE run the system installs two packages then fails with the SONAME error. I have NOT modified my CHOST or anything. I did modify my USE flags and the CPU_FLAGS_X86 variable, but that is it. This is bone-stock.
The funny thing is, I can go through this exact same process, same order, EVERYTHING on a 64bit system and it works. It just fails to work on my old laptop. I have no clue what to do. _________________ Ever picture systemd as what runs "The Borg"? |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Wed Feb 04, 2015 3:48 am Post subject: |
|
|
The_Great_Sephiroth ...
that does look like the wrong stage3, current-stage3-i486 rather than current-stage3-i686. So, yes, start over, though you could save the portage-snapshot ... which will save some time re-downloading.
best ... khay |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|