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
Hi Craig,
Yes, I've had problems trying to run vbox, where it just hangs. I
tried running it through ktrace, but it just stopped the trace after
loading the libraries, nothing else. Haven't tried with truss,
though, nor have I checked SUID or anything (wasn't motivated enough
to look deep into i
On Thu, 18 Jun 2009, Cantu, Mike wrote:
> I had an issue building the port with apr_memcache under the amd64
> 7.2-RELEASE. No matter what I tried, the configure phase would not
> "find" libapr_memcache. One of the tests would say "yes" but it would
> end up saying that the lib was not found. I
Hi All
Is anyone else having difficulties running this as a normal user ?
* running 7.2-RELEASE i386
* have added user to the vboxusers group.
* confirmed by issuing groups command as user
When I go to run VirtualBox it just hangs, if I run it within a truss
session I get a warning saying;
Vir
> From: demonichandextensi...@hotmail.com
> To: freebsd-ports@freebsd.org
> Date: Fri, 19 Jun 2009 20:22:31 +
> Subject: problem compiling audio/ardour
>
>
> I have tried several times now to get ardour installed on a few different
> systems. The first was a station that already had hyd
10 matches
Mail list logo
