Skip to Content.
Sympa Menu

texmacs-users - Re: [TeXmacs] Fix to libc problem?

Subject: mailing-list for TeXmacs Users

List archive

Re: [TeXmacs] Fix to libc problem?


Chronological Thread 
  • From: "Ingolf Schäfer" <address@hidden>
  • To: "Joris van der Hoeven" <address@hidden>
  • Cc: address@hidden
  • Subject: Re: [TeXmacs] Fix to libc problem?
  • Date: Wed, 2 Aug 2006 20:19:53 +0200
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=bKUCSVCc13simykywAdV8F9z+2febU3pI2UEfpx6bUwjMK7iVun+AL0K7we/h0f/3MwMSFEnve5YxiVXrSDRnySzbT5VPgUqSS2oQIWuOlzid5Sutm7xXPmxBriWHkbirARLENNJ1tlzA/m832PpJ5Yho1TevAO9aNFGqy7Ch1o=

Hi

2006/8/1, Joris van der Hoeven <address@hidden>:
On Tue, Aug 01, 2006 at 10:31:48AM +0200, Jean BOYABE wrote:
>
> >
> > I really don't understand what is going on and definitely
> > need help from other developers in order to fix this problem.
> > After static linking, I do not even understand how you
> > can get your error message:
> >
> >     [vdhoeven@alcazar src]$ grep libc.so TeXmacs/bin/texmacs.bin
> >     [vdhoeven@alcazar src]$
> >
> > Do you get the same result after a grep (on the texmacs.bin of
> > the most recent binary distribution)?
>
> of course, I get the same result after the grep:
>
> cannot handle file 'libc.so.6' with TLS data

Hmm, I have been searching on the web and found one interesting page in French:

        http://linuxfr.org/~houplaboom/7900.html

Please check whether you have a directory

        /usr/lib/tls

If so, then move it to a safe place

        su -
        mv /usr/lib/tls /usr/lib/tls.bak

and try again. This might work.

Other references to this problem:

        http://articles.involution.com/tls.php
         http://www.nvnews.net/vbulletin/showthread.php?t=10968

I still don't understand whether something is wrong on the machine
on which I build the binaries or on machines running certain
new distributions. Someone can help?

I do not know, if this is help, but I think I know the problem exactly.  With the change of kernels a new thread model (nptl) was used, which has made its way into glibc.

I suppose you are compiling on a kernel 2.4 system with an old glibc. For reasons which I do not fully understand this made statically linked programms incompatible.

cf.
http://www.redhatconfig.com/msg/11988.html
http://lists.ibiblio.org/pipermail/sm-discuss/2003-December/004962.html
http://en.wikipedia.org/wiki/Native_POSIX_Thread_Library

I see to alternatives either have a statically link version for the new kernel ( with nptl ) or do not  statically with  libc. But what puzzles me, is that the problem should have occured 3 years ago for the first time.

Yours,

Ingolf

 

Best wishes, Joris



--
Ingolf Schaefer


Archive powered by MHonArc 2.6.19.

Top of Page