Date: Mon, 21 Mar 2005 14:45:44 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Randy Bush <randy@psg.com> Cc: freebsd gnome <freebsd-gnome@freebsd.org> Subject: Re: problem in config of gnomesystemtools-1.2.0_2 Message-ID: <1111434344.44352.24.camel@shumai.marcuscom.com> In-Reply-To: <16959.9108.850381.48347@roam.psg.com> References: <16959.9108.850381.48347@roam.psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-MZIaZAg7YeX5UsnpqyPj Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2005-03-21 at 11:42 -0800, Randy Bush wrote: > cvsup and -current as of yesterday This looks like a symptom of one trying to upgrade from GNOME 2.8 without using gnome_upgrade.sh. You need to remove the old gnomesystemtools port first. You cannot portupgrade it. Joe >=20 > =3D=3D=3D> Configuring for gnomesystemtools-1.2.0_2 > checking for a BSD-compatible install... /usr/bin/install -c -o root -g w= heel > checking whether build environment is sane... yes > checking whether gmake sets $(MAKE)... yes > checking for working aclocal-1.4... missing > checking for working autoconf... missing > checking for working automake-1.4... missing > checking for working autoheader... missing > checking for working makeinfo... found > checking for intltool >=3D 0.29... 0.33 found > checking for perl... /usr/bin/perl > checking for XML::Parser... ok > checking for iconv... /usr/local/bin/iconv > checking for msgfmt... /usr/local/bin/msgfmt > checking for msgmerge... /usr/local/bin/msgmerge > checking for xgettext... /usr/local/bin/xgettext > checking whether to enable maintainer-specific portions of Makefiles... n= o > checking build system type... i386-portbld-freebsd6.0 > checking host system type... i386-portbld-freebsd6.0 > checking for gcc... cc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables...=20 > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether cc accepts -g... yes > checking for cc option to accept ANSI C... none needed > checking for a sed that does not truncate output... /usr/bin/sed > checking for egrep... grep -E > checking for ld used by cc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for /usr/bin/ld option to reload object files... -r > checking for BSD-compatible nm... /usr/bin/nm -B > checking whether ln -s works... yes > checking how to recognise dependent libraries... pass_all > checking how to run the C preprocessor... cc -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking dlfcn.h usability... yes > checking dlfcn.h presence... yes > checking for dlfcn.h... yes > checking whether we are using the GNU C++ compiler... yes > checking whether c++ accepts -g... yes > checking how to run the C++ preprocessor... c++ -E > checking for g77... no > checking for f77... f77 > checking whether we are using the GNU Fortran 77 compiler... yes > checking whether f77 accepts -g... yes > checking the maximum length of command line arguments... (cached) 262144 > checking command to parse /usr/bin/nm -B output from cc object... ok > checking for objdir... .libs > checking for ar... ar > checking for ranlib... ranlib > checking for strip... strip > checking if cc static flag works... yes > checking if cc supports -fno-rtti -fno-exceptions... no > checking for cc option to produce PIC... -fPIC > checking if cc PIC flag -fPIC works... yes > checking if cc supports -c -o file.o... yes > checking whether the cc linker (/usr/bin/ld) supports shared libraries...= yes > checking whether -lc should be explicitly linked in... yes > checking dynamic linker characteristics... freebsd6.0 ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > configure: creating libtool > appending configuration tag "CXX" to libtool > checking for ld used by c++... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking whether the c++ linker (/usr/bin/ld) supports shared libraries..= . yes > checking for c++ option to produce PIC... -fPIC > checking if c++ PIC flag -fPIC works... yes > checking if c++ supports -c -o file.o... yes > checking whether the c++ linker (/usr/bin/ld) supports shared libraries..= . yes > checking dynamic linker characteristics... freebsd6.0 ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > appending configuration tag "F77" to libtool > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for f77 option to produce PIC... -fPIC > checking if f77 PIC flag -fPIC works... yes > checking if f77 supports -c -o file.o... yes > checking whether the f77 linker (/usr/bin/ld) supports shared libraries..= . yes > checking dynamic linker characteristics... freebsd6.0 ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking for strerror in -lcposix... no > checking for gcc... (cached) cc > checking whether we are using the GNU C compiler... (cached) yes > checking whether cc accepts -g... (cached) yes > checking for cc option to accept ANSI C... (cached) none needed > checking for cc option to accept ANSI C... none needed > checking for ANSI C header files... (cached) yes > checking for a BSD-compatible install... /usr/bin/install -c -o root -g w= heel > checking whether gmake sets $(MAKE)... (cached) yes > checking for glib-genmarshal... /usr/local/bin/glib-genmarshal > checking for su... /usr/bin/su > checking for ssh... /usr/bin/ssh > checking for forkpty in -lutil... yes > checking pty.h usability... no > checking pty.h presence... no > checking for pty.h... no > checking for crypt in -lcrypt... yes > checking crypt.h usability... no > checking crypt.h presence... no > checking for crypt.h... no > checking for pkg-config... /usr/local/bin/pkg-config > checking for > gtk+-2.0 >=3D 2.6.0 > libgnomeui-2.0 >=3D 2.9.0 > libglade-2.0 >=3D 2.4.0 > gconf-2.0 >=3D 2.2.0 > system-tools-backends >=3D 1.1.92 > ... Requested 'system-tools-backends >=3D 1.1.= 92' but v > ersion of gst-backends is 1.0.2 >=20 > configure: error: Library requirements ( > gtk+-2.0 >=3D 2.6.0 > libgnomeui-2.0 >=3D 2.9.0 > libglade-2.0 >=3D 2.4.0 > gconf-2.0 >=3D 2.2.0 > system-tools-backends >=3D 1.1.92 > ) not met; consider adjusting the PKG_CONFIG_P= ATH env > ironment variable if your libraries are in a nonstandard prefix so pkg-co= nfig ca > n find them. > =3D=3D=3D> Script "configure" failed unexpectedly. > Please direct the output of the failure of the make command to a file, an= d > then feed that file to the gnomelogalyzer, available from > http://www.freebsd.org/gnome/gnomelogalyzer.sh, which will diagnose the p= roblem > and suggest a solution. If - and only if - the gnomelogalyzer cannot sol= ve > the problem, report the problem to the FreeBSD GNOME team at gnome@FreeBS= D.org, > and attach > "/usr/ports/sysutils/gnomesystemtools/work/gnome-system-tools-1.2.0/confi= g.log" > and the output of the failure of the make command. Also, it might be a g= ood > idea to provide an overview of all packages installed on your system (e.g= . > an `ls /var/db/pkg`). > *** Error code 1 >=20 > _______________________________________________ > freebsd-gnome@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome > To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org" >=20 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-MZIaZAg7YeX5UsnpqyPj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCPyRnb2iPiv4Uz4cRAmOqAJ9DwIpMxEYMFTyOrAcYoiFGWCMPbQCfRY1F PJ66+RRUxns+qdOu7say2Tc= =wGB+ -----END PGP SIGNATURE----- --=-MZIaZAg7YeX5UsnpqyPj--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1111434344.44352.24.camel>