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,
I cannot compile the port /usr/ports/math/fftw on either FreeBSD 6.4
i386 or FreeBSD 8.1 i386. Some ports such as audio/gramofile require
fftw. The error I get when building the fftw port is along these
lines:
snip
libtool: compile: gcc44 -DHAVE_CONFIG_H -I. -I. -I. -I. -I./../fftw
-I. -O2
On 06/09/2010 23:12, per...@pluto.rain.com wrote:
Matthias Andree mand...@freebsd.org wrote:
Am 06.09.2010 07:32, schrieb Dominic Fandrey:
What kind of dependency should I define if I just need something
for the install target? It's not needed before, not after and
not for the package.
I
--- Upgrading 'lua-5.1.4' to 'lua-5.1.4_1' (lang/lua)
--- Building '/usr/ports/lang/lua'
=== Cleaning for lua-5.1.4_1
=== License check disabled, port has not defined LICENSE
=== Extracting for lua-5.1.4_1
= MD5 Checksum OK for lua-5.1.4.tar.gz.
= SHA256 Checksum OK for lua-5.1.4.tar.gz.
===
Hi
Thanks in advance for fixing
dns1# cd /usr/ports/multimedia/gstreamer-plugins-ugly
dns1# make clean
=== Cleaning for gstreamer-plugins-ugly-0.10.16,3
dns1# make
=== License check disabled, port has not defined LICENSE
= gst-plugins-ugly-0.10.16.tar.bz2 is not in
Andrea Venturoli m...@netfence.it writes:
--- Upgrading 'lua-5.1.4' to 'lua-5.1.4_1' (lang/lua)
--- Building '/usr/ports/lang/lua'
=== Cleaning for lua-5.1.4_1
=== License check disabled, port has not defined LICENSE
=== Extracting for lua-5.1.4_1
= MD5 Checksum OK for
On 9/6/10 10:07 PM, Brian W. wrote:
Any chance this could by default do a sa-update? I have this happen
twice now where portupgrade -ap got me a new spamassassin, but spamd
wouldn't start until I ran sa-update.
patches welcome, but consider automated ports builds, and portmaster and
Hi,
On Sat, Sep 04, 2010 at 10:00:06PM +0400, Anonymous swel...@gmail.com wrote:
Since the PR was handed over to you by p...@[1] I haven't seen any activity
for around a month. Do you even have an interest in the lisp port? If not or
I'm sorry for what happened, but the only reason I didn't
Hi
Thanks in advance for fixing
dns1# cd /usr/ports/multimedia/gstreamer-plugins-ugly
dns1# make clean
=== Cleaning for gstreamer-plugins-ugly-0.10.16,3
dns1# make
=== License check disabled, port has not defined LICENSE
= gst-plugins-ugly-0.10.16.tar.bz2 is not in
Alexander Pyhalov ha scritto:
Can someone explain why this stubs are in libc? Why didn't linker just
throw a linking error?
Simple explanation: the stubs are there because you can create a
thread-safe library and use it in a single-threaded or multi-threaded
program. Once linked to a
Thanks for explanation.
Alex Dupre wrote:
Simple explanation: the stubs are there because you can create a
thread-safe library and use it in a single-threaded or multi-threaded
program. Once linked to a multi-threaded program (with -pthread) the
library gets access to the real libthr
Alexander Pyhalov ha scritto:
Yes, it was the case. And it was not rather simple to find out this :)
Did I win anything? ;-)
And one more interesting thing. I have a sample threaded application. On
one system it was implicitly linked to libthr (on 8.0-stable), and on
other system
Alex Dupre wrote:
Alexander Pyhalov ha scritto:
Yes, it was the case. And it was not rather simple to find out this :)
Did I win anything? ;-)
Yes. My gratitude.
It would be more if I had gotten this answer two dayas ago before
sitting with gdb for a working day :)
--
Best regards,
On Tue, Sep 07, 2010 at 02:18:02PM +0400, Alexander Pyhalov wrote:
Thanks for explanation.
Alex Dupre wrote:
Simple explanation: the stubs are there because you can create a
thread-safe library and use it in a single-threaded or multi-threaded
program. Once linked to a multi-threaded
Hi All,
I've just spent over 3 hours at the pc watching over a py-lucene install,
accepting licenses, running off to other download sites to fetch stuff, that
sort of fun.
So I was not happy to be getting a stop error after 3 hours like I have got
below. any ideas how to proceed please?
Gav...
Size mismatch for file from www.fox-toolkit.org/ftp
File not available from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/
dns1# make
=== License check disabled, port has not defined LICENSE
=== Found saved configuration for fox-1.6.37_3
= fox-1.6.40.tar.gz doesn't seem to exist in
Size mismatch for file from www.fox-toolkit.org/ftp
File not available from
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/
dns1# make
=== License check disabled, port has not defined LICENSE
=== Found saved configuration for fox-1.6.37_3
= fox-1.6.40.tar.gz doesn't seem to
On Tue, Sep 07, 2010 at 02:31:38PM +0100, David Southwell wrote:
As a test I downloaded the file via http from http://www.fox-
toolkit.org/fox.html and then ran
# make makesum
and then tried
#make
and received the following errors:
configure: WARNING: unrecognized options:
On Tue, Sep 07, 2010 at 02:31:38PM +0100, David Southwell wrote:
As a test I downloaded the file via http from http://www.fox-
toolkit.org/fox.html and then ran
# make makesum
and then tried
#make
and received the following errors:
configure: WARNING: unrecognized options:
Hello!
I've recently bumped into the issue which was already discussed
on current@:
http://lists.freebsd.org/pipermail/freebsd-current/2010-July/018638.html
In short, in the ports' tinderbox, i386 jail fails on the amd64 host
during make distribution step. This configuration, while
not strictly
Dear port committers,
I understand that infofarmer@ and miwi@ have no more enough free
time to be hyper-active about those and other ports (and btw, thanks
very much for the huge work you did in the past!), but is out there
anyone else out there with both a commit bit and some time on hand to
2010/8/23 Mark Linimon lini...@lonesome.com:
I sent mail to sobomax on the 17th and he responded. I'm willing to
wait a few more days to see what action he takes but that's it.
mcl
Have you heard from sobo...@?
Thanks in advance.
--
TAKATSU Tomonari
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/10 16:39, Lapo Luchini wrote:
Dear port committers,
I understand that infofarmer@ and miwi@ have no more enough free
time to be hyper-active about those and other ports (and btw, thanks
very much for the huge work you did in the
Quoth Lapo Luchini on Tuesday, 07 September 2010:
Dear port committers,
I understand that infofarmer@ and miwi@ have no more enough free
time to be hyper-active about those and other ports (and btw, thanks
very much for the huge work you did in the past!), but is out there
anyone else out
--- Original message ---
From: Lapo Luchini l...@lapo.it
To: po...@freebsd.org
Cc: infofar...@freebsd.org, m...@freebsd.org, s...@freebsd.org
Sent: 7.9.'10, 20:39
Dear port committers,
I understand that infofarmer@ and miwi@ have no more enough free
time to be hyper-active about
On 09/07/2010 09:39 AM, Lapo Luchini wrote:
Dear port committers,
I understand that infofarmer@ and miwi@ have no more enough free
time to be hyper-active about those and other ports (and btw, thanks
very much for the huge work you did in the past!), but is out there
anyone else out there
Il 09/07/10 10:40, Anonymous ha scritto:
It's expected becasue you're overriding -fPIC in port's Makefile from
your make.conf (CFLAGS=...). If you still want to *reduce* optimization
then append CFLAGS by using `+=' instead of `='.
Thanks, this was the problem.
So, I've had the following in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/10 19:33, Andrea Venturoli wrote:
Il 09/07/10 10:40, Anonymous ha scritto:
It's expected becasue you're overriding -fPIC in port's Makefile from
your make.conf (CFLAGS=...). If you still want to *reduce* optimization
then append CFLAGS
On 09/07/2010 12:39, FreeBSD Ports wrote:
06.09.2010 19:53, jhell написав(ла):
I have just created a gdb7 port from the existing devel/gdb6.
Sir, if your port follows my example of having the Insight (GUI-front
end for GDB) as an option, you have my blessing. Back in the day I had
to
So, I've had the following in /etc/make.conf since eons:
CFLAGS=-O -pipe
COPTFLAGS=-O -pipe
Genrally speaking (meaning for any port), is this still useful?
Are the above flags deprecated?
Will I get optimized code without them?
$ make -V CFLAGS -V COPTFLAGS
- -O2 -pipe
- -O2 -pipe
are
On 09/07/2010 01:20 PM, Lapo Luchini wrote:
Doug Barton wrote:
For those that we are simply
repackaging, what's the value in doing that, vs. simply allowing
users to download them from mozilla's site?
Well, in vastly multi-user places there might of course be good reasons
to have a single
On Tue, Sep 7, 2010 at 19:39, Doug Barton do...@freebsd.org wrote:
My concern with this for some time is that there is little to no actual
benefit for the vast majority of these ports, however they do consume
resources. Admittedly not an overwhelming number of resources, but given the
fact
On 09/07/2010 09:09 PM, Rob Farmer wrote:
Around 6 months ago, a similar thing was proposed for a number of
eclipse plugins - they can all be installed and updated via the
builtin update manager and nothing is built for FreeBSD - they are
just Java stuff that can be binary downloaded and run
Doug Barton wrote:
Are these eclipse plugins similar to mozilla plugins in that the user
has to take an additional step after the FreeBSD package is added, or if
the package is on the system then it's available to all the users
immediately? If the latter, then I can understand why having
On 09/07/2010 09:36 PM, Lapo Luchini wrote:
Doug Barton wrote:
Are these eclipse plugins similar to mozilla plugins in that the user
has to take an additional step after the FreeBSD package is added, or if
the package is on the system then it's available to all the users
immediately? If the
On Tue, Sep 7, 2010 at 21:32, Doug Barton do...@freebsd.org wrote:
On 09/07/2010 09:09 PM, Rob Farmer wrote:
Around 6 months ago, a similar thing was proposed for a number of
eclipse plugins - they can all be installed and updated via the
builtin update manager and nothing is built for
Rob Farmer wrote:
Do users have to run some command to import the plugins into their
~/.mozilla profiles after root installs them or is it automatic?
Homedir of the iser isn't really involved, Firefox/Thunderbird/SeaMonkey
expect the system to have system-wide packages available in system
42 matches
Mail list logo
