View previous topic :: View next topic |
Author |
Message |
Naib Watchman
Joined: 21 May 2004 Posts: 6051 Location: Removed by Neddy
|
Posted: Tue Feb 08, 2011 1:14 am Post subject: |
|
|
WOW I am so glad I removed prelink last month... was causing issues with 64bit 3D applications. prelink would be linking in the 32bit libs from nvidia... _________________
Quote: | Removed by Chiitoo |
|
|
Back to top |
|
|
HolgerH n00b
Joined: 02 Mar 2008 Posts: 16
|
Posted: Tue Feb 08, 2011 1:20 am Post subject: |
|
|
SoLoR wrote: | glibc-2.13 also breaks postfix for me...
..
reverting glibc back to 2.12.2 and problem is gone. |
Same here. May I ask how you downgraded? I read the various guides and just like the ebuild safety-check they all contain unhelpful panic warnings without actually saying what the problems are.
I haven't emerged anything since glibc, so is it just a matter of editing the 2.12.2 ebuild to disable the check, updating the manifest & emerging?
thanks. |
|
Back to top |
|
|
rhill Retired Dev
Joined: 22 Oct 2004 Posts: 1629 Location: sk.ca
|
Posted: Tue Feb 08, 2011 5:54 am Post subject: |
|
|
you can run
Code: | ROOT="/../" emerge -av1 =glibc-2.12.2 |
to get around the downgrade check. _________________ by design, by neglect
for a fact or just for effect |
|
Back to top |
|
|
vdracula n00b
Joined: 03 Aug 2004 Posts: 51 Location: NGC 5907
|
Posted: Tue Feb 08, 2011 6:00 am Post subject: |
|
|
After restoring my system back to normal, did a prelink -au.
Since then, everything o.k. here. No problems at all.
One have to be carefull with all kind of optimizations... |
|
Back to top |
|
|
yoshi314 l33t
Joined: 30 Dec 2004 Posts: 850 Location: PL
|
Posted: Tue Feb 08, 2011 7:08 am Post subject: |
|
|
NightMonkey wrote: | Welcome to unstable, everyone. | it's well beyond unstable, in that case.
i can understand an apps failing on unstable, but the whole system ? that stuff belongs to hard masked packages.
whoever is responsible for that critical system component really messed up. _________________ ~amd64
shrink your /usr/portage with squashfs+aufs |
|
Back to top |
|
|
HolgerH n00b
Joined: 02 Mar 2008 Posts: 16
|
Posted: Tue Feb 08, 2011 10:01 am Post subject: |
|
|
dirtyepic wrote: | you can run
Code: | ROOT="/../" emerge -av1 =glibc-2.12.2 |
to get around the downgrade check. |
Nope, didn't work for me. Could be me using zsh though. Anyway just editing the ebuild and rebuilding worked fine, postfix is back up & running. |
|
Back to top |
|
|
FireBurn Apprentice
Joined: 19 Sep 2004 Posts: 170 Location: Edinburgh, UK
|
Posted: Tue Feb 08, 2011 11:31 am Post subject: |
|
|
yoshi314 wrote: | NightMonkey wrote: | Welcome to unstable, everyone. | it's well beyond unstable, in that case.
i can understand an apps failing on unstable, but the whole system ? that stuff belongs to hard masked packages.
whoever is responsible for that critical system component really messed up. |
Considering I gave a heads up to the committer within hours of the ebuild going live I'm angry at the length of time to took for something to be done
I got an email back with in an hour telling me that email wasn't the way to communicate bugs |
|
Back to top |
|
|
Xenoist n00b
Joined: 21 Aug 2002 Posts: 26 Location: EU/DE/NRW/NEUSS
|
Posted: Tue Feb 08, 2011 3:55 pm Post subject: to go back to glibc-2.12.2 use this |
|
|
Sanity check is in /usr/portage/sys-libs/glibc/files/eblits/pkg_setup.eblit
So set # like here:
# eerror "Sanity check to keep you from breaking your system:"
# eerror " Downgrading glibc is not supported and a sure way to destruction"
# die "aborting to save your system"
ebuild /usr/portage/sys-libs/glibc/sys-libs/glibc-2.12.2.ebuild digest
echo "=sys-libs/glibc-2.13*" >> /etc/portage/package.mask
emerge -av1 =sys-libs/glibc-2.12.2
But i think that will be a bad option.
I will try it with complete rebuild on a 64bit environment in chroot.
Don't forget to enable the check again in /usr/portage/sys-libs/glibc/files/eblits/pkg_setup.eblit and do a ebuild /usr/portage/sys-libs/glibc/sys-libs/glibc-2.12.2.ebuild digest. _________________ Once live is to short to learn all, but keep trying it.
"emerge the world" every day!
Last edited by Xenoist on Tue Feb 08, 2011 10:11 pm; edited 1 time in total |
|
Back to top |
|
|
musv Advocate
Joined: 01 Dec 2002 Posts: 3337 Location: de
|
Posted: Tue Feb 08, 2011 7:36 pm Post subject: Re: WARNING: updating to glibc-2.13 w/prelink hoses system |
|
|
Yes, I can confirm this. It's working (the segfaults).
Odysseus wrote: | If you're running a ~ arch, DO NOT update to glibc-2.13 if you have prelink installed!!! It will completely hose your box!!! I just spent several hours trying to recover from this bug https://bugs.gentoo.org/show_bug.cgi?id=353814 |
---> afk for several hours. Downgrading glibc. |
|
Back to top |
|
|
rich0 Developer
Joined: 15 Sep 2002 Posts: 161
|
Posted: Tue Feb 08, 2011 7:39 pm Post subject: |
|
|
FireBurn wrote: |
I got an email back with in an hour telling me that email wasn't the way to communicate bugs |
Well, for a bug of this magnitude i'd probably suggest bugzilla plus email plus irc plus a process server...
Granted devs have day jobs too, but escalating this was not inappropriate... |
|
Back to top |
|
|
musv Advocate
Joined: 01 Dec 2002 Posts: 3337 Location: de
|
Posted: Tue Feb 08, 2011 9:02 pm Post subject: |
|
|
I didn't figure out how to downgrade glibc because of sanity check.
So I deinstalled prelink temporary. I hope there will be a patch soon. |
|
Back to top |
|
|
rhill Retired Dev
Joined: 22 Oct 2004 Posts: 1629 Location: sk.ca
|
Posted: Tue Feb 08, 2011 11:22 pm Post subject: |
|
|
HolgerH wrote: | dirtyepic wrote: | you can run
Code: | ROOT="/../" emerge -av1 =glibc-2.12.2 |
to get around the downgrade check. |
Nope, didn't work for me. Could be me using zsh though. Anyway just editing the ebuild and rebuilding worked fine, postfix is back up & running. |
Me neither actually. I guess portage is smart enough to rewrite it to "/". _________________ by design, by neglect
for a fact or just for effect |
|
Back to top |
|
|
crculver n00b
Joined: 02 Mar 2004 Posts: 17
|
Posted: Wed Feb 09, 2011 1:10 am Post subject: |
|
|
Is there any fix for postfix with this glibc? I've recompiled a fair bit of my system since the glibc upgrade and I'm afraid to revert to the previous version of glibc.
Incidentally, wouldn't finally updating the version of kernel-headers in Portage and then recompiling glibc make for a more reliable system for those running recent kernels? |
|
Back to top |
|
|
Odysseus Apprentice
Joined: 23 Jun 2004 Posts: 250 Location: Miami, FL. I miss San Francisco!!!
|
Posted: Thu Feb 10, 2011 10:37 am Post subject: |
|
|
crculver wrote: | Is there any fix for postfix with this glibc? I've recompiled a fair bit of my system since the glibc upgrade and I'm afraid to revert to the previous version of glibc.
Incidentally, wouldn't finally updating the version of kernel-headers in Portage and then recompiling glibc make for a more reliable system for those running recent kernels? |
Finish recompiling against the new glibc, but make sure that prelink is either disabled or removed from your system. It's far safer to just finish recompiling than downgrading to the previous version (unless you're willing to risk breaking your box). I know I wouldn't risk it myself, despite some of the posts here to the contrary.
Fixing the bugs with this new glibc release is probably one of the highest priorities for the maintainers at the moment. I noticed on bugzilla that they've setup a tracker to focus on eliminating them. So I'm sure that before long we'll either see an update to glibc or to the packages affected by it. Unless you can write code and are willing to contribute the only thing to do is wait and have patience.
Updating the kernel headers only matters if there is a new feature, driver or supported processor in the newer kernel that you need that isn't included in what you have installed. I've gone for well over a year before without updating kernel headers, while updating my kernel sources with each new release, with no negative effects. Where you really run into problems is if you update your headers to a newer version then your kernel sources. I did that once and found I couldn't compile a kernel until I updated my sources.
Most of the time when I see a new kernel header package in portage, I'll mask it until there is a gcc or glibc update, then unmask and recompile my world against both. This way I kill two birds with one stone. Who wants to be constantly recompiling their entire system? Not me.
I hope this helps
Ciao |
|
Back to top |
|
|
asturm Developer
Joined: 05 Apr 2007 Posts: 8936
|
Posted: Thu Feb 10, 2011 6:06 pm Post subject: |
|
|
So far I haven't noticed any problems on my 1250sth packages system, so it seems to be rather safe with the known exceptions. |
|
Back to top |
|
|
Odysseus Apprentice
Joined: 23 Jun 2004 Posts: 250 Location: Miami, FL. I miss San Francisco!!!
|
Posted: Mon Feb 14, 2011 10:51 pm Post subject: |
|
|
Prelink is fixed now in glibc-2.13-r1 as per this bug report https://bugs.gentoo.org/show_bug.cgi?id=353814
I just resynced, updated to the new glibc version, reinstalled and enabled prelink, ran prelink -amR, and all worked as expected. I rebooted my system and it was noticeably faster as was starting KDE on my five year old ~x86 single-core Centrino notebook.
So it appears this has been resolved and I can confirm that things are back to normal now.
The issue appears to have been caused by the omission of this patch that RedHat had included in their build of glibc, that wasn't included in the officially released version. http://sourceware.org/git/?p=glibc.git;a=commit;h=25b3aada
You can read more about it here on the Arch Linux forums https://bugs.archlinux.org/task/22656
So the OP can now mark this thread as "solved" and we can all go back to using prelink as before.
I hope this helps,
Ciao |
|
Back to top |
|
|
Hwoarang Retired Dev
Joined: 24 Feb 2007 Posts: 701 Location: Leeds, UK
|
Posted: Mon Feb 14, 2011 11:18 pm Post subject: |
|
|
Sadly skype is still broken so I had to dowgrade glibc everywhere |
|
Back to top |
|
|
HighOnBonsai Apprentice
Joined: 05 Jan 2004 Posts: 260
|
|
Back to top |
|
|
duderonomy Guru
Joined: 20 Mar 2004 Posts: 349 Location: SF Bay Area
|
Posted: Fri Feb 18, 2011 12:02 pm Post subject: |
|
|
oh man. and I thought this was "just me". lol!
thank you, for this thread...
|
|
Back to top |
|
|
HighOnBonsai Apprentice
Joined: 05 Jan 2004 Posts: 260
|
Posted: Sat Feb 26, 2011 9:10 am Post subject: |
|
|
Kernel 2.6.37-gentoo-r1 now contains the Patch which should fix the issue wie Postfix. Will now upgrade to the new kernel and glibc... Hope it works...
Christopher _________________ Are YOU high - on bonsai? |
|
Back to top |
|
|
iaindb n00b
Joined: 30 Jun 2004 Posts: 19
|
Posted: Thu Mar 03, 2011 2:22 am Post subject: |
|
|
SoLoR wrote: |
im trying to recompile whole system with new glibc to see if it fixed my postfix issue, but it will take a while... |
any luck SoLoR? same issue here! |
|
Back to top |
|
|
HighOnBonsai Apprentice
Joined: 05 Jan 2004 Posts: 260
|
Posted: Thu Mar 03, 2011 6:40 am Post subject: |
|
|
With 2.6.37-gentoo-r1 and glibc-2.13-r1 postfix now works for me.
Christopher _________________ Are YOU high - on bonsai? |
|
Back to top |
|
|
|