# portsnap fetch update && portupgrade -arRLooking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
Fetching snapshot tag from portsnap2.freebsd.org... done.
Latest snapshot on server matches what we already have.
No updates needed.
Ports tree is already up to date.
Stale dependency: dbus-glib-0.74 --> glib-2.14.2 -- manually run 'pkgdb -F' to fix, or specify -O to force.
# pkgdb -F
---> Checking the package registry database
Stale dependency: dbus-glib-0.74 -> glib-2.14.2 (devel/glib20):
[Updating the portsdb <format:bdb_btree> in /usr/ports ... - 17867 port entries found .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000.........12000.........13000.........14000.........15000.........16000.........17000........ ..... done]
Install stale dependency? ([y]es/[n]o/[a]ll) [yes]
[Gathering depends for devel/glib20 ........... done]
---> Installing 'glib-2.14.4' from a port (devel/glib20)
---> Building '/usr/ports/devel/glib20'
===> Cleaning for glib-2.14.4
===> Vulnerability check disabled, database not found
===> Found saved configuration for glib-2.14.4
===> Extracting for glib-2.14.4
=> MD5 Checksum OK for gnome2/glib-2.14.4.tar.bz2.
=> SHA256 Checksum OK for gnome2/glib-2.14.4.tar.bz2.
===> glib-2.14.4 depends on file: /usr/local/bin/perl5.8.8 - found
===> Patching for glib-2.14.4
===> glib-2.14.4 depends on file: /usr/local/bin/perl5.8.8 - found
===> glib-2.14.4 depends on file: /usr/local/bin/libtool - found
===> Applying FreeBSD patches for glib-2.14.4
===> glib-2.14.4 depends on executable: gmake - found
===> glib-2.14.4 depends on file: /usr/local/bin/perl5.8.8 - found
===> glib-2.14.4 depends on file: /usr/local/bin/libtool - found
===> glib-2.14.4 depends on executable: pkg-config - found
===> glib-2.14.4 depends on shared library: pcre.0 - found
===> glib-2.14.4 depends on shared library: intl - found
===> Configuring for glib-2.14.4
env: ./configure: Permission denied
===> Script "configure" failed unexpectedly.
Please run the gnomelogalyzer, available from
"http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will diagnose the
problem and suggest a solution. If - and only if - the gnomelogalyzer cannot
solve the problem, report the build failure to the FreeBSD GNOME team at
gnome@FreeBSD.org, and attach (a)
"/tmp/port_wrk/usr/ports/devel/glib20/work/glib-2.14.4/config.log", (b) the
output of the failed make command, and (c) the gnomelogalyzer output. Also,
it might be a good idea to provide an overview of all packages installed on
your system (i.e. an `ls /var/db/pkg`). Put your attachment up on any website,
copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) with
the attachment. Try to avoid sending any attachments to the mailing list
(gnome@FreeBSD.org), because attachments sent to FreeBSD mailing lists are
usually discarded by the mailing list software.
*** Error code 1
Stop in /usr/ports/devel/glib20.
*** Error code 1
Stop in /usr/ports/devel/glib20.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall.34636.0 env make
** Fix the problem and try again.
** Listing the failed packages (*:skipped / !:failed)
! devel/glib20 (permission denied)
---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed
Command failed [exit code 1]: /usr/local/sbin/portinstall devel/glib20
# cd /usr/ports/devel/glib20 && wget http://www.freebsd.org/gnome/gnomelogalyzer.sh && chmod 700 gnomelogalyzer.sh && ./gnomelogalyzer.sh
--13:50:13-- http://www.freebsd.org/gnome/gnomelogalyzer.sh
=> `gnomelogalyzer.sh'
Resolving www.freebsd.org... 69.147.83.33, 2001:4f8:fff6::21
Connecting to www.freebsd.org|69.147.83.33|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7,870 (7.7K) [application/octet-stream]
100%[=================================================================================================================>] 7,870 4.63K/s
13:50:15 (4.63 KB/s) - `gnomelogalyzer.sh' saved [7870/7870]
Generating build log. Please wait... done.
The cause of your build failure is not known to gnomelogalyzer.sh. Before
e-mailing the build log to the FreeBSD GNOME team at freebsd-gnome@FreeBSD.org,
TRY EACH OF THE FOLLOWING:
* If you are generating your own logfile, make sure to generate it with
something similar to:
"make 2>&1 | tee /path/to/logfile" (sh/bash/ksh/zsh) or
"make |& tee /path/to/logfile" (csh/tcsh)
* Make sure your cvsup(1) configuration file specifies the 'ports-all'
collection
* Run cvsup(1) and attempt the build again
* Check /usr/ports/UPDATING for information pertinent to your build
failure
* 99% of the commonly reported build failures can be solved by
running "portupgrade -a"
* Read the FAQs at http://www.FreeBSD.org/gnome/
* Search the archives of freebsd-gnome@FreeBSD.org. Archives can be
searched at http://www.freebsd.org/gnome/index.html#search
If you have not performed each of the above suggestions, don't bother asking
for help. The chances are good that you'll simply be told to perform one of
the aforementioned steps.
