gdm-2.4.1.4 not launching

Joe Marcus Clarke marcus at marcuscom.com
Sun May 11 09:42:15 PDT 2003


On Sun, 2003-05-11 at 09:02, Timur I. Bakeyev wrote:
> On Sun, May 11, 2003 at 02:14:55AM -0400, Joe Marcus Clarke wrote:
> > On Sun, 2003-05-11 at 00:44, Glenn Johnson wrote:
> > > > >
> > > > > Well, version 2.4.1.3 works just fine.  I have that version
> > > > > installed now.  It seems like most of the differences, other than
> > > > > the language support, are in the Makefiles and configure scripts.
> > > > > Something must be getting built incorrectly for version 2.4.1.4.
> > > >
> > > > The attached patch to ltmain.sh gets gdm-2.4.1.4 working for me.
> > > 
> > Glenn, I owe you a bottle of something.  This patch not only fixes gdm,
> > but nautilus and [maybe] bonobo as well.  This crept in, and is only
> > applicable to -STABLE.  -CURRENT _should_ have libc_r linked in.
> 
> Thanks Glenn for the fix! I spend half of Sunday incrementally applying
> patches to 2.4.1.3 to make it 2.4.1.4 and reached the stage, where only
> changes in libtool and configure were not applied and the beast was still
> working :(). So you saved my other half of the day from investigation :)

Try doing that with nautilus which is what I was doing.  I had applied
all the patches to get from 2.2.3 to 2.3.1, but it was _still_ failing. 
I was about to look at LDFLAGS, but I was still a ways off from
ltmain.sh.

> 
> As a side help - can someone explain me, what is this mess with -lc_r and
> -pthread is all about? What should be used with wich version of FreeBSD?

In -STABLE, you may notice that all of functions in libc are also in
libc_r.  libc_r contains thread-safe versions.  If you link both libc
and libc_r into a binary in -STABLE, you get symbol collisions, and bad
things can happen.  At some point early in 5.x -CURRENT development,
libc was made thread-safe, and only the POSIX thread API was put into
libc_r.  Therefore, you can now safely link both libc and libc_r into
binaries in -CURRENT.

-pthread is handled specially by the linker.  It knows where it can and
where it can't link libc_r (e.g. shared libraries).  However, in
-CURRENT, these restrictions have now been lessened, so passing -lc_r
directly is now okay.  Note how I modified Glenn's patch to exclude
-lc_r from the linker in freebsd4*.  This should really be necessary as
${PTHREAD_LIBS} should always be -pthread on -STABLE.

Hope that clarifies things for you.

Joe

> 
> Thanks a lot,
> 	    Timur.
-- 
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20030511/5b04dba7/attachment.bin


More information about the freebsd-gnome mailing list