[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Berkeley DB fails creating a new repository, "invalid argument"

From: Enrique Perez-Terron <enrio_at_online.no>
Date: 2004-08-18 00:40:40 CEST

On Tue, 2004-08-17 at 10:21, Max Bowsher wrote:
> Enrique Perez-Terron wrote:
> > There appears to be a solution simply to ensure that the tls version of
> > the library is used, adding /lib/tls and /usr/lib/tls to the top of
> > /etc/ld.so.conf, and running ldconfig.
>
> *BAD* idea. The tls variants are automatically used by the linker iff your
> kernel supports NPTL.

Eh, are you sure that is how it works? The runtime linker in
/lib/ld-2.3.3.so does not contain the string "tls/" while it does
contain the following:

   # strings ld-2.3.3.so | grep lib/
   /lib/
   /usr/lib/
   /lib/libNoVersion.so.1
   This program usually lives in the file `/lib/ld.so', and special directives

The runtime linker is part of the glibc package:

   # rpm -qf /lib/ld-2.3.3.so
   glibc-2.3.3-27

and so, I get the tls version only if I have a glibc that supports tls.
Since the glibc.spec never was updated to make separate versions for
i486 and i586 (never mind K6...), I have a glibc for i386 that does not
support tls even the kernel does for i486 and up.

But all this could be the continued snowballing of the confusion, if I
am misled by to much and uncritical googling....

> You could, in theory, rebuild glibc (ouch!).

Yes. Ouch, ouch.

> Or, you could rebuild db, with --disable-posixmutexes.
> This is likely the easiest option.

I will do that.

Thanks,
Enrique

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 18 00:41:15 2004

This is an archived mail posted to the Subversion Users mailing list.