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: Joris van der Hoeven <address@hidden>
  • To: address@hidden
  • Subject: Re: [TeXmacs] Fix to libc problem?
  • Date: Wed, 2 Aug 2006 23:58:10 +0200

On Wed, Aug 02, 2006 at 08:19:53PM +0200, Ingolf Schäfer wrote:
> 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

Thanks for the info.

> 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.

After some hacking, I found out that the problem comes from Guile and
more precisely from the call to 'cuserid' in line 28 of

$TEXMACS_PATH/progs/link/locus-edit.scm (statically linked)
/usr/share/TeXmacs/progs/link/locus-edit.scm (rpm)

If you replace

(if (defined? 'cuserid) (base256->number (cuserid)) 0)

by 0 in this line, then everything is likely to work fine.
Please let me know if this fixes the problem for all of you.

Best wishes, Joris



Archive powered by MHonArc 2.6.19.

Top of Page