From owner-freebsd-gnome@FreeBSD.ORG Sun May 11 09:42:15 2003 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7392D37B404 for ; Sun, 11 May 2003 09:42:15 -0700 (PDT) Received: from ms-smtp-02.southeast.rr.com (ms-smtp-02.southeast.rr.com [24.93.67.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1278943F93 for ; Sun, 11 May 2003 09:42:14 -0700 (PDT) (envelope-from marcus@marcuscom.com) Received: from mail3.nc.rr.com (fe3 [24.93.67.50])h4BGdqgs004269; Sun, 11 May 2003 12:39:52 -0400 (EDT) Received: from creme-brulee.marcuscom.com ([66.57.17.158]) by mail3.nc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); Sun, 11 May 2003 12:39:13 -0400 Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) h4BGc4aa021205; Sun, 11 May 2003 12:38:04 -0400 (EDT) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: creme-brulee.marcuscom.com: shumai.marcuscom.com [192.168.1.4] didn't use HELO protocol From: Joe Marcus Clarke To: "Timur I. Bakeyev" In-Reply-To: <20030511150225.A84789@bat.ru> References: <20030509160612.GA19809@node1.cluster.srrc.usda.gov> <1052500047.313.14.camel@gyros> <20030509172845.GA76544@node1.cluster.srrc.usda.gov> <1052502107.313.24.camel@gyros> <20030510064319.GC36282@gforce.johnson.home> <20030511044052.GA68086@gforce.johnson.home> <20030511044457.GA68161@gforce.johnson.home> <1052633694.98015.38.camel@shumai.marcuscom.com> <20030511150225.A84789@bat.ru> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-c9b3dx2NcuKyu4bSQfO2" Organization: MarcusCom, Inc. Message-Id: <1052671323.6810.10.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.3.3 (Preview Release) Date: 11 May 2003 12:42:03 -0400 X-Spam-Status: No, hits=-39.4 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE_2, QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,REFERENCES, REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: FreeBSD GNOME Users cc: Glenn Johnson Subject: Re: gdm-2.4.1.4 not launching X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2003 16:42:15 -0000 --=-c9b3dx2NcuKyu4bSQfO2 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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. > > >=20 > > 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. >=20 > 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.=20 I was about to look at LDFLAGS, but I was still a ways off from ltmain.sh. >=20 > 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 >=20 > Thanks a lot, > Timur. --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-c9b3dx2NcuKyu4bSQfO2 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQA+vn1bb2iPiv4Uz4cRAk3FAJ0ZY3sLXwZY8n9I0cRFFzB3QFlaTwCgjaP4 jwAOwXx70WHnlpW+YsgAbJA= =2WJh -----END PGP SIGNATURE----- --=-c9b3dx2NcuKyu4bSQfO2--