Dear porters,
This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is
http://people.freebsd.org/~fenner/errorlogs/
so you can easily check the status of ports that you maintain. In
addition, the li
Current FreeBSD problem reports
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including experimental
development code and obsolete releases.
Bugs can be in one of several states:
o - open
A problem report has bee
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
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
On Mon, Jan 28, 2008 at 07:45:09AM -0600, Stephen Montgomery-Smith wrote:
> Bill Fenner wrote:
>> Dear porters,
>>
>> This is just a reminder to please periodically check the list of
>> unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
>> A list by MAINTAINER is
>>
>> http://people
Wesley Shields wrote:
On Mon, Jan 28, 2008 at 07:45:09AM -0600, Stephen Montgomery-Smith wrote:
Bill Fenner wrote:
Dear porters,
This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is
http://peo
Quoting Frank Jahnke <[EMAIL PROTECTED]> (from Mon, 28 Jan 2008
08:23:23 -0800):
On Mon, 2008-01-28 at 14:29 +0100, Alexander Leidinger wrote:
Did you really specify /usr/local/lpr instead of
/usr/local/bin/lpr or /usr/bin/lpr?
Sorry, that was a typo -- I use /usr/bin/lpr, with CUPS contr
Hi,
In the good hope that there are more clever users than me on the list, I
need to upgrade a couple of mail servers to 2.3.11 and the problem is
that I need to apply the autocreate patches from University of Athens.
The patches does not apply cleanly after FreeBSD's own patchset have
been
On Mon, 2008-01-28 at 14:29 +0100, Alexander Leidinger wrote:
> Did you really specify /usr/local/lpr instead of
> /usr/local/bin/lpr or /usr/bin/lpr?
>
Sorry, that was a typo -- I use /usr/bin/lpr, with CUPS controlling the
printing. The message is "The specified file 'usr/bin/lpr' does not
Hi,
On Sun, Jan 27, 2008 at 09:36:55PM -0500, Vivek Khera wrote:
> It seems that the recent changes to the apache20 port Makefile.modules
> has broken how I've been configuring my systems.
>
> In my make.conf file I have globally set the following:
>
> WITH_BDB_VER=43
>
> which instructs many
Mark Ovens wrote:
> If someone can explain how to build a debug version of digikam (and
> libgphoto2) I will provide a back trace.
make -DWITH_DEBUG
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freeb
Re-posting as the original, posted a week ago, hasn't appeared on the
list - apologies if it appears twice
I originally posted this on the digikam mailing list as it appeared to
be a dk problem, however two people there have posted to say that it
works on Linux so it looks like this is specifi
Quoting Frank Jahnke <[EMAIL PROTECTED]> (from Sun, 27 Jan 2008
08:07:31 -0800):
Also, I was unable to print from it. Does that work for you?
Traditionally I have gone through /usr/local/lpr, but acroread8 seems
not to find it. I suspect it looks in the linux compat area, where it
does not f
Bill Fenner wrote:
Dear porters,
This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is
http://people.freebsd.org/~fenner/errorlogs/
so you can easily check the status of ports that you maintain.
checking for i386-portbld-freebsd6.2-ranlib... no
checking for ranlib... ranlib
checking for i386-portbld-freebsd6.2-strip... no
checking for strip... strip
checking for correct ltmain.sh version... no
configure: error:
*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a vers
On Mon, 2008-01-28 at 17:44 +0100, Alexander Leidinger wrote:
> You could try to just put /usr/local/bin/lpr in the acroread config instead.
>
That does indeed work. So acroread does not follow a symbolic link?
That's a first for me.
Frank
___
free
Doug Barton wrote:
I didn't see the first one, so it probably didn't hit the list.
Both of your problems are almost certainly caused by running the old
version first. Please repeat your -Baud run to make sure that
portmaster 2.0 is handling +IGNOREME properly (it should), and then
update apache
Alex Dupre wrote:
Mark Ovens wrote:
If someone can explain how to build a debug version of digikam (and
libgphoto2) I will provide a back trace.
make -DWITH_DEBUG
Thanks Alex - I seem to remember it wasn't that simple; it compiled with
``-g'' but the binaries still got stripped, but it wor
Mark Ovens wrote:
But, it doesn't seem to produce a core file and if I run it from within
gdb then gdb itself core dumps (and does produce a core file):
/home/mark{102}# gdb /usr/local/bin/digikam
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covere
Mark Ovens wrote:
> Doug Barton wrote:
>> I didn't see the first one, so it probably didn't hit the list.
>>
>> Both of your problems are almost certainly caused by running the old
>> version first. Please repeat your -Baud run to make sure that
>> portmaster 2.0 is handling +IGNOREME properly (it
People,
Much closer to getting local mail [[ from tao.thought.org]] working. so far,
no mail, not even to [EMAIL PROTECTED] gets thru.If tis does, can anyone
explain the appended lines from /var/log/maillog??? WHY is the "Helo
command rejected: Host not found"? sendmail *is* rewri
On Mon, Jan 28, 2008 at 05:28:24PM -0800, Gary Kline wrote:
> Much closer to getting local mail [[ from tao.thought.org]] working. so
> far,
> no mail, not even to [EMAIL PROTECTED] gets thru.If tis does, can anyone
> explain the appended lines from /var/log/maillog??? WHY is the "He
Clement Laforet wrote:
WITH_BERKELEYDB is now deprecated in favor of WITH_BDB in order to
make BDB support consistent with the rest of the ports tree.
Is there a warning generated for users that have the old one defined? If
not it would be a good idea to add one. In the past when I've changed
As a sysadmin, it's not unusual for me to have a desire to do similar
things on sets of systems; thus, when a colleague pointed out the
net/omnitty port to me, it didn't take long for me to find it useful.
But I noticed on 21 January that omnitty(1) wasn't working: upon
accepting the name of a ho
Mark Ovens wrote:
> Mark Ovens wrote:
>> But, it doesn't seem to produce a core file and if I run it from
>> within gdb then gdb itself core dumps (and does produce a core file):
It happens even here. This is the gdb backtrace:
(gdb) bt
#0 0x081c7a69 in cplus_demangle_mangled_name ()
#1 0x081c7
Good morning,
I am using portmaster v2.0 and very good it is to, except...
This morning among the ports that needed updating following my
over-night CVSup was security/sudo (1.6.9.6 -> 1.6.9.12). I am using
portmaster's new feature SU_CMD. I am also using the new HIDE_BUILD
feature which I rea
30 matches
Mail list logo
