From owner-freebsd-gnome Sat Mar 15 10:26: 4 2003 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 4C8B437B404 for ; Sat, 15 Mar 2003 10:26:00 -0800 (PST) Received: from creme-brulee.marcuscom.com (rdu57-17-158.nc.rr.com [66.57.17.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A88543FBD for ; Sat, 15 Mar 2003 10:25:59 -0800 (PST) (envelope-from marcus@marcuscom.com) Received: from [192.168.1.4] (shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.12.8/8.12.8) with ESMTP id h2FIP5rI059947; Sat, 15 Mar 2003 13:25:05 -0500 (EST) (envelope-from marcus@marcuscom.com) Subject: Re: From: Joe Marcus Clarke To: Peter Seipel Cc: FreeBSD GNOME Users In-Reply-To: <1347.192.168.0.3.1047747029.squirrel@192.168.0.4> References: <1347.192.168.0.3.1047747029.squirrel@192.168.0.4> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-PZSQncabd28GLkI7Jtrd" Organization: MarcusCom, Inc. Message-Id: <1047752751.81982.15.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 15 Mar 2003 13:25:52 -0500 X-Spam-Status: No, hits=-38.6 required=5.0 tests=BAYES_00,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE_2, QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Sender: owner-freebsd-gnome@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-PZSQncabd28GLkI7Jtrd Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Top posting since this error is starting to become a common scene. This is bizarre. You're now the third reporter of this problem.=20 However, bento nor I have been able to reproduce it. I'm at a loss to find a common thread that could explain why this is happening. I'm afraid, the only way I'm going to get to the bottom of this is to get remote access to a machine experiencing the problem. Do you think you can set me up with an account? Joe=20 On Sat, 2003-03-15 at 11:50, Peter Seipel wrote: > "Configure" asked me to send this after a "make install" of the > XFree86-4-Server faild. >=20 > checking for BSD-compatible nm... (cached) /usr/bin/nm -B > checking whether ln -s works... (cached) yes > updating cache .././config.cache > /ltconfig: Can't open /ltconfig: No such file or directory > configure: error: libtool configure failed > configure: error: ./configure failed for glib-1.2.8 > =3D=3D=3D> Script "configure" failed unexpectedly. > Please report the problem to gnome@FreeBSD.org [maintainer] and att= ach > the "/usr/ports/devel/pkgconfig/work/pkgconfig-0.15.0/config.log" > including the output of the failure of your make command. Also, it > might > be a good idea to provide an overview of all packages installed on = your > system (e.g. an `ls /var/db/pkg`). > *** Error code 1 >=20 > Stop in /usr/ports/devel/pkgconfig. > *** Error code 1 >=20 > Stop in /usr/ports/x11-fonts/fontconfig. > *** Error code 1 >=20 > Stop in /usr/ports/x11/XFree86-4-libraries. > *** Error code 1 >=20 > Stop in /usr/ports/x11-servers/XFree86-4-Server. >=20 > ------------------------------------------------------------ > $ls /var/db/pkg > cvsup-without-gui-16.1f gmake-3.79.1_3 libtool-1.3.4_4 > ezm3-1.0 imake-4.3.0 linux_base-7.1_1 > ------------------------------------------------------------ >=20 > $cat /usr/ports/devel/pkgconfig/work/pkgconfig-0.15.0/config.log > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. >=20 > configure:732: checking for a BSD compatible install > configure:785: checking whether build environment is sane > configure:842: checking whether gmake sets ${MAKE} > configure:888: checking for working aclocal-1.4 > configure:901: checking for working autoconf > configure:914: checking for working automake-1.4 > configure:927: checking for working autoheader > configure:940: checking for working makeinfo > configure:954: checking whether to enable maintainer-specific portions of > Makefiles > configure:993: checking for Cygwin environment > configure:1026: checking for mingw32 environment > configure:1055: checking how to run the C preprocessor > configure:1210: checking host system type > configure:1231: checking build system type > configure:1251: checking for gcc > configure:1364: checking whether the C compiler (cc -O -pipe ) works > configure:1380: cc -o conftest -O -pipe conftest.c 1>&5 > configure:1406: checking whether the C compiler (cc -O -pipe ) is a > cross-compiler > configure:1411: checking whether we are using GNU C > configure:1439: checking whether cc accepts -g > configure:1482: checking for ld used by GCC > configure:1550: checking if the linker (/usr/libexec/elf/ld) is GNU ld > configure:1567: checking for /usr/libexec/elf/ld option to reload object > files > configure:1579: checking for BSD-compatible nm > configure:1617: checking whether ln -s works > configure:1638: checking how to recognise dependant libraries > configure:1821: checking for object suffix > configure:1847: checking for executable suffix > configure:1888: checking command to parse /usr/bin/nm -B output > configure:2071: checking for dlfcn.h > configure:2249: checking for ranlib > configure:2316: checking for strip > configure:2559: checking for objdir > configure:2586: checking for cc option to produce PIC > configure:2738: checking if cc PIC flag -fPIC works > configure:2804: checking if cc static flag -static works > configure:2846: checking if cc supports -c -o file.o > configure:2894: checking if cc supports -c -o file.lo > configure:2962: checking if cc supports -fno-rtti -fno-exceptions > configure:2975: cc -c -O -pipe -fno-rtti -fno-exceptions -c conftest.c=20 > conftest.c 1>&5 > configure:3002: checking whether the linker (/usr/libexec/elf/ld) support= s > shared libraries > configure:3686: checking how to hardcode library paths into programs > configure:3714: checking whether stripping libraries is possible > configure:3728: checking dynamic linker characteristics > configure:4125: checking if libtool supports shared libraries > configure:4129: checking whether to build shared libraries > configure:4152: checking whether to build static libraries > configure:4688: checking whether -lc should be explicitly linked in > configure:5293: checking for gcc > configure:5406: checking whether the C compiler (cc -O -pipe ) works > configure:5422: cc -o conftest -O -pipe conftest.c 1>&5 > configure:5448: checking whether the C compiler (cc -O -pipe ) is a > cross-compiler > configure:5453: checking whether we are using GNU C > configure:5481: checking whether cc accepts -g > configure:5514: checking for Win32 > configure:5580: checking for working alloca.h > configure:5613: checking for alloca > configure:5815: checking for setresuid > configure:5871: checking for dirent.h > configure:5871: checking for unistd.h > configure:5871: checking for sys/wait.h >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-gnome" in the body of the message --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-PZSQncabd28GLkI7Jtrd Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQA+c3Avb2iPiv4Uz4cRAlfrAJ99yK65EHWukI4EhNkij2KNAbcv5gCgk4PR JH3SL5P6q815ghpCTO8fGWg= =X/ly -----END PGP SIGNATURE----- --=-PZSQncabd28GLkI7Jtrd-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message