FreeBSD unmaintained ports which are currently marked broken

2010-11-07 Thread linimon 
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 problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 6.x/7.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:   audio/festvox-aec
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=festvox-aec


portname:   audio/gtkguitune
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gtkguitune


portname:   audio/gxmms2
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gxmms2


portname:   audio/rsynth
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=rsynth


portname:   chinese/chinput3
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=chinput3


portname:   databases/p5-sqlrelay
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=p5-sqlrelay


portname:   devel/ace+tao
broken because: Does not compile on FreeBSD >= 7.0
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ace%2Btao


portname:   devel/fampp
broken because: FAM system mismatch: gamin is installed, while desired
FAM system is fam
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fampp


portname:   devel/gcvs
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gcvs


portname:   devel/linux-js
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-js


portname:   devel/linuxthreads
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linuxthreads


portname:   devel/ngpt
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ngpt


portname:   dns/fourcdns
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=fourcdns


portname:   emulators/cpmtools2
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=cpmtools2


portname:   emulators/win4bsd
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=win4bsd


portname:   finance/gfp
broken because: fails during build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=finance&portname=gfp


portname:   ftp/ftpq
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/por

FreeBSD ports which are currently marked broken

2010-11-07 Thread linimon 
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 problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 6.x/7.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:   audio/aureal-kmod
broken because: doesn't build on RELENG_8
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=aureal-kmod


portname:   audio/baudline
broken because: no longer available (website now have 1.08)
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=baudline


portname:   audio/ecawave
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ecawave


portname:   audio/emu10kx
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=emu10kx


portname:   audio/festvox-aec
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=festvox-aec


portname:   audio/gmpc-mserver
broken because: fails to build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gmpc-mserver


portname:   audio/gtkguitune
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gtkguitune


portname:   audio/gxmms2
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gxmms2


portname:   audio/rsynth
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=rsynth


portname:   benchmarks/polygraph
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=polygraph


portname:   benchmarks/polygraph31
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=polygraph31


portname:   cad/tclspice
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=tclspice


portname:   chinese/chinput3
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=chinput3


portname:   comms/hcfmdm
broken because: Does not compile at 7.x or higher
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=hcfmdm


portname:   comms/hso-kmod
broken because: does not build with USB2, please try comms/uhso-kmod
instead
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=hso-kmod


portname:   comms/ib-kmod
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=ib-kmod


portname:   comms/uticom
broken because: does not compile
build errors:   none.

FreeBSD unmaintained ports which are currently scheduled for deletion

2010-11-07 Thread linimon 
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 the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   audio/bmp-musepack
description:Musepack decoder for beep-media-player
maintainer: po...@freebsd.org
deprecated because: does not build with audio/musepack
expiration date:2010-11-15
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=bmp-musepack


portname:   audio/py-musepack
description:Python module that provides the Musepack decoding
interface
maintainer: po...@freebsd.org
deprecated because: does not build with audio/musepack
expiration date:2010-11-15
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-musepack


portname:   chinese/chinput3
description:Chinese GB2312,BIG5 code input server
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: Development has ceased.
expiration date:2010-12-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=chinput3


portname:   databases/p5-sqlrelay
description:Perl5 modules to access to SQL Relay, including a DBD
interface
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: broken and upstream disapeared
expiration date:2010-12-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=p5-sqlrelay


portname:   dns/fourcdns
description:A simple DNS server
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: upstream has disapeared
expiration date:2010-12-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=fourcdns


portname:   emulators/win4bsd
description:Win4BSD Virtual Machine for Windows under BSD
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: Development has ceased and distfile is no longer
available
expiration date:2010-12-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=win4bsd


portname:   french/mozilla-flp
description:seamonkey French Language Pack (FLP)
maintainer: po...@freebsd.org
deprecated because: www/seamonkey port is deprecated. Consider using the
www/firefox-i18n.
expiration date:2010-12-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=french&portname=mozilla-flp


portname:   french/xtel
description:An emulator for the french Minitel
maintainer: po...@freebsd.org
deprecated because: Minitel services will be discontinued at the end of
2010.
expiration date:2010-12-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=french&portname=xtel


portname:   ftp/ftpq
description:Upload queue manager for non-permanent connections
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: upstream has disapeared
expiration date:2010-12-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=ftp&portname=ftpq


portname:   graphics/g3dviewer
description:A 3D file viewer for GTK+
maintainer: po...@freebsd.org
deprecated because: does not build with gcc 4.2, upstream disapeared
expiration date:2010-12-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=g3dviewer


portname:   graphics/paintlib
description:C++ library for processing images
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: does not compile with new tiff and no more maintained
upstream
expiration date:2010-12-30
build errors:
http://pointyhat.FreeBSD.org/errorlogs/powerpc-errorlogs/e.8.20100815051156/paintlib-2.6.2_5.log.bz2
 (_Sep_20_05:12:48_UTC_2010)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=gra

FreeBSD ports which are currently scheduled for deletion

2010-11-07 Thread linimon 
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 the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   archivers/linux-par2cmdline
description:Linux version of par2cmdline
maintainer: marty...@freebsd.org
deprecated because: Native version available
expiration date:2010-11-15
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=linux-par2cmdline


portname:   audio/bmp-musepack
description:Musepack decoder for beep-media-player
maintainer: po...@freebsd.org
deprecated because: does not build with audio/musepack
expiration date:2010-11-15
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=bmp-musepack


portname:   audio/libmpcdec
description:High quality audio compression format
maintainer: multime...@freebsd.org
deprecated because: superseded by audio/musepack
expiration date:2010-11-15
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=libmpcdec


portname:   audio/py-musepack
description:Python module that provides the Musepack decoding
interface
maintainer: po...@freebsd.org
deprecated because: does not build with audio/musepack
expiration date:2010-11-15
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-musepack


portname:   chinese/chinput3
description:Chinese GB2312,BIG5 code input server
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: Development has ceased.
expiration date:2010-12-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=chinput3


portname:   databases/p5-sqlrelay
description:Perl5 modules to access to SQL Relay, including a DBD
interface
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: broken and upstream disapeared
expiration date:2010-12-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=p5-sqlrelay


portname:   devel/libisc
description:ISC's utility library
maintainer: si...@freebsd.org
deprecated because: Unlikely to be used...
expiration date:2010-11-07
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=libisc


portname:   devel/php-dbg2
description:Debugger for PHP
maintainer: jpaet...@freebsd.org
status: BROKEN
deprecated because: No upstream support
expiration date:2010-12-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=php-dbg2


portname:   devel/thistest
description:A Java unit testing framework
maintainer: alepul...@freebsd.org
status: IGNORE
deprecated because: development has ceased; website disappeared
expiration date:2011-04-11
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=thistest


portname:   dns/bind9
description:Completely new version of the BIND DNS suite with
updated DNSSEC
maintainer: do...@freebsd.org
deprecated because: Past EOL, will be removed when RELENG_6 goes EOL
expiration date:2010-11-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=bind9


portname:   dns/fourcdns
description:A simple DNS server
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: upstream has disapeared
expiration date:2010-12-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=fourcdns


portname:   emulators/dynagen-devel
description:Text-based front end for Dynamips development version
maintainer: pavelivol...@googlemail.com
deprecated because: Please install emulators/dynagen instead
expiration date:2010-12-01
build errors:   none.
overview:   
http://portsmon.F

FreeBSD unmaintained ports which are currently marked forbidden

2010-11-07 Thread linimon 
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, including errors seen on the build farm,
is included below.

portname:   misc/compat3x
forbidden because:  FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath  - not
fixed / no lib available
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x
___
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"

FreeBSD ports which are currently marked forbidden

2010-11-07 Thread linimon 
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, including errors seen on the build farm,
is included below.

portname:   databases/gnats
forbidden because:  Security issues
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats


portname:   misc/compat3x
forbidden because:  FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath  - not
fixed / no lib available
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x
___
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"

[CFT] mplayer / mencoder port update

2010-11-07 Thread Thomas Zander 
Hi,

I have prepared a recent mplayer snapshot for a possible update for
mplayer and mencoder ports.
You can find the tarball here:

http://www.rrr.de/~riggs/mplayer/m20101106.tar.bz2

Since I had to tweak it on several occasions to get it to build and I
have tested it only on amd64 so far, please test whether it builds and
works as intended for you. Of course, I appreciate any form of
constructive feedback.

Thanks in advance,
Riggs
___
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"

Re: [CFT] mplayer / mencoder port update

2010-11-07 Thread Anonymous 
Thomas Zander  writes:

> Hi,
>
> I have prepared a recent mplayer snapshot for a possible update for
> mplayer and mencoder ports.
> You can find the tarball here:
>
> http://www.rrr.de/~riggs/mplayer/m20101106.tar.bz2
>
> Since I had to tweak it on several occasions to get it to build and I
> have tested it only on amd64 so far, please test whether it builds and
> works as intended for you. Of course, I appreciate any form of
> constructive feedback.

Can you include ariff's patch for VPC (Volume Per Channel)?

  http://people.freebsd.org/~ariff/ports/multimedia_mplayer/patch-xzz
  http://forums.freebsd.org/showpost.php?p=29564&postcount=31

I've been using it for about a year and it *works* unlike
the one in uoti's repo.

  http://repo.or.cz/w/mplayer.git/commitdiff/91d0d3a

Also, did you miss -ac mpg123 with previous update intentionally?
It decodes faster than -ac mp3lib on my 2yo amd64 box.
___
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"

Re: Can't update apr1 on 7.3 stable

2010-11-07 Thread eculp 

Quoting Christer Solskogen :


On Sun, Nov 7, 2010 at 3:44 AM, eculp  wrote:

Trying to update all my ports on 7.3-STABLE FreeBSD 7.3-STABLE #1135: Fri
Oct 29 07:32:29 CDT 2010.

I can't get apr1 to build.  It breaks with the following messages:



Try uninstallling automake, autoconf and libtool first.

--
chs,

Thanks so much, Chris.  Hopefully someone can see the errors in my  
ways while doing this.I have done that many times already but I  
think that maybe I may be leaving something undone or in the wrong  
order, etc.  So, I just did the following:


  First check the existing packages
# ls -d /var/db/pkg/automake* /var/db/pkg/autoconf* /var/db/pkg/libtool*
/var/db/pkg/autoconf-2.68   /var/db/pkg/automake-1.11.1 
 /var/db/pkg/automake-wrapper-20071109
/var/db/pkg/autoconf-wrapper-20071109   /var/db/pkg/automake-1.4.6_6
 /var/db/pkg/libtool-2.2.10


   Deinstall them
/# pkg_deinstall /var/db/pkg/automake* /var/db/pkg/autoconf*  
/var/db/pkg/libtool*

--->  Deinstalling 'automake-1.11.1'
--->  Deinstalling 'automake-1.4.6_6'
[Updating the pkgdb  in /var/db/pkg ... - 1153  
packages found (-1 +0) (...) done]

--->  Deinstalling 'autoconf-2.68'
[Updating the pkgdb  in /var/db/pkg ... - 1152  
packages found (-1 +0) (...) done]

--->  Deinstalling 'automake-wrapper-20071109'
[Updating the pkgdb  in /var/db/pkg ... - 1151  
packages found (-1 +0) (...) done]

--->  Deinstalling 'libtool-2.2.10'
[Updating the pkgdb  in /var/db/pkg ... - 1150  
packages found (-1 +0) (...) done]

--->  Deinstalling 'autoconf-wrapper-20071109'
[Updating the pkgdb  in /var/db/pkg ... - 1149  
packages found (-1 +0) (...) done]
[Updating the pkgdb  in /var/db/pkg ... - 1148  
packages found (-1 +0) (...) done]


Verify that they have actually been deinstalled
# ls -d /var/db/pkg/automake* /var/db/pkg/autoconf* /var/db/pkg/libtool*
ls: /var/db/pkg/autoconf*: No such file or directory
ls: /var/db/pkg/automake*: No such file or directory
ls: /var/db/pkg/libtool*: No such file or directory

I did not delete the original apr1 - first in the list
ls -d /var/db/pkg/*apr*
/var/db/pkg/apr-ipv6-devrandom-gdbm-db42-1.4.2.1.3.9_1   
/var/db/pkg/xf86dgaproto-2.1 
/var/db/pkg/xineramaproto-1.2


I then ran
# portmaster apr-ipv6-devrandom-gdbm-db42-1.4.2.1.3.9_1

The end is again repeated

===>  Building for apr-ipv6-devrandom-gdbm-db46-ldap24-1.4.2.1.3.10
cd /new/usr/local/ports/devel/apr1/work/apr-1.4.2; /usr/bin/env  
TMPDIR="/tmp" TMPDIR="/tmp" SHELL=/bin/sh NO_LINT=YES  
ACLOCAL=/usr/local/bin/aclocal-1.11  
AUTOMAKE=/usr/local/bin/automake-1.11 AUTOMAKE_VERSION=111  
AUTOCONF=/usr/local/bin/autoconf-2.68  
AUTOHEADER=/usr/local/bin/autoheader-2.68  
AUTOIFNAMES=/usr/local/bin/ifnames-2.68  
AUTOM4TE=/usr/local/bin/autom4te-2.68  
AUTORECONF=/usr/local/bin/autoreconf-2.68  
AUTOSCAN=/usr/local/bin/autoscan-2.68  
AUTOUPDATE=/usr/local/bin/autoupdate-2.68 AUTOCONF_VERSION=268  
LIBTOOL=/usr/local/bin/libtool LIBTOOLIZE=/usr/local/bin/libtoolize  
LIBTOOL_M4=/usr/local/share/aclocal/libtool.m4 PREFIX=/usr/local   
LOCALBASE=/usr/local X11BASE=/usr/local  MOTIFLIB="-L/usr/local/lib  
-lXm -lXp" LIBDIR="/usr/lib"  CC="cc" CPP="cpp" CXX="c++"  CFLAGS="-O2  
-fno-strict-aliasing -pipe -DLDAP_DEPRECATED" CXXFLAGS="-O2  
-fno-strict-aliasing -pipe -DLDAP_DEPRECATED"  MANPREFIX="/usr/local"  
BSD_INSTALL_PROGRAM="install  -s -o root -g wheel -m 555"   
BSD_INSTALL_LIB="install  -s -o root -g wheel -m 444"   
BSD_INSTALL_SCRIPT="install  -o root -g wheel -m 555"   
BSD_INSTALL_DATA="install  -o root -g wheel -m 444"   
BSD_INSTALL_MAN="install  -o root -g wheel -m 444" /usr/bin/make
/bin/sh /new/usr/local/ports/devel/apr1/work/apr-1.4.2/libtool  
--silent --mode=compile cc -g -O2   -DHAVE_CONFIG_H-I./include  
-I/new/usr/local/ports/devel/apr1/work/apr-1.4.2/include/arch/unix  
-I./include/arch/unix  
-I/new/usr/local/ports/devel/apr1/work/apr-1.4.2/include/arch/unix  
-I/new/usr/local/ports/devel/apr1/work/apr-1.4.2/include  -o  
passwd/apr_getpass.lo -c passwd/apr_getpass.c && touch  
passwd/apr_getpass.lo

X--mode=compile: not found
*** Warning: inferring the mode of operation is deprecated.: not found
*** Future versions of Libtool will require --mode=MODE be specified.:  
not found

Xcc: not found
X-g: not found
X-O2: not found
X-DHAVE_CONFIG_H: not found
/new/usr/local/ports/devel/apr1/work/apr-1.4.2/libtool: X-I./include:  
not found
/new/usr/local/ports/devel/apr1/work/apr-1.4.2/libtool:  
X-I/new/usr/local/ports/devel/apr1/work/apr-1.4.2/include/arch/unix:  
not found
/new/usr/local/ports/devel/apr1/work/apr-1.4.2/libtool:  
X-I./include/arch/unix: not found
/new/usr/local/ports/devel/apr1/work/apr-1.4.2/libtool:  
X-I/new/usr/local/ports/devel/apr1/work/apr-1.4.2/include/arch/unix:  
not found
/new/usr/local/ports/devel/apr1/work/apr-1.4.2/libtool:  
X-I/new/usr/

Re: Can't update apr1 on 7.3 stable

2010-11-07 Thread Christer Solskogen 
On Sun, Nov 7, 2010 at 2:30 PM, eculp  wrote:

> Thanks for any corrections to the procedure or anything else that I could be
> doing wrong.
>

I don't think you have done something wrong ;-) But take a look at
this: Maybe you have the same issue?
http://lists.freebsd.org/pipermail/freebsd-apache/2010-June/001798.html



-- 
chs,
___
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"

Status of: PR ports/151133

2010-11-07 Thread Jerry 
Has there been any work done on "PR 151183"
?

I attempted to build it again and it still fails. Apparently, there are
at least three users affected by this problem. It appears to affect
both i386 and amd64 bit systems.

Has anyone else experienced this phenomena?

-- 
Jerry ✌
freebsd-ports.u...@seibercom.net

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
Experience is what you get when you didn't get what you wanted.
___
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"

Re: Status of: PR ports/151133

2010-11-07 Thread Rob Farmer 
On Sun, Nov 7, 2010 at 09:16, Jerry  wrote:
> Has there been any work done on "PR 151183"
> ?
>
> I attempted to build it again and it still fails. Apparently, there are
> at least three users affected by this problem. It appears to affect
> both i386 and amd64 bit systems.
>
> Has anyone else experienced this phenomena?

Isn't mysql 5.5 (which seems to be what everyone in the PR is running)
an unsupported development version? The php extension builds and works
fine with 5.1 so the burden is probably more on the reporters to
submit a fix - maybe upstream php has one?

-- 
Rob Farmer
___
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"

problem on building perl5.12

2010-11-07 Thread Koichiro Iwao 
I've post the same to freebsd-questions but no replies, let me
repost. Does anyone know how to make perl?

I tried to upgrade perl 5.10 to 5.12 according to UPDATING
but building perl 5.12 fails. I believe the failure is caused by
needless "-lnsl" option. How to build it fine?

# portmaster -o lang/perl5.12 lang/perl5.10
---(snip)---
and I got the following output:

/usr/bin/ld: cannot find -lnsl
I can't compile the test program.
You have a BIG problem.  Shall I abort Configure [y]  
Ok.  Stopping Configure.
===>  Script "Configure" failed unexpectedly.
Please report the problem to s...@freebsd.org [maintainer] and attach the
"/usr/ports/lang/perl5.12/work/perl-5.12.2/config.log" including the
output
of the failure of your make command. Also, it might be a good idea to
provide
an overview of all packages installed on your system (e.g. an `ls
/var/db/pkg`).
*** Error code 1

See also; whole portmaster outputs:
http://www.club.kyutech.ac.jp/~meta/temp/perlerror.txt

-- 
kiwao
___
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"

Re: Status of: PR ports/151133

2010-11-07 Thread Jerry 
On Sun, 7 Nov 2010 09:27:35 -0800
Rob Farmer  articulated:

> On Sun, Nov 7, 2010 at 09:16, Jerry
>  wrote:
> > Has there been any work done on "PR 151183"
> > ?
> >
> > I attempted to build it again and it still fails. Apparently, there
> > are at least three users affected by this problem. It appears to
> > affect both i386 and amd64 bit systems.
> >
> > Has anyone else experienced this phenomena?
> 
> Isn't mysql 5.5 (which seems to be what everyone in the PR is running)
> an unsupported development version? The php extension builds and works
> fine with 5.1 so the burden is probably more on the reporters to
> submit a fix - maybe upstream php has one?

I question whether or not it is "unsupported"; however, that doesn't
change the fact that the PR is factually correct. If the PHP extension
will not build with that version of MySQL, then the port should so
indicate it. Perhaps using a "CONFLICTS" statement or something similar
in the ports Makefile would be appropriate.

I do find it rather interesting that while I employ quite a few PHP
modules, this is the only one that fails. Perhaps there is an inherent
problem with the port that up until now had not be discovered. In any
event, I thought that Ale would have responded with some feedback by
now.

-- 
Jerry ✌
freebsd-ports.u...@seibercom.net

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
Why are a wise man and a wise guy opposites?


signature.asc
Description: PGP signature

Re: [CFT] mplayer / mencoder port update

2010-11-07 Thread Stefan Ehmann 
On Sunday 07 November 2010 12:50:48 Thomas Zander wrote:
> Hi,
> 
> I have prepared a recent mplayer snapshot for a possible update for
> mplayer and mencoder ports.
> You can find the tarball here:
> 
> http://www.rrr.de/~riggs/mplayer/m20101106.tar.bz2
> 
> Since I had to tweak it on several occasions to get it to build and I
> have tested it only on amd64 so far, please test whether it builds and
> works as intended for you. Of course, I appreciate any form of
> constructive feedback.

Built fine here. Unfortunately, x264 support in mencoder is broken.

Apparently, mencoder wants X264_BUILD >= 99, but multimedia/x264 is at build 
98.
___
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"

Re: Can't update apr1 on 7.3 stable

2010-11-07 Thread Edwin L. Culp W. 
On Sun, Nov 7, 2010 at 10:48 AM, Christer Solskogen
 wrote:
> On Sun, Nov 7, 2010 at 2:30 PM, eculp  wrote:
>
>> Thanks for any corrections to the procedure or anything else that I could be
>> doing wrong.
>>
>
> I don't think you have done something wrong ;-) But take a look at
> this: Maybe you have the same issue?
> http://lists.freebsd.org/pipermail/freebsd-apache/2010-June/001798.html
>
>
>
> --
> chs,
> ___
> 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"
>

No doubt.  If that is going to be necessary, I think it would make
sense to upgrade to 8 stable or 9 current.  And then reinstall my
ports.   I should have done this some time ago but . . . . . lazy.

Thanks,

ed
___
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"

Re: sane-backend 1.0.21 broke on 8.0?

2010-11-07 Thread Jason Naughton 
Hi Warren,

> One last thing, then I'm out of tricks.  After the change to FreeBSD 8,
> did you rebuild all, yes all, of your ports?

I did a complete re-install.  I didn't upgrade.  So when I installed
Freebsd 8 the ports were built with that version of the OS.

> Also (two! two last tricks!) you should not have the libusb port
> installed, since libusb is now part of the OS.

# pkg_info |grep libusb
#

Not installed.

I've managed to solve the problem but at the same time definitely find a
bug with the sane-backend 1.0.21.  I wanted to isolate where the seg fault
was occurring as it was not occurring when I moved everything out of
/usr/local/etc/sane.d and just left epson.conf which was indicated from
the sane support page that my scanner was to be apart of.  With only
epson.conf
inside of the /usr/local/etc/sane.d folder I had the following results:

# sane-find-scanner -q
found USB scanner (vendor=0x04b8 [EPSON], product=0x011e [EPSON Scanner])
at libusb:/dev/usb:/dev/ugen3.2

# scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

I could do this as root or as user.  Now if I put everything back into
/usr/local/etc/sane.d I would get a seg fault.  So I did the following:

# cd /usr/local/etc/sane.d
# mkdir ../orig
# mv * ../orig
# mv ../orig/epson.conf .
# mv ../orig/epson2.conf .
# mv ../orig/dll* .

So now:

# ls /usr/local/etc/sane.d
dll.confdll.d   epson.conf  epson2.conf

# scanimage -L
device `epson2:libusb:/dev/usb:/dev/ugen3.2' is a Epson GT-8300 flatbed
scanner

Now both xsane and scanimage work fine without a seg fault.  Odd that the
same scanner that was under epson is now seen as an epson2.

So using trial a process of elimination I moved one file at a time back
into the sane.d folder.  What I found was when the microtek2.conf file was
added to the sane.d folder the following would occur:

# scanimage -L
zsh: segmentation fault  scanimage -L

My quick and simple solution would be to simply delete the microteck2.conf
file and I can now use my scanner.  Yet what is in this file that would
make scanimage seg fault:

# grep -v "#" microtek2.conf

option dump 1
option no-backtrack-option on
option lightlid-35 on
option toggle-lamp on
option lineart-autoadjust on
option backend-calibration on
scsi * * Scanner

One of the above lines is causing scanimage to segfault. As I move this
file outside of the sane.d folder I can now:

# scanimage -L
device `epson2:libusb:/dev/usb:/dev/ugen3.2' is a Epson GT-8300 flatbed
scanner

and everything works again...  Just to recap my scanner is an EPSON
Perfection 1660 Photo usb scanner which is supposedly completely
compatible with sane-backends.

Cheers

Jason Naughton,  P.Eng, M.E.Sc,
Professional Contractor,
JMN Planning,  Pickering, Ontario,
Office: (416)-509-4886 Fax: (905)-831-3810


___
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"

RFC/CFT dialog(1) replacement for ports infrastructure

2010-11-07 Thread Eitan Adler 
I've been working on a replacement for dialog(1) as used in ports for
make config.

It provides a number of benefits over the existing infrastructure
1) It supports always-on "long descriptions"
2) Supports mutually exclusive options.
3) Support's user-input freeform options
4) Supports the license infrastructure - the configuration screen
provided the ability to view and accept/reject the port's license
5) It is released under the  MIT license (thus avoiding the GPLed dialog)
6) Since it doesn't rely on dialog we have a lot more control over it.
If we needed to do something it would be easier

Please note that this is currently a backend feature only. There are
NO port facing or user facing configuration changes at this time.
bsd.options.mk would have to be changed to have this implemented.

The source code is available at
https://isis.poly.edu/~eitan/files/d4p-version8.2/
Makefile - a makefile to build the standalone binary.
   It would obviously be included in the build system with
significant changes.
dialog4ports.c - the main source file
dialog4ports.h - the main header file
nolicence.sh - runs the program without a license to accept
withlicence.sh - runs the program with a license to accept
info.txt - random junk used for testing
lic.txt - random junk used for testing
n.txt - random junk used for testing

I've been discussing this program on EFnet's #bsdports with largely
positive feedback. I'm now looking for more eyes to review the program
and more people to test it. Are there any situations on which this
program would fail?

What would it take for this tool to become the new config screen for
ports? Are there any non-bikeshead objections? If yes what can I do to
resolve them? If no what is the next step for me to take?

If you have a specific feature request for the tool and it it is
something integrable I might do it, but I want to avoid the "I want
every feature so lets put it in" problem.

A few people have asked me to turn this into a generic dialog(1)
replacement. This is not the goal of this program, but I would not
against making such a library in the future. Making such a library
requires a very different program than I had in mind - so please don't
bring this up for now. I'll consider doing it as a GSOC project.
-- 
Eitan Adler
___
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"

[patch] Port lint shouldn't report that 'work' isn't in cvs

2010-11-07 Thread Eitan Adler 
portlint currently reports two conflicting messages when it finds a
"work" directory in a port
a) Make sure it isn't committed
b) It was not found in CVS

This patch silences the second one

--- portlint.old2010-11-05 14:02:28.0 -0400
+++ portlint2010-11-07 20:58:57.0 -0500
@@ -464,7 +464,7 @@
if /^(?:\.\.?|CVS)$/;
my $filename = $dir eq '.' ? $_ : "$dir/$_";
if (-d $filename) {
-   if (!$entries{$_} || $entries{$_} ne 'D') {
+   if ((!$entries{$_} || $entries{$_} ne 'D') && 
$filename ne 'work') {
&perror("FATAL", "", -1, "directory 
$filename not in CVS.");
}
else {


-- 
Eitan Adler
___
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"