FreeBSD ports which are currently scheduled for deletion

2011-01-06 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/ecawave
description:Simple graphical audio file editor
maintainer: syl...@freebsd.org
status: BROKEN
deprecated because: has been broken for over one year
expiration date:2011-02-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ecawave


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/bind94
description:The BIND DNS suite with updated DNSSEC and threads
maintainer: do...@freebsd.org
deprecated because: Reaches EOL May 2011
expiration date:2011-04-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=bind94


portname:   dns/bind94-geoip
description:The BIND DNS suite with updated DNSSEC and threads
maintainer: do...@freebsd.org
deprecated because: Reaches EOL May 2011
expiration date:2011-04-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=bind94-geoip


portname:   emulators/xmamegui
description:SDLMAME frontend that has been written using Java
maintainer: alepul...@freebsd.org
deprecated because: development has ceased; try emulators/qmc2 instead
expiration date:2011-04-11
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=xmamegui


portname:   games/airrox
description:An 3D Air Hockey, which uses SDL & OpenGL
maintainer: alepul...@freebsd.org
deprecated because: development has ceased
expiration date:2011-04-11
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=airrox


portname:   games/bfm
description:Battle for Mandicor is free RTS fantasy game using
Stratagus
maintainer: alepul...@freebsd.org
deprecated because: development has ceased; website disappeared
expiration date:2011-04-11
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=bfm


portname:   games/xracer
description:Awesome WipeOut clone for OpenGL and X11!
maintainer: bsdkaf...@gmail.com
deprecated because: has not been developed for 10 years
expiration date:2011-04-11
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=xracer


portname:   java/netbeans3
description:A full-featured integrated environment for Java
maintainer: po...@freebsd.org
status: IGNORE
deprecated because: old, unmaintained
expiration date:2011-03-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=netbeans3


portname:   java/netbeans4
description:A full-featured integrated environment for Java
maintainer: po...@freebsd.org
status: IGNORE
deprecated because: old, unmaintained
expiration date:2011-03-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=netbeans4


portname:   java/netbeans5
description:A free and open-source IDE for Java
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: old, unmaintained
expiration date:2011-03-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=netbeans5


portname:   lang/gpc
description:GNU Pascal compiler
maintainer: alepul...@freebsd.org
deprecated because: development has ceased; use lang/fpc instead
expiration date:2011-04-11
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=gpc


portname:   mail/spa

FreeBSD ports which are currently marked forbidden

2011-01-06 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:   www/chromium
forbidden because:  several security vulnerabilities
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=chromium
___
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 unmaintained ports which are currently scheduled for deletion

2011-01-06 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:   java/netbeans3
description:A full-featured integrated environment for Java
maintainer: po...@freebsd.org
status: IGNORE
deprecated because: old, unmaintained
expiration date:2011-03-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=netbeans3


portname:   java/netbeans4
description:A full-featured integrated environment for Java
maintainer: po...@freebsd.org
status: IGNORE
deprecated because: old, unmaintained
expiration date:2011-03-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=netbeans4


portname:   java/netbeans5
description:A free and open-source IDE for Java
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: old, unmaintained
expiration date:2011-03-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=netbeans5


portname:   net/straw
description:A GNOME 2 desktop weblog aggregator written in Python
maintainer: po...@freebsd.org
deprecated because: abandoned upstream and does not work with python 2.6+
expiration date:2011-03-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=straw


portname:   shells/bash3
description:The GNU Project's Bourne Again SHell
maintainer: po...@freebsd.org
deprecated because: Use shells/bash or shells/bash-static instead
expiration date:2011-01-21
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=bash3


portname:   shells/bash3-static
description:The GNU Project's Bourne Again SHell
maintainer: po...@freebsd.org
deprecated because: Use shells/bash or shells/bash-static instead
expiration date:2011-01-21
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=bash3-static
___
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 broken

2011-01-06 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:   accessibility/eflite
broken because: does not link
build errors:
http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20101229091133/eflite-0.4.1.log
 (_Dec_31_18:05:29_UTC_2010)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=accessibility&portname=eflite


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/gx2osd
broken because: does not configure
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20101230082724/gx2osd-0.2_6.log
 (_Dec_31_00:45:50_UTC_2010)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gx2osd


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


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:   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 comp

FreeBSD unmaintained ports which are currently marked broken

2011-01-06 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/gx2osd
broken because: does not configure
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20101230082724/gx2osd-0.2_6.log
 (_Dec_31_00:45:50_UTC_2010)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gx2osd


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


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/crow
broken because: Doesn't build with Glibmm 2.25
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=crow


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:   emulators/cpmtools2
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=cpmtools2


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


portname:   games/hlstats
broken because: checksum mismatch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=hlstats


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


portname:   games/lgeneral-data
broken because: bad plist
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9.20101120065700/lgeneral-data-1.1.3_3.log.bz2
 (_Nov_21_13:26:40_UTC_2010)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=lgeneral-data


portname:   graphics/libv3d
broken because: does not build
build errors:
http://pointyhat.freebsd

Re: Xfce 4.8pre3

2011-01-06 Thread Oliver Lehmann

Bernhard Froehlich  wrote:


http://home.bluelife.at/patches/xfce48.tgz

Wouldn't it be a good to talk to oliver@ first before duplicating  
all the work?


I'm right now working on a new archive with the latest 4.8.pre version
of Xfce based on miwi's work.



This message was sent using IMP, the Internet Messaging Program.

___
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: FreeBSD Port: isc-dhcp41-server-4.1.2,1; Concurrent IPv4 DHCP and DHCPv6

2011-01-06 Thread Freddie Cash
The OpenVPN port does a pretty good job of this.  Default rc.d script
is just openvpn.  But you can create manual symlinks to it using
openvpn_somename, and it checks rc.conf for openvpn_somename_enable.

Having to manually create the symlink is kind of needed in the openvpn
setup and can lead to left-over files on port removal, but wouldn't be
needed for dhcpd.

Might want to look through the openvpn rc script for ideas.
-- 
Freddie Cash
fjwc...@gmail.com
___
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: FreeBSD Port: isc-dhcp41-server-4.1.2,1; Concurrent IPv4 DHCP and DHCPv6

2011-01-06 Thread Wesley Shields
On Thu, Jan 06, 2011 at 10:01:23PM -0500, Wesley Shields wrote:
> On Thu, Jan 06, 2011 at 04:49:36PM -0800, Doug Barton wrote:
> > On 01/05/2011 01:14, Douglas Thrift wrote:
> > > Hello,
> > >
> > > Since ISC dhcpd 4.1 now supports DHCPv6, but a single instance of the
> > > daemon can't do both IPv4 DHCP and DHCPv6, it would be nice if the rc.d
> > > script from the port could be configured to start the daemon twice. Has
> > > anyone thought about this at all or implemented anything?
> > 
> > I really dislike this trend that we're seeing of individual rc.d scripts 
> > supporting running multiple versions of the same daemon, but I haven't 
> > yet found the time to write it up for TPH. The canonical way to do this 
> > is for the rc.d script to have multiple copies of itself, and then do 
> > something like:
> > 
> > name="${0##*/}"
> > 
> > For this example you could have the port install rc.d/dhcpd by default 
> > (or whatever the name is, not suggesting a change), and an option to 
> > also install dhcpd_v6 (perhaps as a symlink). This would make it easy to 
> > clean up as the additional copy of the script should also be in the plist.
> 
> I'm not a big fan of the same script running multiple versions of the
> same daemon either. I do think the symlink and code above is a good
> solution though.
> 
> > The other reason I haven't squawked more about this is that for services 
> > that would like to be able to run an arbitrary number of the same daemon 
> > the servicename_N_{flags|pidfile|etc} method works, and eliminates the 
> > problem of leaving behind multiple numbers of the script after port 
> > deinstall. But for something like this where we're discussing a fixed 
> > (and small) number of copies it's better to have this done the "right" way.
> 
> I didn't know servicename_N_foo existed. I still like the symlink
> approach. I can certainly add that to the port in the future.

Forgot to mention... Could you please submit a PR for this so that it
does not end up lost?

-- WXS
___
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: FreeBSD Port: isc-dhcp41-server-4.1.2,1; Concurrent IPv4 DHCP and DHCPv6

2011-01-06 Thread Wesley Shields
On Thu, Jan 06, 2011 at 04:49:36PM -0800, Doug Barton wrote:
> On 01/05/2011 01:14, Douglas Thrift wrote:
> > Hello,
> >
> > Since ISC dhcpd 4.1 now supports DHCPv6, but a single instance of the
> > daemon can't do both IPv4 DHCP and DHCPv6, it would be nice if the rc.d
> > script from the port could be configured to start the daemon twice. Has
> > anyone thought about this at all or implemented anything?
> 
> I really dislike this trend that we're seeing of individual rc.d scripts 
> supporting running multiple versions of the same daemon, but I haven't 
> yet found the time to write it up for TPH. The canonical way to do this 
> is for the rc.d script to have multiple copies of itself, and then do 
> something like:
> 
> name="${0##*/}"
> 
> For this example you could have the port install rc.d/dhcpd by default 
> (or whatever the name is, not suggesting a change), and an option to 
> also install dhcpd_v6 (perhaps as a symlink). This would make it easy to 
> clean up as the additional copy of the script should also be in the plist.

I'm not a big fan of the same script running multiple versions of the
same daemon either. I do think the symlink and code above is a good
solution though.

> The other reason I haven't squawked more about this is that for services 
> that would like to be able to run an arbitrary number of the same daemon 
> the servicename_N_{flags|pidfile|etc} method works, and eliminates the 
> problem of leaving behind multiple numbers of the script after port 
> deinstall. But for something like this where we're discussing a fixed 
> (and small) number of copies it's better to have this done the "right" way.

I didn't know servicename_N_foo existed. I still like the symlink
approach. I can certainly add that to the port in the future.

Thanks!

-- WXS
___
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: FreeBSD Port: isc-dhcp41-server-4.1.2,1; Concurrent IPv4 DHCP and DHCPv6

2011-01-06 Thread Doug Barton

On 01/05/2011 01:14, Douglas Thrift wrote:

Hello,

Since ISC dhcpd 4.1 now supports DHCPv6, but a single instance of the
daemon can't do both IPv4 DHCP and DHCPv6, it would be nice if the rc.d
script from the port could be configured to start the daemon twice. Has
anyone thought about this at all or implemented anything?


I really dislike this trend that we're seeing of individual rc.d scripts 
supporting running multiple versions of the same daemon, but I haven't 
yet found the time to write it up for TPH. The canonical way to do this 
is for the rc.d script to have multiple copies of itself, and then do 
something like:


name="${0##*/}"

For this example you could have the port install rc.d/dhcpd by default 
(or whatever the name is, not suggesting a change), and an option to 
also install dhcpd_v6 (perhaps as a symlink). This would make it easy to 
clean up as the additional copy of the script should also be in the plist.


The other reason I haven't squawked more about this is that for services 
that would like to be able to run an arbitrary number of the same daemon 
the servicename_N_{flags|pidfile|etc} method works, and eliminates the 
problem of leaving behind multiple numbers of the script after port 
deinstall. But for something like this where we're discussing a fixed 
(and small) number of copies it's better to have this done the "right" way.



hth,

Doug

--

Nothin' ever doesn't change, but nothin' changes much.
-- OK Go

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.com/

___
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: print/teTeX-base failed to install on ia64

2011-01-06 Thread Anton Shterenlikht
On Thu, Jan 06, 2011 at 09:59:44PM +, Anton Shterenlikht wrote:
> I've no problems updating to teTeX-base-3.0_21 on amd64 and
> on sparc64. HOwever, on ia64 I get this error on "make install":
> 
> *snip*
> install  -o root -g wheel -m 444 ./mktex.opt 
> /usr/local/share/texmf/web2c/mktex.opt
> install  -o root -g wheel -m 555 ./mktexdir 
> /usr/local/share/texmf/web2c/mktexdir
> install  -o root -g wheel -m 444 ./mktexdir.opt 
> /usr/local/share/texmf/web2c/mktexdir.opt
> install  -o root -g wheel -m 555 ./mktexnam 
> /usr/local/share/texmf/web2c/mktexnam
> install  -o root -g wheel -m 444 ./mktexnam.opt 
> /usr/local/share/texmf/web2c/mktexnam.opt
> install  -o root -g wheel -m 555 ./mktexupd 
> /usr/local/share/texmf/web2c/mktexupd
> /bin/sh ../libtool --mode=install install  -o root -g wheel -m 444 
> .libs/libkpathsea.a /usr/local/lib
> install -o root -g wheel -m 444 .libs/libkpathsea.a 
> /usr/local/lib/libkpathsea.a
> ranlib /usr/local/lib/libkpathsea.a
> chmod 644 /usr/local/lib/libkpathsea.a
> /bin/sh ../libtool --mode=install install  -s -o root -g wheel -m 555 
> kpsewhich /usr/local/bin
> install -o root -g wheel -m 555 -s kpsewhich /usr/local/bin/kpsewhich
> install  -s -o root -g wheel -m 555 kpsestat /usr/local/bin
> BFD: /usr/local/bin/stZ0ROVc: The first section in the PT_DYNAMIC segment is 
> not the .dynamic section
> strip:/usr/local/bin/stZ0ROVc[.interp]: Bad value
> BFD: /usr/local/bin/stZ0ROVc: The first section in the PT_DYNAMIC segment is 
> not the .dynamic section
> strip:/usr/local/bin/stZ0ROVc: Bad value
> install: wait: No such file or directory
> gmake[2]: *** [install-exec] Error 70
> gmake[2]: Leaving directory 
> `/usr/ports/print/teTeX-base/work/tetex-src-3.0/texk/kpathsea'
> gmake[1]: *** [install] Error 1
> gmake[1]: Leaving directory 
> `/usr/ports/print/teTeX-base/work/tetex-src-3.0/texk'
> gmake: *** [install] Error 1
> *** Error code 2
> 
> Stop in /usr/ports/print/teTeX-base.
> #
> 
> I can do
> 
> # cd ./work/tetex-src-3.0/texk/kpathsea/
> # make install
> 
> with no errors.
> 
> 
> I also wonder which "strip" is used above: /usr/bin/strip
> or the one from devel/binutils: /usr/local/bin/strip? 
> 

I've found several similar errors on the net, e.g.:
http://www.coreboot.org/AVATT#The_KVM_image_is_outdated

they blame binutils. There was a recent fix to binutils on ia64,
perhaps I better send this to @current?

many thanks
anton

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
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"


print/teTeX-base failed to install on ia64

2011-01-06 Thread Anton Shterenlikht
I've no problems updating to teTeX-base-3.0_21 on amd64 and
on sparc64. HOwever, on ia64 I get this error on "make install":

*snip*
install  -o root -g wheel -m 444 ./mktex.opt 
/usr/local/share/texmf/web2c/mktex.opt
install  -o root -g wheel -m 555 ./mktexdir 
/usr/local/share/texmf/web2c/mktexdir
install  -o root -g wheel -m 444 ./mktexdir.opt 
/usr/local/share/texmf/web2c/mktexdir.opt
install  -o root -g wheel -m 555 ./mktexnam 
/usr/local/share/texmf/web2c/mktexnam
install  -o root -g wheel -m 444 ./mktexnam.opt 
/usr/local/share/texmf/web2c/mktexnam.opt
install  -o root -g wheel -m 555 ./mktexupd 
/usr/local/share/texmf/web2c/mktexupd
/bin/sh ../libtool --mode=install install  -o root -g wheel -m 444 
.libs/libkpathsea.a /usr/local/lib
install -o root -g wheel -m 444 .libs/libkpathsea.a /usr/local/lib/libkpathsea.a
ranlib /usr/local/lib/libkpathsea.a
chmod 644 /usr/local/lib/libkpathsea.a
/bin/sh ../libtool --mode=install install  -s -o root -g wheel -m 555 kpsewhich 
/usr/local/bin
install -o root -g wheel -m 555 -s kpsewhich /usr/local/bin/kpsewhich
install  -s -o root -g wheel -m 555 kpsestat /usr/local/bin
BFD: /usr/local/bin/stZ0ROVc: The first section in the PT_DYNAMIC segment is 
not the .dynamic section
strip:/usr/local/bin/stZ0ROVc[.interp]: Bad value
BFD: /usr/local/bin/stZ0ROVc: The first section in the PT_DYNAMIC segment is 
not the .dynamic section
strip:/usr/local/bin/stZ0ROVc: Bad value
install: wait: No such file or directory
gmake[2]: *** [install-exec] Error 70
gmake[2]: Leaving directory 
`/usr/ports/print/teTeX-base/work/tetex-src-3.0/texk/kpathsea'
gmake[1]: *** [install] Error 1
gmake[1]: Leaving directory 
`/usr/ports/print/teTeX-base/work/tetex-src-3.0/texk'
gmake: *** [install] Error 1
*** Error code 2

Stop in /usr/ports/print/teTeX-base.
#

I can do

# cd ./work/tetex-src-3.0/texk/kpathsea/
# make install

with no errors.


I also wonder which "strip" is used above: /usr/bin/strip
or the one from devel/binutils: /usr/local/bin/strip? 

many thanks
anton

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
freebsd-questi...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

- End forwarded message -

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
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: FreeBSD Port: isc-dhcp41-server-4.1.2,1; Concurrent IPv4 DHCP and DHCPv6

2011-01-06 Thread Wesley Shields
On Wed, Jan 05, 2011 at 01:14:26AM -0800, Douglas Thrift wrote:
> Hello,
> 
> Since ISC dhcpd 4.1 now supports DHCPv6, but a single instance of the
> daemon can't do both IPv4 DHCP and DHCPv6, it would be nice if the rc.d
> script from the port could be configured to start the daemon twice. Has
> anyone thought about this at all or implemented anything?

I'm certainly open to the idea if you can get it to work cleanly. I'm
not entirely sure it's going to be an easy solution though. It might be
a better question for the rc list (to which I am not subscribed so you
may want to keep me on the CC).

-- WXS
___
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: jpeg build problem

2011-01-06 Thread Wesley Shields
On Thu, Jan 06, 2011 at 12:00:03AM +0100, Radek Krej?a wrote:
> Hi, I have problem with build of jpeg from ports - latest ports, csup
> 10 minutes ago.
> 
> => Attempting to fetch from http://www.ijg.org/files/.
> jpegsrc.v8b.tar.gz
> 
> ===>  Vulnerability check disabled, database not found
> ===>  License check disabled, port has not defined LICENSE
> ===>  Extracting for jpeg-8_3
> => SHA256 Checksum OK for jpeg8b/jpegsrc.v8b.tar.gz.
> => SHA256 Checksum OK for jpeg8b/jpegexiforient.c.
> => SHA256 Checksum OK for jpeg8b/exifautotran.txt.
> cp: /usr/ports/distfiles//jpegexiforient.c: No such file or directory
> *** Error code 1

Wait for r1.159 of graphics/jpeg/Makefile to make it to the mirrors.
Should be fixed with that.

-- WXS
___
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: java/netbeans segfaults

2011-01-06 Thread Patrick Lamaiziere
Le Wed, 05 Jan 2011 14:13:58 +0100,
David Demelier  a écrit :

> Hello,

Hello,

> I just wanted to try netbeans here on FreeBSD :
> Is it possible that openjdk could be the problem?

Try it, here Netbeans 6.9.1 works fine with the Sun JDK (except the
profiler). I use it on 8.1 and -STABLE but on an i386 version, i don't
know for amd64. (could be an amd64 problem?)

pkg_info:
jdk-1.6.0.3p4_17Java Development Kit 1.6.0
netbeans-6.9.1  A full-featured integrated environment for Java

Regards.
___
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: drupal6

2011-01-06 Thread Marin Atanasov Nikolov
On Thu, Jan 6, 2011 at 1:44 PM, wen heping  wrote:
> Hi,

Hi,

>
>   Drupal7 released! Would you send a PR of repocopy of it ?

I was about of sending a request for adding Drupal 7 to the ports
tree, but I see you've already started the discussion :)

Anyone working on this one already?

Regards,
Marin
>
> wen
>
> 2011/1/3 wen heping :
>> It is time to send a PR to request repocopy drupal6 --> drupal7 .
>>
>> wen
>>
>> 2011/1/2 David Southwell ARPS :
 On 2 Jan 2011, at 15:40, David Southwell ARPS  wrote:
 > Any chance of a ports upgrade to drupal 6.20

 Someone submitted a pr for this earlier this morning. I'll take a look at
 it later

 Nick
>>> Thanks Nick
>>>
>>> You might also want to mention that Drupal7 is due for release on wednesday
>>> 5th January
>>>
>>> David
>>>
>>> Photographic Artist
>>> Permanent Installations & Design
>>> Creative Imagery and Advanced Digital Techniques
>>> High Dynamic Range Photography & Official Portraiture
>>> Combined darkroom & digital creations
>>> ___
>>> 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@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>



-- 
Marin Atanasov Nikolov

dnaeon AT gmail DOT com
daemon AT unix-heaven DOT org
http://www.unix-heaven.org/
___
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: drupal6

2011-01-06 Thread wen heping
Hi,

   Drupal7 released! Would you send a PR of repocopy of it ?

wen

2011/1/3 wen heping :
> It is time to send a PR to request repocopy drupal6 --> drupal7 .
>
> wen
>
> 2011/1/2 David Southwell ARPS :
>>> On 2 Jan 2011, at 15:40, David Southwell ARPS  wrote:
>>> > Any chance of a ports upgrade to drupal 6.20
>>>
>>> Someone submitted a pr for this earlier this morning. I'll take a look at
>>> it later
>>>
>>> Nick
>> Thanks Nick
>>
>> You might also want to mention that Drupal7 is due for release on wednesday
>> 5th January
>>
>> David
>>
>> Photographic Artist
>> Permanent Installations & Design
>> Creative Imagery and Advanced Digital Techniques
>> High Dynamic Range Photography & Official Portraiture
>> Combined darkroom & digital creations
>> ___
>> 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@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"