| View previous topic :: View next topic |
| Author |
Message |
rjw8703
Apprentice
Joined: 14 Aug 2004
Posts: 246
Location: Auburn, Al
|
 Posted: Tue Jun 17, 2008 11:00 pm Post subject: I need to down grade glibc 2.8 |
 |
|
I need to down grade glibc. I found a way to do this in the wiki, but I don't know how to implement this line | Code: | | Add (/usr/local/glibc/lib:/usr/local/glibc/lib64:/usr/local/glibc/usr/lib64:/usr/local/glibc/lib32:/usr/local/glibc/usr/lib32) to your $LDPATH |
The URL for the wiki is http://gentoo-wiki.com/HOWTO_downgrade_glibc Could someone show me how to do this? Thanks in advance. |
|
| Back to top |
|
 |
tarpman
Veteran
Joined: 04 Nov 2004
Posts: 1083
Location: Victoria, BC, Canada
|
| Posted: Wed Jun 18, 2008 2:06 am Post subject: |
|
|
Create a file in /etc/env.d that follows the naming convention of the existing files there like so:
| /etc/env.d/99local: | | LDPATH=/usr/local/glibc/lib:/usr/local/glibc/lib64:/usr/local/glibc/usr/lib64:/usr/local/glibc/lib32:/usr/local/glibc/usr/lib32 |
and then env-update && . /etc/profile. But seriously, what is so bad about the new glibc that you're willing to risk almost certain destruction of your system to get rid of it? If you do intend to go ahead with this, I can't stress enough - make a backup first.
_________________
Saving the world, one kilobyte at a time. |
|
| Back to top |
|
|
rjw8703
Apprentice
Joined: 14 Aug 2004
Posts: 246
Location: Auburn, Al
|
| Posted: Wed Jun 18, 2008 4:38 am Post subject: |
|
|
Well that didn't work. I created a file called 99local in /etc/env.d then ran | Code: | | LDPATH=/usr/local/glibc/lib:/usr/local/glibc/lib64:/usr/local/glibc/usr/lib64:/usr/local/glibc/lib32:/usr/local/glibc/usr/lib32 |
Then did
And finally | Code: | | source /etc/profile |
Then I did an emerge glibc and got the same result of
| Code: | >>> Emerging (1 of 1) sys-libs/glibc-2.7-r2 to /
* glibc-2.7-patches-1.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* glibc-ports-2.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* glibc-2.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* glibc-libidn-2.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
* checking glibc-2.7.tar.bz2 ;-) ... [ ok ]
* checking glibc-libidn-2.7.tar.bz2 ;-) ... [ ok ]
* checking glibc-ports-2.7.tar.bz2 ;-) ... [ ok ]
* checking glibc-2.7-patches-1.7.tar.bz2 ;-) ... [ ok ]
* Sanity check to keep you from breaking your system:
* Downgrading glibc is not supported and a sure way to destruction
*
* ERROR: sys-libs/glibc-2.7-r2 failed.
* Call stack:
* ebuild.sh, line 49: Called pkg_setup
* glibc-2.7-r2.ebuild, line 198: Called die
* The specific snippet of code:
* die "aborting to save your system"
* The die message:
* aborting to save your system
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/log/portage/sys-libs:glibc-2.7-r2:20080618-041250.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.7-r2/temp/die.env'.
*
* Messages for package sys-libs/glibc-2.7-r2:
* Sanity check to keep you from breaking your system:
* Downgrading glibc is not supported and a sure way to destruction
*
* ERROR: sys-libs/glibc-2.7-r2 failed.
* Call stack:
* ebuild.sh, line 49: Called pkg_setup
* glibc-2.7-r2.ebuild, line 198: Called die
* The specific snippet of code:
* die "aborting to save your system"
* The die message:
* aborting to save your system
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/log/portage/sys-libs:glibc-2.7-r2:20080618-041250.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.7-r2/temp/die.env'.
*
|
There were too many packages broken by the combination of gcc4.3.1 and glibc2.8, especially math packages and acml, that I could no longer use gentoo. It's been 3+ years since I've been burned this bad by a gentoo upgrade. Anymore help would be a great help.
P.S.
I'm not exactly sure what system setting and files I need to backup. I have all of my math stuff as well as /etc/portage, fstab, xorg.conf, and make.conf copied to another directory. Any other ideas would be welcomed. |
|
| Back to top |
|
|
Genone
Retired Dev
Joined: 14 Mar 2003
Posts: 9565
Location: beyond the rim
|
| Posted: Wed Jun 18, 2008 6:09 am Post subject: |
|
|
| Short version: you'll have to modify the ebuild to get remove the downgrade check, there is no override switch. (the wiki article only makes sense when you're going to install another glibc version in parallel in /usr/local). |
|
| Back to top |
|
|
rjw8703
Apprentice
Joined: 14 Aug 2004
Posts: 246
Location: Auburn, Al
|
| Posted: Wed Jun 18, 2008 3:11 pm Post subject: |
|
|
| Rats. That means I need to do a full reinstall. I was sure hoping I didn't have to do that. Thanks much for the help. I appreciate it. |
|
| Back to top |
|
|
desultory
Bodhisattva
Joined: 04 Nov 2005
Posts: 9410
|
| Posted: Thu Jun 19, 2008 2:15 am Post subject: |
|
|
The modifications mentioned by Genone are not complex.
| Before: | pkg_setup() {
# prevent native builds from downgrading ... maybe update to allow people
# to change between diff -r versions ? (2.3.6-r4 -> 2.3.6-r2)
if [[ ${ROOT} == "/" ]] && [[ ${CBUILD} == ${CHOST} ]] && [[ ${CHOST} == ${CTARGET} ]] ; then
if has_version '>'${CATEGORY}/${PF} ; then
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"
fi
fi
|
| After: | pkg_setup() {
# prevent native builds from downgrading ... maybe update to allow people
# to change between diff -r versions ? (2.3.6-r4 -> 2.3.6-r2)
# if [[ ${ROOT} == "/" ]] && [[ ${CBUILD} == ${CHOST} ]] && [[ ${CHOST} == ${CTARGET} ]] ; then
# if has_version '>'${CATEGORY}/${PF} ; then
# 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"
# fi
# fi
|
Of course, that does not mean that there are no other modifications required nor would the resulting operation be safe or officially supported, so any bugs about it would be closed as being invalid, whether it works or not. |
|
| Back to top |
|
|
Peha
n00b
Joined: 07 Aug 2002
Posts: 37
|
|
| Back to top |
|
|
|
Portage & Programming
