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,
On Sun, Jan 25, 2009 at 8:27 PM, Garrett Cooper yanef...@gmail.com wrote:
On Jan 25, 2009, at 5:18, Robert Huff roberth...@rcn.com wrote:
bf writes:
Just a note to those of you who helped to integrate the Gnome,
X11, and Fortran updates in Ports: thank you very much for the
work that you
On Sat, 2009-01-10 at 00:48 -0500, Joe Marcus Clarke wrote:
Presenting GNOME 2.24 for FreeBSD.
See http://library.gnome.org/misc/release-notes/2.24/ for the general
release notes. On the FreeBSD front, this release introduces Fuse
support in HAL, adds multi-CPU support to libgtop, WebKit
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and
I think that it was a worthwhile line of exploration. I gave it a try,
and but with no success.
I sent Jarrod the output from ktrace/kdump
I'll rebuild nagios this weekend with debugging symbols again and run it
through gdb to get the exact error message that I saw earlier.
--karl
Guido
hi,
i have a fresh 7.1 i386 with gnome2-lite and fvwm-crystal fully built
from ports this w/e and fully up to date (including new Xorg).
when i try to run both vlc and mplayer from menus, nothing seems to
happen. from the terminal they run when i include a filename (eg vlc
1233.avi
Vladimir Grebenschikov wrote:
On Sat, 2009-01-10 at 00:48 -0500, Joe Marcus Clarke wrote:
Presenting GNOME 2.24 for FreeBSD.
See http://library.gnome.org/misc/release-notes/2.24/ for the general
release notes. On the FreeBSD front, this release introduces Fuse
support in HAL, adds multi-CPU
icemaca wrote:
hi,
i have a fresh 7.1 i386 with gnome2-lite and fvwm-crystal fully built
from ports this w/e and fully up to date (including new Xorg).
when i try to run both vlc and mplayer from menus, nothing seems to
happen. from the terminal they run when i include a filename (eg vlc
icemaca wrote:
[...]
the packages work fine, which is ver 0.8.x something i think for vlc,
but updating to 0.9.x in ports produced this problem and i am not sure
if it is something in the config options or other missing depends.
[...]
The vlc folks switched to a Qt-based interface. There's an
Philipp Ost wrote:
icemaca wrote:
[...]
the packages work fine, which is ver 0.8.x something i think for vlc,
but updating to 0.9.x in ports produced this problem and i am not
sure if it is something in the config options or other missing depends.
[...]
The vlc folks switched to a Qt-based
On Sat, Jan 24, 2009 at 09:20:35AM +0200, Mario Pavlov wrote:
Hi Peter,
well I guess I could try :)
only that I can't start right now and it will take some time...
I've update the port to 5.0.0.GA. However, the build still fails on the
ports cluster since it uses Maven to download the
INDEX build failed with errors:
Generating INDEX-6 - please wait..pkg_info: not found
pkg_info: not found
pkg_info: not found
pkg_info: not found
Done.
make_index: p5-ZConf-Mail-0.0.0: no entry for /usr/ports/devel/p5-IO-MultiPipe
Committers on the hook:
gabor glarkin marcus pgollucci rafan skv
On Mon, Jan 26, 2009 at 12:02 PM, icemaca icem...@gmail.com wrote:
when i try to run both vlc and mplayer from menus, nothing seems to happen.
from the terminal they run when i include a filename (eg vlc 1233.avi
ormplayer 1234.avi) but i get a borderless window playing video, and have no
On Mon, Jan 26, 2009 at 8:20 PM, icemaca icem...@gmail.com wrote:
back to the drawing board then. still baffled why mplayer too
Dunno if this is your case, but you may be confused by the way mplayer
GUI is launched. Normally, mplayer runs a GUI-less version of
mplayer, and as you have been
Hi,
I guess that cluster doesn't have internet connection for security reasons ?
Downloading the files from the maven repo prior to building the port sounds a
little bit complex to me...
But that's probably because I'm not very much in the ports system...however if
you think there's anything I
Dear Srs.
The error ocurred when I enter in my gmail.
[supo...@bsdteste /usr/home/suporte]$ firefox --sync
:1: error: unexpected character `\1', expected keyword - e.g. `style'
NP_Initialize
New
open dsp: No such file or directory
SetWindow
SetWindow
NewStream
WriteReady
Write
decoding...
Michal Varga wrote:
On Mon, Jan 26, 2009 at 8:20 PM, icemaca icem...@gmail.com wrote:
back to the drawing board then. still baffled why mplayer too
Dunno if this is your case, but you may be confused by the way mplayer
GUI is launched. Normally, mplayer runs a GUI-less version of
oh jesus, i didn't realize that was actually what you posted.
i saw it before, yet
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
INDEX build failed with errors:
Generating INDEX-6 - please wait..pkg_info: not found
pkg_info: not found
pkg_info: not found
pkg_info: not found
Done.
make_index: p5-ZConf-Mail-0.0.0: no entry for /usr/ports/devel/p5-IO-MultiPipe
Committers on the hook:
beech gabor glarkin marcus mnag pgj
On Sun, 25 Jan 2009 11:56:39 -0600, Victor Popov v.a.po...@gmail.com
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everyone,
Replying to myself, sorry.
Victor Popov wrote:
| Deluge bittorrent client is great, and has a flexible architecture,
which
| allows user to run a
Reproducibly stops at same place. This is probably pilot error, but
I have no clue. Is this known? Any help appreciated.
uname -a
FreeBSD leucine.activesitedynamics.com 7.1-RELEASE-p1 FreeBSD 7.1-RELEASE-p1 #0:
Thu Jan 8 17:33:50 CST 2009
On Mon, 2007-08-06 at 13:05 +0200, Chris Billington wrote:
On 8/6/07, Angelo Turetta ature...@commit.it wrote:
Chris Billington wrote:
Has anyone had any success with producing a port for the Kdenlive
video editor (kdenlive.sourceforge.net)? It looks like a more
sophisticated version
I get the following error in this build (make, make install clean):
In file included from libsmb/libsmbclient.c:25:
include/includes.h:1112: error: conflicting types for
'krb5_set_real_time'
/usr/local/include/krb5-protos.h:3486: error: previous declaration of
'krb5_set_real_time' was here
I was
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Howdy!
It's been almost exactly 6 months since the last portmaster release,
which in my mind is a good thing. :) I do have a new version ready
for those who would like to give it a try before I commit it.
It would be especially useful if those
Here's another one:
/bin/sh ../libtool --tag=CC--mode=link cc -D_THREAD_SAFE
-I/usr/local/include -D_THREAD_SAFE -I/usr/local/include
-DMALLOC_0_RETURNS_NULL -O2 -fno-strict-aliasing -pipe -version-number
2:1:0 -no-undefined -o libXrandr.la -rpath /usr/local/lib Xrandr.lo
XrrConfig.lo
Hi
I've written a port for OpenNMS, the port still needs a lot of work done
to it but I thought I'd post my initial effort to get some feedback on
how I went about it.
The port will install just fine except that it complains about some
files listed in the plist which are not there, well they
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
On Mon, Jan 26, 2009 at 10:09:47PM +0200, Mario Pavlov wrote:
I guess that cluster doesn't have internet connection for security reasons ?
Packages are built in an isolated environment on the package building
cluster, yes.
There are examples of ports that download from a repository, but I can't
Sevan / Venture37 wrote:
Hi
I've written a port for OpenNMS, the port still needs a lot of work done
to it but I thought I'd post my initial effort to get some feedback on
how I went about it.
The port will install just fine except that it complains about some
files listed in the plist which
On Tue, 2009-01-27 at 11:22 +1000, Da Rock wrote:
Here's another one:
/bin/sh ../libtool --tag=CC--mode=link cc -D_THREAD_SAFE
-I/usr/local/include -D_THREAD_SAFE -I/usr/local/include
-DMALLOC_0_RETURNS_NULL -O2 -fno-strict-aliasing -pipe -version-number
2:1:0 -no-undefined -o
It appear that the update of gstreamer-plugins from 0.10.1 to
0.10.2 ... might have broken the port.
When trying to do a full built of gnome2, this port is bombing out ...
In file included from audioconvert.c:32:
../../gst-libs/gst/floatcast/floatcast.h:111: error: redefinition of
On Mon, 2009-01-26 at 22:04 -0500, Robert Noland wrote:
On Tue, 2009-01-27 at 11:22 +1000, Da Rock wrote:
Here's another one:
/bin/sh ../libtool --tag=CC--mode=link cc -D_THREAD_SAFE
-I/usr/local/include -D_THREAD_SAFE -I/usr/local/include
-DMALLOC_0_RETURNS_NULL -O2
On Tue, 2009-01-27 at 15:28 +1000, Da Rock wrote:
On Mon, 2009-01-26 at 22:04 -0500, Robert Noland wrote:
On Tue, 2009-01-27 at 11:22 +1000, Da Rock wrote:
Here's another one:
/bin/sh ../libtool --tag=CC--mode=link cc -D_THREAD_SAFE
-I/usr/local/include -D_THREAD_SAFE
On Tue, 2009-01-27 at 00:53 -0500, Robert Noland wrote:
On Tue, 2009-01-27 at 15:28 +1000, Da Rock wrote:
On Mon, 2009-01-26 at 22:04 -0500, Robert Noland wrote:
On Tue, 2009-01-27 at 11:22 +1000, Da Rock wrote:
Here's another one:
/bin/sh ../libtool --tag=CC--mode=link cc
If anyone is interested in fixing the sipX ports and bringing them up
to date, they are now available for adoption. Otherwise, they are on
the deprecated list.
mcl
- Forwarded message from Mark Linimon lini...@freebsd.org -
From: Mark Linimon lini...@freebsd.org
To:
On Mon, 26 Jan 2009, David P. Discher wrote:
It appear that the update of gstreamer-plugins from 0.10.1 to 0.10.2 ...
might have broken the port.
It's more likely the update of multimedia/gstreamer from 0.10.21 to
0.10.22 that broke gstreamer-plugins.
When trying to do a full built of
On Mon, 26 Jan 2009 08:48:17 -0600, eculp wrote:
Quoting Max Brazhnikov m...@issp.ac.ru:
I've replied to k...@freebsd maillist, duplicating here:
On Sat, 24 Jan 2009 00:32:15 +0300, Max Brazhnikov wrote:
On Fri, 23 Jan 2009 13:17:32 -0600, eculp wrote:
I have tried everyway that I can
42 matches
Mail list logo
