Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Jan 2009 15:45:50 +0100 (CET)
From:      Pieter Donche <>
To:        "mail.list freebsd-questions" <>
Subject:   port upgrade
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help
I just recently installed a new FreeBSD 7 system (beginning of week)
and installed a ports collection via portsnap fetch and portsnap extract.
which created a /usr/ports of 498 Mb

My cron does a portsnap every night
1 3 * * * root portsnap -I cron update && pkg_version -vIL=

So far the only packages I installed are: portupgrade and linux_base_fc4.
The I went for kde3. This installed a large nummber of packages.
But is stopped at error: aggregate 'Arts::PosixThreads::timespec 
abstime' h
as incomplete type and cannot be defined
gmake[2]: *** [threads_posix.lo] Error 1
gmake[2]: Leaving directory 
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory '/usr/ports/audio/arts/work/arts-1.5.10'
gmake: *** [all] Error 2
*** Error code 2
Stop in /usr/ports/audio/arts.
*** Error code 1
Stop in /usr/ports/audio/arts.
*** Error code 1
Stop in /usr/ports/x11/kdelibs3.
*** Error code 1
Stop in /usr/ports/x11/kdebase3.
*** Error code 1
Stop in /usr/ports/x11/kdebase3.
*** Error code 1
Stop in /usr/ports/x11/kde3.

How do I go from here - I feel uncertain, since my experience with FreebSD
ports system is almost nothging and with portupgrade etc.. is zero for the 
I would like not to make errors.

The mail from the nightly cronned portsnap does not report anything about
arts-... 'needs updating'.

Why not ?

Checking I see, there is a fix
from Mon 12 Jan 11:25 UTC, but this date is two days before the
the creation of the /usr/ports/audio/arts directory (Jan 14 08:58)

Does this mean I have the latest version?

If not, why does portsnap not report it.

Is is sufficient to do
# portupgrade arts
# cd /usr/ports/audio/arts
# make install clean
# cd /usr/ports/x11/kde3
# make install clean

I prefer to ask in advance, avoiding getting me into trouble because
of wrong approach..

Want to link to this message? Use this URL: <>