Date: Wed, 10 Aug 2005 20:43:26 -0400 From: Kris Kennaway <kris@obsecurity.org> To: lukem.freebsd@cse.unsw.edu.au Cc: freebsd-ports@freebsd.org Subject: Re: Building gtk-2.6.9: problem and solution Message-ID: <20050811004326.GA35300@xor.obsecurity.org> In-Reply-To: <Pine.LNX.4.61.0508111013490.8401@wagner.orchestra.cse.unsw.EDU.AU> References: <Pine.LNX.4.61.0508111013490.8401@wagner.orchestra.cse.unsw.EDU.AU>
next in thread | previous in thread | raw e-mail | index | archive | help
--EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 11, 2005 at 10:26:44AM +1000, lukem.freebsd@cse.unsw.edu.au wro= te: > I've been having trouble with portupgrade not succeeding with upgrading= =20 > gtk for a while, and this morning I figured out why. I noticed a lot of= =20 > people with similar compile issues when googling, so I figured one post= =20 > here might save others some time in the future. >=20 > The compile would fail with: > cc -O -pipe -mcpu=3Dpentiumpro -Wall -o timescale timescale.o=20 > -L/usr/local/lib -L/usr/X11R6/lib ./.libs/libpixops.a -lglib-2.0 -liconv= =20 > -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lm -lintl > /usr/local/lib/libgthread-2.0.so: undefined reference to=20 > `pthread_attr_destroy' >=20 > And similar for a bunch of pthread functions. >=20 > Listing the symbols in /usr/local/lib/libgthread-2.0.so using nm showed= =20 > that indeed, they were not defined. >=20 > Anyway, to cut a long story short, if you link with -pthread as well as= =20 > libgthread, things will build properly. >=20 > So, build with "make CFLAGS=3D-pthread" instead of just "make". >=20 > Perhaps a port maintainer would like to make this default behaviour, or= =20 > perhaps my libgthread should have been built differently. >=20 > I tried rebuilding glib-2.6.6 to make sure it wasn't the problem.=20 > Interestingly my AMD-64 box which is also maintained with cvsup and=20 > portupgrade did not encounter the same problem. This sounds weird and should of course not be necessary..probably something else is wrong, but I don't know what it might be. Kris --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC+p8uWry0BWjoQKURAqyhAJ0b3tT7Soay/AYGcg8jeSQJA85iawCeJIUz E2Ko5bjQN8BZVYsulN+5Gs4= =mWAM -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050811004326.GA35300>