On Wed, 3 Nov 2010 12:27:04 -0300
Joey Mingrone j...@mingrone.org mentioned:
I cannot reproduce this error. It builds succesfully on the
buildfarm, so it might be related to non-standard build options
in some ports. Unfortunately I can't seem to be able to figure
out which one. The temporary
On Wed, 3 Nov 2010 12:27:04 -0300
Joey Mingrone j...@mingrone.org mentioned:
Hello,
I'm trying to build this port, but get the error below. Any
suggestions? All dependencies are installed.
Thanks,
Joey
dot -Tcanon discriminating-functions.dot discriminating-functions.txt
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 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,
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,
Hi,
I have prepared a recent mplayer snapshot for a possible update for
mplayer and mencoder ports.
You can find the tarball here:
http://www.rrr.de/~riggs/mplayer/m20101106.tar.bz2
Since I had to tweak it on several occasions to get it to build and I
have tested it only on amd64 so far, please
Thomas Zander thomas.e.zan...@googlemail.com writes:
Hi,
I have prepared a recent mplayer snapshot for a possible update for
mplayer and mencoder ports.
You can find the tarball here:
http://www.rrr.de/~riggs/mplayer/m20101106.tar.bz2
Since I had to tweak it on several occasions to get
Quoting Christer Solskogen christer.solsko...@gmail.com:
On Sun, Nov 7, 2010 at 3:44 AM, eculp ec...@encontacto.net wrote:
Trying to update all my ports on 7.3-STABLE FreeBSD 7.3-STABLE #1135: Fri
Oct 29 07:32:29 CDT 2010.
I can't get apr1 to build. nbsp;It breaks with the following messages:
On Sun, Nov 7, 2010 at 2:30 PM, eculp ec...@encontacto.net wrote:
Thanks for any corrections to the procedure or anything else that I could be
doing wrong.
I don't think you have done something wrong ;-) But take a look at
this: Maybe you have the same issue?
Has there been any work done on PR 151183
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/151133?
I attempted to build it again and it still fails. Apparently, there are
at least three users affected by this problem. It appears to affect
both i386 and amd64 bit systems.
Has anyone else
On Sun, Nov 7, 2010 at 09:16, Jerry freebsd-ports.u...@seibercom.net wrote:
Has there been any work done on PR 151183
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/151133?
I attempted to build it again and it still fails. Apparently, there are
at least three users affected by this problem.
I've post the same to freebsd-questions but no replies, let me
repost. Does anyone know how to make perl?
I tried to upgrade perl 5.10 to 5.12 according to UPDATING
but building perl 5.12 fails. I believe the failure is caused by
needless -lnsl option. How to build it fine?
# portmaster -o
On Sun, 7 Nov 2010 09:27:35 -0800
Rob Farmer rfar...@predatorlabs.net articulated:
On Sun, Nov 7, 2010 at 09:16, Jerry
freebsd-ports.u...@seibercom.net wrote:
Has there been any work done on PR 151183
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/151133?
I attempted to build it again
On Sunday 07 November 2010 12:50:48 Thomas Zander wrote:
Hi,
I have prepared a recent mplayer snapshot for a possible update for
mplayer and mencoder ports.
You can find the tarball here:
http://www.rrr.de/~riggs/mplayer/m20101106.tar.bz2
Since I had to tweak it on several occasions to
On Sun, Nov 7, 2010 at 10:48 AM, Christer Solskogen
christer.solsko...@gmail.com wrote:
On Sun, Nov 7, 2010 at 2:30 PM, eculp ec...@encontacto.net wrote:
Thanks for any corrections to the procedure or anything else that I could be
doing wrong.
I don't think you have done something wrong ;-)
Hi Warren,
One last thing, then I'm out of tricks. After the change to FreeBSD 8,
did you rebuild all, yes all, of your ports?
I did a complete re-install. I didn't upgrade. So when I installed
Freebsd 8 the ports were built with that version of the OS.
Also (two! two last tricks!) you
I've been working on a replacement for dialog(1) as used in ports for
make config.
It provides a number of benefits over the existing infrastructure
1) It supports always-on long descriptions
2) Supports mutually exclusive options.
3) Support's user-input freeform options
4) Supports the license
portlint currently reports two conflicting messages when it finds a
work directory in a port
a) Make sure it isn't committed
b) It was not found in CVS
This patch silences the second one
--- portlint.old2010-11-05 14:02:28.0 -0400
+++ portlint2010-11-07 20:58:57.0
21 matches
Mail list logo
