Gerald Pfeifer wrote:
>On Thu, 17 Sep 2009, Jason J. Hellenthal wrote:
>> Something like the following.
>>
>> [/usr/local/bin/]
>> libstdc++.so/usr/local/lib/gcc44/libstdc++.so
>> libstdc++.so.6 /usr/local/lib/gcc44/libstdc++.so.6
>
>That looks quite nice, and I was going to us
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
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 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
Pav Lucistnik wrote:
> Hi Jeremy,
>
> yes, we (portmgr) noticed this too. But we don't know why it happens,
> yet.
I'm 99% sure its because lang/perl5.10 is built after lang/perl5.8 and
the latter sets NO_LATEST_LINK=yes.
1) lang/perl5.10 should set latest link to perl5.10
2) it should not set n
Hello,
I discovered that libuuid wasn't actually producing type 1 UUIDs from
the MAC address of the machine. I've made a patch that gets it to do
that correctly, but I haven't wrangled with autotools to get it so it
would be suitable for sending upstream.
__
On Thu, 17 Sep 2009, Jason J. Hellenthal wrote:
> Something like the following.
>
> [/usr/local/bin/]
> libstdc++.so/usr/local/lib/gcc44/libstdc++.so
> libstdc++.so.6 /usr/local/lib/gcc44/libstdc++.so.6
That looks quite nice, and I was going to use that, alas I cannot
seem to
Hi,
I am maintainer of lmdbg port and would like to upgrade it to the latest
upstream version 0.11.0.
But as of version 0.10.0 the author of lmdbg removed GNU autotools stuff in
favor of his own framework -- mk-configure, written in bmake (portable version
of NetBSD make) and shell.
http://sourc
On Sun, Sep 20, 2009 at 03:15:32PM -0400, Robert Huff wrote:
> Lowell Gilbert writes:
>
> > It seems to me (fairly short investigation) that it uses kernel
> > structures that aren't in /usr/include. That means it must be
> > looking in /usr/src/sys. If those sources don't match the
> > inst
Lowell Gilbert writes:
> It seems to me (fairly short investigation) that it uses kernel
> structures that aren't in /usr/include. That means it must be
> looking in /usr/src/sys. If those sources don't match the
> installed kernel exactly, that typically won't be a problem,
> because kerne
Robert Huff writes:
> Lowell Gilbert writes:
>
>> >> Are you saying you rebuilt kernel and lsof built fine afterwards?
>>
>> Right. lsof needs to look at kernel structures, so it has to be
>> built from the same headers that the kernel was, or it won't know
>> how to interpret the data it
Hi Jeremy,
yes, we (portmgr) noticed this too. But we don't know why it happens,
yet.
Jeremy Chadwick píše v ne 20. 09. 2009 v 08:34 -0700:
> I came across the below today while rebuilding one of my boxes. It
> appears the perl.tbz symlink in Latest/ on the FTP mirrors has gone
> missing:
>
> g
I came across the below today while rebuilding one of my boxes. It
appears the perl.tbz symlink in Latest/ on the FTP mirrors has gone
missing:
gujoja# pkg_add -r perl
Error: FTP Unable to get
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/Latest/perl.tbz:
File unavailable (e.g
16 matches
Mail list logo
