| View previous topic :: View next topic |
| Author |
Message |
FIy
n00b
Joined: 24 Jun 2005
Posts: 72
Location: Hamburg, Germany
|
 Posted: Thu Nov 17, 2005 10:59 pm Post subject: GRRRR! Hell with dl-close.c !!!! [solved] |
 |
|
Hey there,
it is time for a post. I have been struggeling with this damn error msg:
| Quote: |
dl-close.c:365: _dl_close: Assertion `imap->l_type == lt_loaded || imap->l_opencount > 0' failed.
|
for weeks now and it appears more and more often !
Unfortunately I cannot remember what exactly happend before the first appearance, but the first time I saw this was when I tried to start scribus a while after I used it the last time. Searched the forums a bit but I didn't find a solution, most people seem to get this problem when playing around with amarok or doom3 demo.
But now - and thats a real hell - I took the risk and made an ACCEPT_KEYWORDS="~amd64" emerge gnome for at last getting gnome-2.12. And now this damn error msg appears during emerge pango!? It doesnt matter whether i try the masked pango-1.10.1 or the stable pango-1.8.1.
it comes, again and again and i don't have any idea what it even means!
Any ideas on it?
I read that it could be related to glibc so I just wanted to mention that I am using glibc-2.3.5-r2 with +nptl and +nls useflags..
cheers
Fiy
Last edited by FIy on Sat Nov 19, 2005 2:17 pm; edited 1 time in total |
|
| Back to top |
|
 |
widan
Veteran
Joined: 07 Jun 2005
Posts: 1512
Location: Paris, France
|
| Posted: Fri Nov 18, 2005 1:21 am Post subject: |
|
|
I found a message here on a French Gentoo Users mailing list about someone who had the same problem. He somehow ended up with two different versions of libc installed at the same time, one in /usr/lib and one in /lib... He had those:
| Code: | $ locate libc.so.6
/usr/lib32/libc.so.6
/usr/lib64/libc.so.6
/lib32/libc.so.6
/lib64/libc.so.6 |
That were symlinks to different versions of libc:
| Code: | /usr/lib64/libc.so.6 -> libc-2.3.4.so
/lib64/libc.so.6 -> libc-2.3.5.so |
And removing the /usr/lib64/libc.so.6 link made it work again (but unfortunately, it only worked until ldconfig recreated the symlink...).
So you can check if you have a similar situation. |
|
| Back to top |
|
|
FIy
n00b
Joined: 24 Jun 2005
Posts: 72
Location: Hamburg, Germany
|
| Posted: Sat Nov 19, 2005 2:17 pm Post subject: |
|
|
| ah, thanks for the reply, but the solution was to reemerge glibc with the glibc-compat20 useflag.. |
|
| Back to top |
|
|
ThaMubber
n00b
Joined: 09 Nov 2004
Posts: 44
|
| Posted: Mon Feb 13, 2006 12:19 pm Post subject: |
|
|
i have exactly the same problem.
I can only emerge something when i delete the symlink /usr/lib/libc.so.6.
After emerging something the symlink is automaticaly created and the next emerge fails again.
So my question is howto delete the other glibc version to avoid that problem or how can i avoid the creation of that symlink (libc.so.6)
thanks |
|
| Back to top |
|
|
FIy
n00b
Joined: 24 Jun 2005
Posts: 72
Location: Hamburg, Germany
|
| Posted: Mon Feb 13, 2006 2:11 pm Post subject: |
|
|
| well as i said: the problem completely disapeared after activating the compat-20 useflag and remerging glibc. |
|
| Back to top |
|
|
ThaMubber
n00b
Joined: 09 Nov 2004
Posts: 44
|
| Posted: Mon Feb 13, 2006 3:42 pm Post subject: |
|
|
i re-emerged glibc too.
USE="compat20" emerge glibc
But that can't solve my problem.
edit: ahh mybe i used wrong use flag , i should use "glibc-compat20" right? |
|
| Back to top |
|
|
FIy
n00b
Joined: 24 Jun 2005
Posts: 72
Location: Hamburg, Germany
|
| Posted: Mon Feb 13, 2006 4:10 pm Post subject: |
|
|
| Code: |
# emerge -pv glibc
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] sys-libs/glibc-2.3.5-r2 -build -erandom +glibc-compat20* -glibc-omitfp -hardened -linuxthreads-tls (-multilib) +nls +nptl -nptlonly -pic -profile (-selinux) +userlocales 15,628 kB
|
yes  hope it helps!
cheers fiy |
|
| Back to top |
|
|
ThaMubber
n00b
Joined: 09 Nov 2004
Posts: 44
|
| Posted: Mon Feb 13, 2006 6:02 pm Post subject: |
|
|
ok i checked it now.
i compiled that the right way. so that is not the solution for my problem  |
|
| Back to top |
|
|
|
Gentoo on AMD64
