Dear porters,
This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is
http://people.freebsd.org/~fenner/errorlogs/
so you can easily check the status of ports that you maintain. In
addition, the li
WANT_GNOME= yes
should that be WANT_GNOME or WITH_GNOME?
We should add --disable-tests to MOZ_OPTIONS unless WITH_DEBUG is enabled.
Lastly:
$portlint
WARN: Makefile: [45]: use of != in assignments is almost never a good
thing to do. Try to avoid using them. See
http://lists.freebsd.org/pipermai
Garrett Cooper wrote:
On Dec 27, 2008, at 14:59, Peter Jeremy
wrote:
On 2008-Dec-27 22:27:05 +0100, cwt wrote:
i usually have some trouble building world on amd64, but always
somewhere in gnu tree. this week it didn't fail and seemed
to build and install ok, but apparently...
I have been
Hi
Installation of port audio/aacplusenc fails.
The file http://teknoraver.net/software/mp4tools/aacplusenc-0.17.tar.bz2 is
unfetchable. It seems to be that the server is down?
--
Yours sincerely
Helko Glathe
___
freebsd-ports@freebsd.org mailing list
Hi Guys
Trying to build a FreeSBIE with MINIMAL=YES defined causes the
buildworld process to bomb out, below is the output from the log file,
any ideas??
-
>>> stage 4.2: building libraries
Installed the 2008-09-23 02:47:00 package to a 7.0 system and ran a
ktrace giving
2079 ktrace RET ktrace 0
2079 ktrace CALL execve(0xbfbfed94,0xbfbfec90,0xbfbfec98)
2079 ktrace NAMI "/usr/local/bin/timeseal"
2079 timeseal RET execve 0
2079 timeseal CALL compat.sigaction
2079 t
On Sun, Dec 28, 2008 at 8:37 PM, Sevan / Venture37 wrote:
> Hi Guys
> Trying to build a FreeSBIE with MINIMAL=YES defined causes the buildworld
> process to bomb out, below is the output from the log file, any ideas??
>
>
>
> -
>
> >>> st
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
matt donovan wrote:
does your normal buildworld bomb out? I tend to do a make buildworld
outside of freesbie then just put NO_BUILDWORLD in my freesbie.conf.
I don't have any problems running make buildworld when doing system
upgrades. I've copied the make.conf.minimal which is bundled with
f
14 matches
Mail list logo
