Now pkg-config trouble.................Re: startx does not work, startxfce4 does!
Hi, Leslie Try this. Create a file: $HOME/.xinitrc containing: /usr/local/bin/startxfce4 Then give 'startx' another shot. I did all the things suggested here at the list with no success so I decided to clean out and start over. did pkg_delete -f '*' rm -r /usr/ports/distfiles rm -r /usr/local/* Then I installed sysutils/screen ports-mgmt/portupgrade ports-mgmt/portmaster And started installation of x11/xorg But it fails rather quickly with the message below: I've attached the log file and output suggested in the message. One thing that I see is the path to pkg-config is :whereis pkg-config pkg-config: /usr/ports/devel/pkg-config where as on my other machine I've got whereis pkg-config pkg-config: /usr/local/bin/pkg-config /usr/local/man/man1/pkg-config.1.gz /usr/ports/devel/pkg-config I tried /usr/ports/devel/pkg-config:make install clean === Cleaning for gmake-3.81_3 === Cleaning for gettext-0.17_1 === Cleaning for libtool-1.5.26 === Cleaning for libiconv-1.13 === Cleaning for pkg-config-0.23_1 /usr/ports/devel/pkg-config:rehash /usr/ports/devel/pkg-config:whereis pkg-config pkg-config: /usr/ports/devel/pkg-config As you can see in the listing below pkg-config is not listed as installed! That's proberly the source of the install failure, so how do I get pkg-config to install? --- checking dependency style of cc... gcc3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for pkg-config... no checking for XSETROOT... configure: error: The pkg-config script could not be found or is too old. Make sure it is in your PATH or set the PKG_CONFIG environment variable to the full path to pkg-config. Alternatively, you may set the environment variables XSETROOT_CFLAGS and XSETROOT_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. To get pkg-config, see http://www.freedesktop.org/software/pkgconfig. See `config.log' for more details. === Script configure failed unexpectedly. Please report the problem to x...@freebsd.org [maintainer] and attach the /usr/ports/x11/xsetroot/work/xsetroot-1.0.2/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/xsetroot. *** Error code 1 Stop in /usr/ports/x11/xorg-apps. *** Error code 1 Stop in /usr/ports/x11/xorg-apps. *** Error code 1 Stop in /usr/ports/x11/xorg. r...@blj01/usr/ports/x11/xorg: -- - ll /var/db/pkg total 25810 drwxr-xr-x 2 root wheel 512 Jun 19 06:14 db43-4.3.29_1/ -rw-r--r-- 1 root wheel 26382336 Jun 18 20:19 pkgdb.db drwxr-xr-x 2 root wheel 512 Jun 19 06:05 portmaster-2.7/ drwxr-xr-x 2 root wheel 512 Jun 19 06:14 portupgrade-2.4.6_2,2/ drwxr-xr-x 2 root wheel 512 Jun 19 06:14 ruby-1.8.7.160_2,1/ drwxr-xr-x 2 root wheel 512 Jun 19 06:14 ruby18-bdb43-0.6.5_1/ drwxr-xr-x 2 root wheel 512 Jun 19 06:00 screen-4.0.3_6/ drwxr-xr-x 2 root wheel 512 Jun 19 06:04 sudo-1.6.9.20/ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by xsetroot configure 1.0.2, which was generated by GNU Autoconf 2.59. Invocation command line was $ ./configure --x-libraries=/usr/local/lib --x-includes=/usr/local/include --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ --build=i386-portbld-freebsd7.2 ## - ## ## Platform. ## ## - ## hostname = uname -m = i386 uname -r = 7.2-RELEASE uname -s = FreeBSD uname -v = FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC /usr/bin/uname -p = i386 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown 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: /usr/X11R6/bin PATH: /root/bin ## --- ## ## Core tests. ## ## --- ## configure:1340: checking for a BSD-compatible install configure:1395: result: /usr/bin/install -c -o root -g wheel configure:1406: checking whether build environment is sane configure:1449: result: yes configure:1514: checking for gawk configure:1543: result: no configure:1514: checking for mawk configure:1543: result: no configure:1514: checking for nawk configure:1530: found /usr/bin/nawk configure:1540: result: nawk configure:1550: checking whether make sets $(MAKE) configure:1570: result: yes configure:1738: checking
Re: Now pkg-config trouble.................Re: startx does not work, startxfce4 does!
Leslie, The given port dirs (x11/xorg, etc) still probably have their work directory, which have the tokens/markers that particular stages of the port build have been done, such as the installation. rm -rf /usr/ports/*/*/work rehash cd /usr/ports/x11/xorg make install Please try that. First removes the work dir that contains the tokens, second updates root's available application hash, third and forth rebuild xorg Since xorg is so large, and receives very few (in relation to the total number of packages) updates, a quick-n-dirty way to get running is to add the package, and then update the outdated ones. pkg_add -r xorg portmaster -a I follow this same pattern on all BIG ports.. gnome2, kde3/4, xorg, and then let the portmaster update the old outdated ports that got installed. There is no functional difference between a package installed and a port installed with no options/config tweaked. Please try this. Write to us if you keep having problems ___ 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
