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 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
> Hi virtualbox users!
>
> I am very glad to be able to send out a VirtualBox 4.2.0 call for testers.
> We've done a good job pushing many patches upstream before the
> release this time so our port is much smaller and easier to handle.
great!
now some question :-)
where can I get latest kbuild?
> great!
> now some question :-)
> where can I get latest kbuild?
> ...
You need kBuild-devel from redports.org svn repository:
svn co https://svn.redports.org/virtualbox/devel/kBuild-devel
# cd kBuild-devel && make deinstall install clean
--
Mikhail
> ===> Building for virtualbox-ose-4.2.0
>
> > great!
> > now some question :-)
> > where can I get latest kbuild?
> > ...
>
> You need kBuild-devel from redports.org svn repository:
>
> svn co https://svn.redports.org/virtualbox/devel/kBuild-devel
> # cd kBuild-devel && make deinstall install clean
>
thanks, btw, maybe the maintener of
latest devel/kBuild-devel is included in the CFT tarball. Please use
that one. I know it
has about the same version number but that is because it's only a
snapshot without
a new release. I should have said that earlier but I simply forgot. Sorry.
vbox@ is the new maintainer of kBuild and kBuild-de
> latest devel/kBuild-devel is included in the CFT tarball. Please use
> that one. I know it
> has about the same version number but that is because it's only a
> snapshot without
> a new release. I should have said that earlier but I simply forgot. Sorry.
>
> vbox@ is the new maintainer of kBuild
I'm trying to debug some segfaults in firefox,
which require having debugging symbols in many
places including the base OS (e.g. libc, libthr).
So I added WITH_DEBUG=yes to /etc/make.conf.
I now see that some ports don't build with
debugging support, e.g.:
# make WITHOUT_DEBUG=
===> png-1.5.12 is
The whole day I get this error message on all systems I maintain, trying
to update the /usr/ports tree via svn:
# [/usr/ports]: make update
Updating '.':
svn: E175002: Unable to connect to a repository at URL
'http://svn.freebsd.org/ports/head'
svn: E175002: OPTIONS of 'http://svn.freebsd.org/por
[ O. Hartmann wrote on Fri 21.Sep'12 at 16:34:20 +0200 ]
> The whole day I get this error message on all systems I maintain, trying
> to update the /usr/ports tree via svn:
>
>
> # [/usr/ports]: make update
> Updating '.':
> svn: E175002: Unable to connect to a repository at URL
> 'http://svn.fr
I install vboxdrv.ko in /usr/local/modules via:
cd virtualbox-ose-kmod
make KMODDIR=/usr/local/modules install
but when installing in virtualbox-ose
there is no KMODDIR, and hence make install fails
___
freebsd-ports@freebsd.org mailing
Thanks to this email (omitted, too lengthy) I removed directories sheduled for
deletion which would have halted portmaster's procedures were they to be only
existing with my own files within them...
bsdar
games/pets
and copied portmanager, its .so.'s, and man page for safekeeping (I used it in
IN FreeBSD 8.3-STABLE usign the openoffice 3.4.1
It finishes with this error:
Entering /usr/ports/editors/openoffice-3/work/aoo-3.4.1/main/store/source
o3tl deliver
Checking DLL ../unxfbsdx.pro/lib/check_libuno_salhelpergcc3.so.3 ...:
ERROR:
/usr/ports/editors/openoffice-3/work/aoo-3.4.1/main/
graphics/autotrace has been updated to OptionsNG, but there is a check of .if
${PORT_OPTIONS:MSETUIDMING} while the Option for it is just MING, not
SETUIDMING. Really minor, but if anyone is using this port with that option,
they would be in a bit of a pickle.
Thanks,
Naram Qashat
___
16 matches
Mail list logo
