nvidia-driver broken by recent commit - 248084

2013-03-09 Thread AN
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 /usr/ports/x11/nvidia-driver is broken, probably by this commit: http://svnweb.freebsd.org/base?view=revision&revision=248084 From commit log:"The KPI

VirtualBox broken by recent commit -248084

2013-03-09 Thread AN
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Virtualbox was broken by this commit: http://svnweb.freebsd.org/base?view=revision&revision=248084 ===> Registering installation for virtualbox-ose-km

INDEX build failed for 8.x

2013-03-09 Thread indexbuild
INDEX build failed with errors: Generating INDEX-8 - please wait.."/home/indexbuild/tindex/ports/Mk/bsd.pbi.mk", line 20: warning: duplicate script for target "check-pbimanager" ignored "/home/indexbuild/tindex/ports/Mk/bsd.pbi.mk", line 45: warning: duplicate script for target "pbi-generate" ig

Re: FreeBSD ports you maintain which are out of date

2013-03-09 Thread Mark Linimon
On Sat, Mar 09, 2013 at 08:33:06PM +1030, Gavin McDonald wrote: > I'm happy to take maintainership of this one. Done, thanks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any

INDEX build failed for 8.x

2013-03-09 Thread indexbuild
INDEX build failed with errors: Generating INDEX-8 - please wait.."/home/indexbuild/tindex/ports/Mk/bsd.pbi.mk", line 20: warning: duplicate script for target "check-pbimanager" ignored "/home/indexbuild/tindex/ports/Mk/bsd.pbi.mk", line 45: warning: duplicate script for target "pbi-generate" ig

Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

2013-03-09 Thread Steve Kargl
On Sat, Mar 09, 2013 at 05:02:56PM +0100, Dimitry Andric wrote: > On Mar 9, 2013, at 16:36 , "Hartmann, O." wrote: > > I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0 > > r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build > > either lang/gcc or lang/gcc46 wit

Re: Questions about ldconfig

2013-03-09 Thread Baptiste Daroussin
On Sat, Mar 09, 2013 at 03:21:00PM -0600, Stephen Montgomery-Smith wrote: > I am looking at committing a port which creates the following files: > > /usr/local/lib/libGmsh.so > /usr/local/lib/libGmsh.so.0 > /usr/local/lib/libGmsh.so.2.7 > /usr/local/lib/libGmsh.so.2.7.0 > > libGmsh.so is a link t

Stop in /usr/ports/devel/qt4-corelib.

2013-03-09 Thread Per olof Ljungmark
FreeBSD 9.1-STABLE #0 r248028 Ports tree from an hour ago The error is g++ -c -O2 -pipe -fno-strict-aliasing -pthread -I/usr/local/include/glib-2.0 -I/usr/local/include -O2 -fvisibility=hidden -fvisibility-inlines-hidden -Wall -W -pthread -D_THREAD_SAFE -fPIC -DQT_SHARED -DQT_BUILD_CORE_LIB -DQT

Questions about ldconfig

2013-03-09 Thread Stephen Montgomery-Smith
I am looking at committing a port which creates the following files: /usr/local/lib/libGmsh.so /usr/local/lib/libGmsh.so.0 /usr/local/lib/libGmsh.so.2.7 /usr/local/lib/libGmsh.so.2.7.0 libGmsh.so is a link to libGmsh.so.0, which is a link to libGmsh.so.2.7, which is a link to libGmsh.so.2.7.0. M

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

2013-03-09 Thread Hartmann, O.
Am 03/09/13 18:07, schrieb David Wolfskill: > On Sat, Mar 09, 2013 at 06:06:05PM +0100, Hartmann, O. wrote: >> ... >> No, it isn't. Same error, system is at revision: >> FreeBSD 10.0-CURRENT #1 r248106: Sat Mar 9 16:44:58 CET 2013 amd64 >> >> The error is the same. >> ... > > Please see the messa

Open office dev build failure

2013-03-09 Thread David Southwell
Hi Getting following 6 module(s): mdds rhino hyphen nss jpeg need(s) to be rebuilt reasons ERROR: 65280 occured whilst making /usr/ports/editors/openoffice-3-devel/work/ooo/main/rhino (Above line repeated for each above mentioned modules Thanks in advance for help to solve this one David --

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

2013-03-09 Thread David Wolfskill
On Sat, Mar 09, 2013 at 06:06:05PM +0100, Hartmann, O. wrote: > ... > No, it isn't. Same error, system is at revision: > FreeBSD 10.0-CURRENT #1 r248106: Sat Mar 9 16:44:58 CET 2013 amd64 > > The error is the same. > ... Please see the message I posted to ports@, a copy of which may be found at

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

2013-03-09 Thread Hartmann, O.
Am 03/09/13 17:46, schrieb Ruslan Makhmatkhanov: > Hartmann, O. wrote on 09.03.2013 20:45: >> Am 03/09/13 17:38, schrieb Ruslan Makhmatkhanov: >>> Hartmann, O. wrote on 09.03.2013 20:31: I rebuild the kernel module for x11/nvidia-driver on a regular basis via /etc/src.conf setting of

Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

2013-03-09 Thread Hartmann, O.
Am 03/09/13 17:02, schrieb Dimitry Andric: > On Mar 9, 2013, at 16:36 , "Hartmann, O." wrote: >> I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0 >> r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build >> either lang/gcc or lang/gcc46 with the very same error sh

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

2013-03-09 Thread Ruslan Makhmatkhanov
Hartmann, O. wrote on 09.03.2013 20:45: Am 03/09/13 17:38, schrieb Ruslan Makhmatkhanov: Hartmann, O. wrote on 09.03.2013 20:31: I rebuild the kernel module for x11/nvidia-driver on a regular basis via /etc/src.conf setting of PORTS_MODULES+=x11/nvidia-driver I answered to yo

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

2013-03-09 Thread Hartmann, O.
Am 03/09/13 17:38, schrieb Ruslan Makhmatkhanov: > Hartmann, O. wrote on 09.03.2013 20:31: >> I rebuild the kernel module for x11/nvidia-driver on a regular basis via >> /etc/src.conf setting of >> >> PORTS_MODULES+=x11/nvidia-driver > > I answered to your pr. Did you tried that? >

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

2013-03-09 Thread Ruslan Makhmatkhanov
Hartmann, O. wrote on 09.03.2013 20:31: I rebuild the kernel module for x11/nvidia-driver on a regular basis via /etc/src.conf setting of PORTS_MODULES+=x11/nvidia-driver I answered to your pr. Did you tried that? """ If I understand correctly, it should be fixed in r248061 (F

CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

2013-03-09 Thread Hartmann, O.
I rebuild the kernel module for x11/nvidia-driver on a regular basis via /etc/src.conf setting of PORTS_MODULES+=x11/nvidia-driver but this time, the port gets deleted and - fails to compile (tried 310.32 and 313.26, the latter worked for me before very well). The compilation err

Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

2013-03-09 Thread Dimitry Andric
On Mar 9, 2013, at 16:36 , "Hartmann, O." wrote: > I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0 > r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build > either lang/gcc or lang/gcc46 with the very same error shown below. … > checking whether cc supports -ped

Re: [RFC] lang/pypy

2013-03-09 Thread poyopoyo
Hi, good work, David. It compiles, packages and works flawlessly here for replacement of 1.9 so far for a week. On my compile box, amd64/Athlon64 5050e 2.6GHz 2 core/8GB, memory requirement for translation processes is far less than warning shown. It prevents build with | warn: this system has in

CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

2013-03-09 Thread Hartmann, O.
I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0 r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build either lang/gcc or lang/gcc46 with the very same error shown below. The box is compiled with CLANG (buildworld/kernel). It doesn't matter whether I compile tho

[PATCH] x11/nvidia-driver fails on head @r248084

2013-03-09 Thread David Wolfskill
During my daily update of the head slice on my laptop, I found that changes made in r248084 broke x11/nvidia-driver. The attached patch worked for me. Caveats: * I'm a hacker, not a developer. Don't assume I know what I'm doing. * I may have got the OSVERSION number wrong (or at least "not opt

Re: 9.1-RELEASE is out - is there any hope for an actual graphics/gimp-app?

2013-03-09 Thread Boris Samorodov
09.03.2013 15:42, Joseph A. Nagy, Jr пишет: > Do. Not. Want. Is there any way to prevent GIMP from upgrading when the > update in ports is official? Yes, many: 1. Do not update the portstree. ;-) 2. Create your private port for gimp26. 3. Create, submit and maintain a new port graphics/gimp26. I

Re: 9.1-RELEASE is out - is there any hope for an actual graphics/gimp-app?

2013-03-09 Thread Joseph A. Nagy, Jr
On 03/09/13 01:23, Matthieu Volat wrote: On Tue, 26 Feb 2013 05:14:09 -0600 ajtiM wrote: [...] Search in mailing list about GIMP 2.8 and you should find a response from maintainer. As I remember we will wait on the 2.8 still... BTW; I use live linux cd and it work very good. There are also O

Re: lang/ruby19: ruby-1.9.3.392, 1 is vulnerable: ** [check-vulnerable] Error code 1

2013-03-09 Thread Hartmann, O.
Am 03/09/13 10:38, schrieb Chris Rees: > On 9 March 2013 09:37, Hartmann, O. wrote: >> I try to compile port lang/ruby19 and I always get on a FreeBSD >> 9.1-STABLE box the following error message, which is obviously triggered >> by some port auditing - but I do not find the "knob" to switch it of

RE: FreeBSD ports you maintain which are out of date

2013-03-09 Thread Gavin McDonald
I'm happy to take maintainership of this one. Cheers Gav... > -Original Message- > From: owner-freebsd-po...@freebsd.org [mailto:owner-freebsd- > po...@freebsd.org] On Behalf Of portsc...@portscout.freebsd.org > Sent: Thursday, 7 March 2013 12:15 AM > To: po...@freebsd.org > Subject: Fr

Re: lang/ruby19: ruby-1.9.3.392,1 is vulnerable: ** [check-vulnerable] Error code 1

2013-03-09 Thread Chris Rees
On 9 March 2013 09:37, Hartmann, O. wrote: > I try to compile port lang/ruby19 and I always get on a FreeBSD > 9.1-STABLE box the following error message, which is obviously triggered > by some port auditing - but I do not find the "knob" to switch it off. > > Can someone give a hint, please? I g

lang/ruby19: ruby-1.9.3.392,1 is vulnerable: ** [check-vulnerable] Error code 1

2013-03-09 Thread Hartmann, O.
I try to compile port lang/ruby19 and I always get on a FreeBSD 9.1-STABLE box the following error message, which is obviously triggered by some port auditing - but I do not find the "knob" to switch it off. Can someone give a hint, please? Regards, Oliver ===> Cleaning for ruby-1.9.3.392,1 =

INDEX now builds successfully on 8.x

2013-03-09 Thread indexbuild
___ 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"