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
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
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
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
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,
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
Jan Beich jbe...@vfemail.net wrote:
Fabian Keil freebsd-lis...@fabiankeil.de writes:
Vitaly Magerya vmage...@gmail.com wrote:
I don't know what this part is supposed to do:
# Workaround to make sure clang isn't confused for gcc
CC=${COMPILER_TYPE}
... but it seems to
On Thu, 20 Nov 2014 17:47:28 -0800
Kevin Oberman rkober...@gmail.com wrote:
On Thu, Nov 20, 2014 at 9:26 AM, Dr. Peter Voigt pvo...@uos.de
wrote:
On Thu, 20 Nov 2014 14:40:21 +0100
Dr. Peter Voigt pvo...@uos.de wrote:
I am on 10.1-RELEASE (amd64) and I am currently using GnuPG
Fabian Keil freebsd-lis...@fabiankeil.de writes:
[*] Testing the CC wrapper and instrumentation output...
AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=. ./afl-clang -O2 -pipe
-fstack-protector -fno-strict-aliasing -Wall -D_FORTIFY_SOURCE=2
-Wno-pointer-sign
The two examples below strike me as particularly aggressive. Speaking as
someone working for a web-hosting group in a major company, I can tell
authoritatively, that -- had we used FreeBSD over there -- we would've
found having to upgrade this way unbearable.
We use Red Hat, which emphasizes
On 20 Nov 2014, at 17:51, Jan Beich jbe...@vfemail.net wrote:
...
while poudriere caught Clang i386 failing
[*] Testing the CC wrapper and instrumentation output...
AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=. ./afl-clang -O2 -pipe
-fstack-protector -fno-strict-aliasing -Wall
I've been using the rawrec port and after the 10.1 upgrade it no longer
works.
atlas.hesiod.org:anton[42]: rawrec
(null): sigaction on SIGIO failed: Invalid argument
I reinstalled with pkg install -f rawrec and built from the port and
still get the problem.
10.0 worked ok, but 10.1 is
Dimitry Andric d...@freebsd.org wrote:
On 20 Nov 2014, at 17:51, Jan Beich jbe...@vfemail.net wrote:
...
while poudriere caught Clang i386 failing
[*] Testing the CC wrapper and instrumentation output...
AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=. ./afl-clang -O2 -pipe
Jan Beich jbe...@vfemail.net wrote:
Fabian Keil freebsd-lis...@fabiankeil.de writes:
[*] Testing the CC wrapper and instrumentation output...
AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=. ./afl-clang -O2 -pipe
-fstack-protector -fno-strict-aliasing -Wall -D_FORTIFY_SOURCE=2
On 09/16/14 11:40, Janos Dohanics wrote:
Hello All,
trying to build/install /usr/ports/devel/py-gobject3:
# make install clean
=== Installing for py27-gobject3-3.8.1_2
=== py27-gobject3-3.8.1_2 depends on package: pygobject3-common=0 - found
=== py27-gobject3-3.8.1_2 depends on file:
On Fri, Nov 21, 2014 at 08:46:47AM -0800, Jeff Anton wrote:
I've been using the rawrec port and after the 10.1 upgrade it no longer
works.
atlas.hesiod.org:anton[42]: rawrec
(null): sigaction on SIGIO failed: Invalid argument
I reinstalled with pkg install -f rawrec and built from the
Fabian Keil freebsd-lis...@fabiankeil.de writes:
On 20 Nov 2014, at 17:51, Jan Beich jbe...@vfemail.net wrote:
...
while poudriere caught Clang i386 failing
[*] Testing the CC wrapper and instrumentation output...
AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=. ./afl-clang -O2 -pipe
Hi,
I try to write a port of an application that needs to edit /etc/nsswitch.conf.
But I have trouble modifying /etc/nsswitch.conf in pkg-plist (there is where it
should be done?).
Even creating a test file in pkg-plist seem be ignored:
/etc/testfile
@exec echo 'test' /etc/testfile
Any ideas
On Fri, Nov 21, 2014 at 2:36 PM, Moritz Warning moritzwarn...@web.de wrote:
Hi,
I try to write a port of an application that needs to edit /etc/nsswitch.conf.
But I have trouble modifying /etc/nsswitch.conf in pkg-plist (there is where
it should be done?).
Even creating a test file in
ok thanks, I did not know pkg-install.
On 11/21/2014 11:39 PM, Scot Hetzel wrote:
On Fri, Nov 21, 2014 at 2:36 PM, Moritz Warning moritzwarn...@web.de wrote:
Hi,
I try to write a port of an application that needs to edit
/etc/nsswitch.conf.
But I have trouble modifying /etc/nsswitch.conf
.
To unsubscribe, send an email to: unsubscribe-240...@elabs11.com with the
address: freebsd-ports@freebsd.org in the subject line.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send
21 matches
Mail list logo
