Re: libXext fails to build on 9.0-RELEASE/amd64
Thanks! :) Martin Wilke m...@freebsd.org wrote: On Wed, 01 Feb 2012 22:18:31 +0100 1126 mailingli...@elfsechsundzwanzig.de wrote: Hi, Please update your ports tree, we have fixed that. - Martin Hello list! Today, I installed a fresh 9.0-RELEASE/amd64 and wanted to install Xorg. There were no other packages installed before, so Xorg and all it's run- and build-dependencies would be the first. But it fails. The error message reads: ... checking for XEXT... configure: error: Package requirements (xproto = 7.0.13 x11 = 1.1.99.1 xextproto = 7.1.99) were not met: No package 'x11' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XEXT_CFLAGS and XEXT_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. === Script configure failed unexpectedly. Please report the problem to x...@freebsd.org [maintainer] and attach the /usr/portx/x11/libXext/work/libXext-1.3.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 Stop in /usr/ports/x11/libXext. *** Error code 1 After reading this, I asked Google, but it didn't came up with a solution. I updated the ports (portsnap fetch update), but that didn't help either. I tried to install only libXext (make install clean), but that didn't work either. Does anyone knows a solution? As has been asked, I append the output of config.log from the work-directory of libXext. I don't know the right way to do this, but I hope this works. ;) Thanks in advance, 1126! This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by libXext configure 1.3.0, which was generated by GNU Autoconf 2.68. Invocation command line was $ ./configure --disable-specs --without-xmlto --enable-malloc0returnsnull --x-libraries=/usr/local/lib --x-includes=/usr/local/include --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ --build=amd64-portbld-freebsd9.0 ## - ## ## Platform. ## ## - ## hostname = Suse uname -m = amd64 uname -r = 9.0-RELEASE uname -s = FreeBSD uname -v = FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC /usr/bin/uname -p = amd64 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /sbin PATH: /bin PATH: /usr/sbin PATH: /usr/bin PATH: /usr/games PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /root/bin ## --- ## ## Core tests. ## ## --- ## configure:2342: checking for a BSD-compatible install configure:2410: result: /usr/bin/install -c -o root -g wheel configure:2421: checking whether build environment is sane configure:2471: result: yes configure:2612: checking for a thread-safe mkdir -p configure:2651: result: ./install-sh -c -d configure:2664: checking for gawk configure:2694: result: no configure:2664: checking for mawk configure:2694: result: no configure:2664: checking for nawk configure:2680: found /usr/bin/nawk configure:2691: result: nawk configure:2702: checking whether make sets $(MAKE) configure:2724: result: yes configure:2805: checking whether to enable maintainer-specific portions of Makefiles configure:2814: result: no configure:2858: checking build system type configure:2872: result: amd64-portbld-freebsd9.0 configure:2892: checking host system type configure:2905: result: amd64-portbld-freebsd9.0 configure:2946: checking how to print strings configure:2973: result: printf configure:3006: checking for style of include used by make configure:3034: result: GNU configure:3104: checking for gcc configure:3131: result: cc configure:3360: checking for C compiler version configure:3369: cc --version 5 cc (GCC) 4.2.1 20070831 patched [FreeBSD] Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3380: $? = 0 configure:3369: cc -v 5 Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070831 patched [FreeBSD] configure:3380: $? = 0 configure:3369: cc -V 5 cc: '-V' option must have argument configure:3380: $? = 1 configure:3369: cc -qversion 5 cc: unrecognized option '-qversion' cc: No input files specified configure
Re: Possible move back to FreeBSD
Quoting Chris rac...@makeworld.com: Outstanding, thank you. Curious though, how is Gnome looking these days (meaning, is it v3 or 2.x). I have read of the craziness of 3 and the introduction of Unity (albeit that is ubuntu). If 3 is used (or when) I assume it would be closer to what I currently have under Sid (and that would be ok) or even 2.x As far as I can see, it's 2.xx, or to be more precise: http://www.freshports.org/x11/gnome2/ By the way: freshports is a good way to check beforehand what ports are available and in which versions ;) Nonetheless, thanks for the info. I'll have time tomorrow to read up a bit and perhaps next time I post, it'll be under 9 Good luck :) Sent from my HTC. - Reply message - From: Adam Vande More amvandem...@gmail.com Date: Fri, Feb 3, 2012 12:10 am Subject: Possible move back to FreeBSD To: Chris rac...@makeworld.com Cc: freebsd-questions@freebsd.org freebsd-questions@freebsd.org On Thu, Feb 2, 2012 at 11:34 PM, Chris rac...@makeworld.com wrote: I have been using Debian for a few years now (previous BSD user) and I'm considering moving back. Admittedly, I have gotten used to the simplicity of using apt-get to update the system. What will pull me back is if there is an equivalent to use. I do not intend on custom kernels, and I don't intend on using ports (it was the many hours spent keeping the ports tree current along with installed ports). If someone would suggest the material to read and perhaps a synopsis of the process, I would be happy to do the leg work. freebsd-update(1) and pkgng should get you to relative feature parity w/ Debian. However pkgng just entered beta, and likely won't make it into the base system anytime soon. That being said, beta testers are wanted and it's largely functional. /usr/ports/UPDATING is still the standard method along with a ports managment tool of your choice eg portmaster(1). -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
libXext fails to build on 9.0-RELEASE/amd64
Hello list! Today, I installed a fresh 9.0-RELEASE/amd64 and wanted to install Xorg. There were no other packages installed before, so Xorg and all it's run- and build-dependencies would be the first. But it fails. The error message reads: ... checking for XEXT... configure: error: Package requirements (xproto = 7.0.13 x11 = 1.1.99.1 xextproto = 7.1.99) were not met: No package 'x11' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XEXT_CFLAGS and XEXT_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. === Script configure failed unexpectedly. Please report the problem to x...@freebsd.org [maintainer] and attach the /usr/portx/x11/libXext/work/libXext-1.3.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 Stop in /usr/ports/x11/libXext. *** Error code 1 After reading this, I asked Google, but it didn't came up with a solution. I updated the ports (portsnap fetch update), but that didn't help either. I tried to install only libXext (make install clean), but that didn't work either. Does anyone knows a solution? As has been asked, I append the output of config.log from the work-directory of libXext. I don't know the right way to do this, but I hope this works. ;) Thanks in advance, 1126! This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by libXext configure 1.3.0, which was generated by GNU Autoconf 2.68. Invocation command line was $ ./configure --disable-specs --without-xmlto --enable-malloc0returnsnull --x-libraries=/usr/local/lib --x-includes=/usr/local/include --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ --build=amd64-portbld-freebsd9.0 ## - ## ## Platform. ## ## - ## hostname = Suse uname -m = amd64 uname -r = 9.0-RELEASE uname -s = FreeBSD uname -v = FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC /usr/bin/uname -p = amd64 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /sbin PATH: /bin PATH: /usr/sbin PATH: /usr/bin PATH: /usr/games PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /root/bin ## --- ## ## Core tests. ## ## --- ## configure:2342: checking for a BSD-compatible install configure:2410: result: /usr/bin/install -c -o root -g wheel configure:2421: checking whether build environment is sane configure:2471: result: yes configure:2612: checking for a thread-safe mkdir -p configure:2651: result: ./install-sh -c -d configure:2664: checking for gawk configure:2694: result: no configure:2664: checking for mawk configure:2694: result: no configure:2664: checking for nawk configure:2680: found /usr/bin/nawk configure:2691: result: nawk configure:2702: checking whether make sets $(MAKE) configure:2724: result: yes configure:2805: checking whether to enable maintainer-specific portions of Makefiles configure:2814: result: no configure:2858: checking build system type configure:2872: result: amd64-portbld-freebsd9.0 configure:2892: checking host system type configure:2905: result: amd64-portbld-freebsd9.0 configure:2946: checking how to print strings configure:2973: result: printf configure:3006: checking for style of include used by make configure:3034: result: GNU configure:3104: checking for gcc configure:3131: result: cc configure:3360: checking for C compiler version configure:3369: cc --version 5 cc (GCC) 4.2.1 20070831 patched [FreeBSD] Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3380: $? = 0 configure:3369: cc -v 5 Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070831 patched [FreeBSD] configure:3380: $? = 0 configure:3369: cc -V 5 cc: '-V' option must have argument configure:3380: $? = 1 configure:3369: cc -qversion 5 cc: unrecognized option '-qversion' cc: No input files specified configure:3380: $? = 1 configure:3400: checking whether the C compiler works configure:3422: cc -O2 -pipe -fno-strict-aliasing conftest.c 5 configure:3426: $? = 0 configure:3474: result: yes configure:3477: checking for C compiler default output file name configure:3479: result: a.out configure:3485: checking for suffix of executables
