INDEX now builds successfully on 8.x
___ 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
lang/ruby19: ruby-1.9.3.392,1 is vulnerable: ** [check-vulnerable] Error code 1
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 === ruby-1.9.3.392,1 has known vulnerabilities: ruby-1.9.3.392,1 is vulnerable: Ruby -- XSS exploit of RDoc documentation generated by rdoc WWW: http://portaudit.FreeBSD.org/d3e96508-056b-4259-88ad-50dc8d1978a6.html ruby-1.9.3.392,1 is vulnerable: Ruby -- Denial of Service and Unsafe Object Creation Vulnerability in JSON WWW: http://portaudit.FreeBSD.org/c79eb109-a754-45d7-b552-a42099eb2265.html = Please update your ports tree and try again. *** [check-vulnerable] Error code 1 Stop in /usr/ports/lang/ruby19. *** [build] Error code 1 Stop in /usr/ports/lang/ruby19. ___ 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: lang/ruby19: ruby-1.9.3.392,1 is vulnerable: ** [check-vulnerable] Error code 1
On 9 March 2013 09:37, Hartmann, O. ohart...@zedat.fu-berlin.de 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 guess you sent it to -stable by mistake-- the knob you need is DISABLE_VULNERABILITIES=yes. I'm sure I don't need to lecture you on Be careful with this :) Chris ___ 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 ports you maintain which are out of date
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: FreeBSD ports you maintain which are out of date Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+- +-+- +-+-- devel/make++| 2.0 | 2.0.98.3 +-+- +-+- +-+-- If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. ___ 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
Re: lang/ruby19: ruby-1.9.3.392, 1 is vulnerable: ** [check-vulnerable] Error code 1
Am 03/09/13 10:38, schrieb Chris Rees: On 9 March 2013 09:37, Hartmann, O. ohart...@zedat.fu-berlin.de 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 guess you sent it to -stable by mistake-- the knob you need is DISABLE_VULNERABILITIES=yes. Yes, sorry for the mistake. Thanks for the hint. I'm sure I don't need to lecture you on Be careful with this :) Yes :-) Chris Regards, Oliver ___ 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: 9.1-RELEASE is out - is there any hope for an actual graphics/gimp-app?
On 03/09/13 01:23, Matthieu Volat wrote: On Tue, 26 Feb 2013 05:14:09 -0600 ajtiM lum...@gmail.com 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 OpenBSD Live CDs and OpenBSD has 2.8. I don't know how is with plugins on OpenBSD. Good news, everybody: many gnome-related ports where bumped to versions high enough to build babl, gegl and gimp in their latest versions. I suppose gimp 2.8 in port is near, but the impatient can more safely use the updated makefiles I updated a while ago : https://github.com/mazhe/gimp28_ports Do. Not. Want. Is there any way to prevent GIMP from upgrading when the update in ports is official? Disclaimer : you still have to revert to gimp 2.6 before tasks like portmaster -r if they impact babl/gegl/gimp, as older gimp do not build with older babl/gegl Maybe not with the latest versions, but I have gegl with Gimp 2.6 -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://copyfree.org/licenses/owl/license.txt ___ 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: 9.1-RELEASE is out - is there any hope for an actual graphics/gimp-app?
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'd say that the latter is preferrable since other people with the same need will get benefit. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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] x11/nvidia-driver fails on head @r248084
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 optimal).
* I use read-only local private mirrors of the SVN repos, so I was
unable to use svn diff to generate the diff and still get the added
files (AFAIK). So I used diff -ruN, then edited the result to
resemble the output of svn diff -- at least enough that patch -C
says it would apply to a pristine copy of x11/nvidia-driver properly.
* My ports working copy is @r313705; src is @248035.
Resulting uname output after successful build:
FreeBSD g1-235.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #832
r248033M/248035: Fri Mar 8 07:36:04 PST 2013
root@localhost:/usr/obj/usr/src/sys/CANARY i386
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Taliban: Evil men with guns afraid of truth from a 14-year old girl.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
Index: x11/nvidia-driver/Makefile
--- x11/nvidia-driver/Makefile 2013-03-09 07:11:03.0 -0800
+++ x11/nvidia-driver/Makefile 2013-03-09 06:48:18.0 -0800
@@ -86,6 +86,10 @@
PLIST_SUB+= LINUXBASE=${LINUXBASE} SHLIB_VERSION=${PORTVERSION} \
MODULESDIR=${MODULESDIR}
+. if ${OSVERSION} 128
+EXTRA_PATCHES+= ${FILESDIR}/r248084-patch-src-nv-freebsd.h
+EXTRA_PATCHES+= ${FILESDIR}/r248084-patch-src-nvidia_subr.c
+. endif
.if ${PORT_OPTIONS:MLINUX}
CONFLICTS= linux[-_]dri-[0-9]* linux-f10-dri-[0-9]*
Index: x11/nvidia-driver/files/r248084-patch-src-nv-freebsd.h
--- x11/nvidia-driver/files/r248084-patch-src-nv-freebsd.h 1969-12-31 16:00:00.0 -0800
+++ x11/nvidia-driver/files/r248084-patch-src-nv-freebsd.h 2013-03-09 06:39:54.0 -0800
@@ -0,0 +1,10 @@
+--- src/nv-freebsd.h.orig 2013-01-14 14:38:44.0 -0800
src/nv-freebsd.h 2013-03-09 06:36:23.0 -0800
+@@ -77,6 +77,7 @@
+ #include vm/vm_object.h
+ #include vm/pmap.h
+ #include vm/vm_map.h
++#include sys/rwlock.h
+ #include vm/vm_pager.h
+ #include vm/uma.h
+
Index: x11/nvidia-driver/files/r248084-patch-src-nvidia_subr.c
--- x11/nvidia-driver/files/r248084-patch-src-nvidia_subr.c 1969-12-31 16:00:00.0 -0800
+++ x11/nvidia-driver/files/r248084-patch-src-nvidia_subr.c 2013-03-09 06:48:53.0 -0800
@@ -0,0 +1,56 @@
+--- src/nvidia_subr.c.orig 2013-01-14 14:38:44.0 -0800
src/nvidia_subr.c 2013-03-09 06:47:05.0 -0800
+@@ -83,7 +83,7 @@
+ if (!sc-BAR_objects[i])
+ goto failed;
+
+-VM_OBJECT_LOCK(sc-BAR_objects[i]);
++VM_OBJECT_WLOCK(sc-BAR_objects[i]);
+ switch (i) {
+ case NV_GPU_BAR_INDEX_FB:
+ vm_object_set_memattr(sc-BAR_objects[i],
+@@ -95,7 +95,7 @@
+ VM_MEMATTR_UNCACHEABLE);
+ break;
+ }
+-VM_OBJECT_UNLOCK(sc-BAR_objects[i]);
++VM_OBJECT_WUNLOCK(sc-BAR_objects[i]);
+ }
+ }
+
+@@ -541,9 +541,9 @@
+ goto failed;
+ }
+
+-VM_OBJECT_LOCK(sc-UD_object);
++VM_OBJECT_WLOCK(sc-UD_object);
+ vm_object_set_memattr(sc-UD_object, VM_MEMATTR_UNCACHEABLE);
+-VM_OBJECT_UNLOCK(sc-UD_object);
++VM_OBJECT_WUNLOCK(sc-UD_object);
+ }
+
+ nv-flags |= NV_FLAG_OPEN;
+@@ -965,9 +965,9 @@
+ goto failed;
+ }
+
+-VM_OBJECT_LOCK(at-object);
++VM_OBJECT_WLOCK(at-object);
+ vm_object_set_memattr(at-object, attr);
+-VM_OBJECT_UNLOCK(at-object);
++VM_OBJECT_WUNLOCK(at-object);
+
+ *private = at;
+ SLIST_INSERT_HEAD(sc-alloc_list, at, list);
+@@ -1108,9 +1108,9 @@
+ goto failed;
+ }
+
+-VM_OBJECT_LOCK(at-object);
++VM_OBJECT_WLOCK(at-object);
+ vm_object_set_memattr(at-object, attr);
+-VM_OBJECT_UNLOCK(at-object);
++VM_OBJECT_WUNLOCK(at-object);
+
+ *private = at;
+ SLIST_INSERT_HEAD(sc-alloc_list, at, list);
pgp_xSNaSrcsx.pgp
Description: PGP signature
CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found
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 those ports with cc (which referes to CLANG 3.2) or USE_GCC=any, which should use the legacy compiler gcc or the installed lang/gcc (which seems to be outdated). Any attempt ends up with the very same error as shown below. This problem is sticky for a while now and I do not know what to do. I don't dare to delete the package in case the problem is then still present and I couldn't build the port again (I have to many scientific packages which do not compile properly with CLANG). Does anyone has an idea? Can I rescue the old installed lang/gcc as a package somehow to attempt a reinstallation in case deletion and recompiling the port will fail? Regards, Oliver [...] cc -O2 -pipe -O3 -march=native -I/usr/local/include -fno-strict-aliasing -o fixincl fixincl.o fixtests.o fixfixes.o server.o procopen.o fixlib.o fixopts.o ../libiberty/libiberty.a echo timestamp full-stamp srcdir=../.././../gcc-4.6.3/fixincludes /bin/sh ../.././../gcc-4.6.3/fixincludes/mkfixinc.sh x86_64-portbld-freebsd10.0 sed -e 's/@gcc_version@/4.6.3/' mkheaders.almost mkheadersT mv -f mkheadersT mkheaders gmake[3]: Leaving directory `/usr/ports/lang/gcc/work/build/build-x86_64-portbld-freebsd10.0/fixincludes' Configuring stage 1 in ./libcpp configure: creating cache ./config.cache checking build system type... x86_64-portbld-freebsd10.0 checking host system type... x86_64-portbld-freebsd10.0 checking target system type... x86_64-portbld-freebsd10.0 checking whether gmake sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for x86_64-portbld-freebsd10.0-gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking whether we are using the GNU C++ compiler... yes checking whether c++ accepts -g... yes checking for x86_64-portbld-freebsd10.0-ranlib... /usr/local/bin/ranlib checking how to run the C preprocessor... cpp checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking for aclocal... aclocal checking for autoconf... autoconf checking for autoheader... autoheader checking whether cc supports -W... yes checking whether cc supports -Wall... yes checking whether cc supports -Wwrite-strings... yes checking whether cc supports -Wmissing-format-attribute... yes checking whether cc supports -Wstrict-prototypes... yes checking whether cc supports -Wmissing-prototypes... yes checking whether cc supports -Wold-style-definition... yes checking whether cc supports -Wc++-compat... yes checking whether cc supports -pedantic -Wno-long-long... yes checking dependency style of cc... none configure: error: no usable dependency style found gmake[2]: *** [configure-stage1-libcpp] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build' gmake[1]: *** [stage1-bubble] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' gmake: *** [all] Error 2 *** [do-build] Error code 1 Stop in /usr/ports/lang/gcc. *** [build] Error code 1 Stop in /usr/ports/lang/gcc. === make failed for lang/gcc === Aborting update ___ 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: [RFC] lang/pypy
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 insufficient memory, expected at least 9227MiB RAM however my translation processes under -DPYPY_IGNORE_MEMORY take 2GB for normal binary and 2.5GB for sandboxed one so they aggregate 4.5GB to run parallel. This is far less than expected, no page thrashing, no hang, no stuttering. It does not matter being with pypy1.9 or pypy2.0 (yes, I built twice for 2.0 self hosting. Not tried with cPython.) So I think this warning is a bit excessive that makes everyone just put PYPY_IGNORE_MEMORY=1 in their make.conf. Just in my case. -- kuro ___ 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: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found
On Mar 9, 2013, at 16:36 , Hartmann, O. ohart...@zedat.fu-berlin.de 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 -pedantic -Wno-long-long... yes checking dependency style of cc... none configure: error: no usable dependency style found gmake[2]: *** [configure-stage1-libcpp] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build' gmake[1]: *** [stage1-bubble] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' gmake: *** [all] Error 2 *** [do-build] Error code 1 What is the actual error in the resulting config.log file? Unfortunately autoconf error message are virtually information-free… My first guess would be that you have non-default CFLAGS in your build environment, which confuse gcc's build stages. ___ 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
CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'
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 error is shown below. [...] === src (all) cc -O2 -pipe -O3 -march=native -fno-strict-aliasing -O3 -march=native -DNV_VERSION_STRING=\313.26\ -D__KERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O -mno-red-zone -mcmodel=kernel -UDEBUG -U_DEBUG -DNDEBUG -O3 -Wno-error=unused-variable -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I. -I@ -I@/contrib/altq -fno-common -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -c nvidia_ctl.c In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:127:2: error: implicit declaration of function 'rw_assert' is invalid in C99 [-Werror,-Wimplicit-function-declaration] VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:2: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:144:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:168:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:191:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(m-object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ 5 errors generated. *** [nvidia_ctl.o] Error code 1 Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-313.26/src. *** [all] Error code 1 Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-313.26. *** [do-build] Error code 1 Stop in /usr/ports/x11/nvidia-driver. *** [build] Error code 1 ___ 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: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'
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 (FreeBSD source): http://svnweb.freebsd.org/base/head/sys/kern/subr_witness.c?r1=244112r2=248093pathrev=248093 -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'
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? If I understand correctly, it should be fixed in r248061 (FreeBSD source): http://svnweb.freebsd.org/base/head/sys/kern/subr_witness.c?r1=244112r2=248093pathrev=248093 I'm on FreeBSD 10.0-CURRENT #0 r248061: Fri Mar 8 19:44:30 CET 2013 amd64. I just finished compiling r248108 - will reboot and see further. ___ 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: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'
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 your pr. Did you tried that? If I understand correctly, it should be fixed in r248061 (FreeBSD source): http://svnweb.freebsd.org/base/head/sys/kern/subr_witness.c?r1=244112r2=248093pathrev=248093 I'm on FreeBSD 10.0-CURRENT #0 r248061: Fri Mar 8 19:44:30 CET 2013 amd64. I just finished compiling r248108 - will reboot and see further. Err, I copypasted the yours revision, not the actual fix revision. Should read it should be fixed in r248093. Sorry. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found
Am 03/09/13 17:02, schrieb Dimitry Andric: On Mar 9, 2013, at 16:36 , Hartmann, O. ohart...@zedat.fu-berlin.de 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 -pedantic -Wno-long-long... yes checking dependency style of cc... none configure: error: no usable dependency style found gmake[2]: *** [configure-stage1-libcpp] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build' gmake[1]: *** [stage1-bubble] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' gmake: *** [all] Error 2 *** [do-build] Error code 1 What is the actual error in the resulting config.log file? Unfortunately autoconf error message are virtually information-free… My first guess would be that you have non-default CFLAGS in your build environment, which confuse gcc's build stages. Hello. CFLAGS settings are either root@thor:/usr/ports/lang/gcc # make -VCFLAGS -O2 -pipe -march=native -I/usr/local/include -fno-strict-aliasing or root@thor:/usr/ports/lang/gcc # make -VCFLAGS -O2 -pipe -O3 -march=native -I/usr/local/include -fno-strict-aliasing There are several config.log files: ./work/build/config.log ./work/build/lto-plugin/config.log ./work/build/gcc/config.log ./work/build/intl/config.log ./work/build/libcpp/config.log ./work/build/build-x86_64-portbld-freebsd10.0/libiberty/config.log ./work/build/build-x86_64-portbld-freebsd10.0/fixincludes/config.log ./work/build/libiberty/config.log Most recent touched is ./work/build/libcpp/config.log and since libcpp occurs in the error, it is the requested log file. I can not see anything useful in that file - I'm sorry :-( It is attached to this post. If you need further material, feel free to ask. By the way, I copied my /etc/make.conf and /etc/src.conf to another CURRENT machine which has the very same revision status (as well as the /usr/src AND /usr/ports, both boxes are up to date even with portmaster run this morning). I do not see the problem on this other machine. ___ 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: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'
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 PORTS_MODULES+=x11/nvidia-driver I answered to your pr. Did you tried that? If I understand correctly, it should be fixed in r248061 (FreeBSD source): http://svnweb.freebsd.org/base/head/sys/kern/subr_witness.c?r1=244112r2=248093pathrev=248093 I'm on FreeBSD 10.0-CURRENT #0 r248061: Fri Mar 8 19:44:30 CET 2013 amd64. I just finished compiling r248108 - will reboot and see further. Err, I copypasted the yours revision, not the actual fix revision. Should read it should be fixed in r248093. Sorry. 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. ___ 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: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'
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 http://docs.FreeBSD.org/cgi/mid.cgi?20130309153454.GS13861. Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpFcGnYnCrmD.pgp Description: PGP signature
Open office dev build failure
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 -- David Southwell ARPS AFIAP Photographic Arts Trained experienced competition judge, mentor, trainer, lecturer, Advanced digital techniques, international project photography ___ 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: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'
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 message I posted to ports@, a copy of which may be found at http://docs.FreeBSD.org/cgi/mid.cgi?20130309153454.GS13861. Peace, david Your patch fixed the problem for me. Thanks, oh ___ 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
Questions about ldconfig
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. My concern is that this will confuse ldconfig. Is my concern justified? ___ 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
Stop in /usr/ports/devel/qt4-corelib.
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_NO_USING_NAMESPACE -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS
-DQT3_SUPPORT -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_USE_ICU
-DHB_EXPORT=Q_CORE_EXPORT -DGNU_LIBICONV -DQT_NO_DEBUG -DQT_HAVE_MMX
-DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_HAVE_SSE3
-DQT_HAVE_SSSE3 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE
-I/usr/local/share/qt4/mkspecs/freebsd-g++ -I. -I../../include
-I../../include/QtCore -I.rcc/release-shared -Iglobal
-I../3rdparty/harfbuzz/src -I../3rdparty/md5 -I../3rdparty/md4
-I.moc/release-shared -I/usr/local/include/qt4 -I/usr/local/include -o
.obj/release-shared/qglobal.o global/qglobal.cpp
In file included from ../../include/QtCore/qatomic_arch.h:1,
from
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:227,
from ../../include/QtCore/qbasicatomic.h:1,
from
../../include/QtCore/../../src/corelib/thread/qatomic.h:46,
from ../../include/QtCore/qatomic.h:1,
from
../../include/QtCore/../../src/corelib/tools/qbytearray.h:45,
from ../../include/QtCore/qbytearray.h:1,
from
../../include/QtCore/../../src/corelib/kernel/qobject.h:49,
from ../../include/QtCore/qobject.h:1,
from
../../include/QtCore/../../src/corelib/thread/qthread.h:45,
from ../../include/QtCore/qthread.h:1,
from
../../include/QtCore/private/../../../src/corelib/thread/qthread_p.h:58,
from ../../include/QtCore/private/qthread_p.h:1,
from global/qglobal.cpp:52:
../../include/QtCore/../../src/corelib/arch/qatomic_arch.h:96:4: error:
#error Qt has not been ported to this architecture
In file included from ../../include/QtCore/qobjectdefs.h:1,
from
../../include/QtCore/../../src/corelib/kernel/qobject.h:47,
from ../../include/QtCore/qobject.h:1,
from
../../include/QtCore/../../src/corelib/thread/qthread.h:45,
from ../../include/QtCore/qthread.h:1,
from
../../include/QtCore/private/../../../src/corelib/thread/qthread_p.h:58,
from ../../include/QtCore/private/qthread_p.h:1,
from global/qglobal.cpp:52:
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:47: error:
'QT_BEGIN_HEADER' does not name a type
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:217: error:
expected constructor, destructor, or type conversion before 'const'
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:256: error:
function definition does not declare parameters
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:269: error:
function definition does not declare parameters
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:279: error:
expected class-name before '{' token
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h: In
constructor 'QArgumentT::QArgument(const char*, const T)':
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:282: error:
class 'QArgumentT' does not have any field named 'QGenericArgument'
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h: At global
scope:
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:287: error:
expected class-name before '{' token
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h: In
constructor 'QArgumentT::QArgument(const char*, T)':
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:290: error:
class 'QArgumentT' does not have any field named 'QGenericArgument'
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h: At global
scope:
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:297: error:
expected class-name before '{' token
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h: In
constructor 'QReturnArgumentT::QReturnArgument(const char*, T)':
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:300: error:
class 'QReturnArgumentT' does not have any field named
'QGenericReturnArgument'
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h: At global
scope:
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:304: error:
function definition does not declare parameters
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:476: error:
expected initializer before '' token
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:483: error:
ISO C++ forbids declaration of 'QMetaObject' with no type
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:483: error:
expected ';' before '*' token
../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:486: error:
'QMetaObject' has not been declared
Re: Questions about ldconfig
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 to libGmsh.so.0, which is a link to libGmsh.so.2.7, which is a link to libGmsh.so.2.7.0. My concern is that this will confuse ldconfig. Is my concern justified? It will not confuse the os at all but it will confuse ldconfig -r which is not able to list libraries ending with more that one digit. Which is just informational, so not a big deal except that bsd.port.mk is not clever enough to correctly deal with libraries. so only detection from ports will be confused, all the rest will work. https://wiki.freebsd.org/ports/fix_lib_depends for more details regards, Bapt pgpAhoehOAGx2.pgp Description: PGP signature
Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found
On Sat, Mar 09, 2013 at 05:02:56PM +0100, Dimitry Andric wrote: On Mar 9, 2013, at 16:36 , Hartmann, O. ohart...@zedat.fu-berlin.de 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 -pedantic -Wno-long-long... yes checking dependency style of cc... none configure: error: no usable dependency style found gmake[2]: *** [configure-stage1-libcpp] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build' gmake[1]: *** [stage1-bubble] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' gmake: *** [all] Error 2 *** [do-build] Error code 1 What is the actual error in the resulting config.log file? Unfortunately autoconf error message are virtually information-free? If you have a clang built FreeBSD-current, then it is no longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor the upcoming gcc-4.8.0. AFAICT, the problem is related to /usr/bin/cpp. I haven't tried earlier versions of gcc. -- Steve ___ 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
INDEX build failed for 8.x
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 ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 46: warning: duplicate script for target pbi-generate ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 47: warning: duplicate script for target pbi-generate ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 50: warning: duplicate script for target clean-pbi ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 51: warning: duplicate script for target clean-pbi ignored Done. make_index: emh-xemacs21-mule-1.14.1_13: no entry for /usr/ports/editors/semi-xemacs21-mule make_index: emh-xemacs21-mule-1.14.1_13: no entry for /usr/ports/editors/semi-xemacs21-mule make_index: wanderlust-xemacs21-mule-2.14.0_14: no entry for /usr/ports/editors/semi-xemacs21-mule make_index: wanderlust-xemacs21-mule-2.14.0_14: no entry for /usr/ports/editors/semi-xemacs21-mule Committers on the hook: amdmi3 bapt glewis marcus sunpoet wen Most recent SVN update was: Updating '.': Usecurity/vuxml/vuln.xml Deditors/semi-xemacs21-mule Ueditors/Makefile UMOVED Ujava/openjdk7/Makefile Djava/openjdk7/files/patch-bsd_close.c Djava/openjdk7/files/patch-PlainDatagramSocketImpl.c Djava/openjdk7/files/patch-zzz-7u11 Ujava/openjdk7/files/patch-set Unet/wireshark/Makefile Unet/wireshark/distinfo Unet/yate/Makefile Ux11/eaglemode/distinfo Ux11/eaglemode/pkg-plist Ux11/eaglemode/Makefile Uwww/siteatschool/Makefile Uwww/ilias3/Makefile Udevel/Makefile Udevel/p5-IO-Detect/Makefile Udevel/p5-Scalar-Does/pkg-plist Udevel/p5-Scalar-Does/Makefile Udevel/p5-Scalar-Does/distinfo Udevel/ros-laser_pipeline/Makefile Adevel/p5-Time-Mock Adevel/p5-Time-Mock/pkg-plist Adevel/p5-Time-Mock/Makefile Adevel/p5-Time-Mock/distinfo Adevel/p5-Time-Mock/pkg-descr Udevel/ros-image_common/Makefile Updated to revision 313792. ___ 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 ports you maintain which are out of date
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 mail to freebsd-ports-unsubscr...@freebsd.org
INDEX build failed for 8.x
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 ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 46: warning: duplicate script for target pbi-generate ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 47: warning: duplicate script for target pbi-generate ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 50: warning: duplicate script for target clean-pbi ignored /home/indexbuild/tindex/ports/Mk/bsd.pbi.mk, line 51: warning: duplicate script for target clean-pbi ignored Done. make_index: emh-xemacs21-mule-1.14.1_13: no entry for /usr/ports/editors/semi-xemacs21-mule make_index: emh-xemacs21-mule-1.14.1_13: no entry for /usr/ports/editors/semi-xemacs21-mule make_index: wanderlust-xemacs21-mule-2.14.0_14: no entry for /usr/ports/editors/semi-xemacs21-mule make_index: wanderlust-xemacs21-mule-2.14.0_14: no entry for /usr/ports/editors/semi-xemacs21-mule Committers on the hook: amdmi3 bapt beech glewis linimon marcus miwi sunpoet wen Most recent SVN update was: Updating '.': UU finance/frontaccounting/pkg-plist Ufinance/frontaccounting/Makefile UU finance/frontaccounting/distinfo Usecurity/vuxml/vuln.xml UMOVED UUPDATING Ushells/mksh/distinfo Ushells/mksh/Makefile Ugames/openlierox/Makefile Ugames/openlierox/distinfo Dgames/openlierox/files/patch-src-gusanos-blitters-mmx.h Agames/openlierox/files/patch-src-common-Debug_DumpCallstack.cpp Agames/openlierox/files/patch-src-common-SystemFunctions.cpp Agames/openlierox/files/patch-src-gusanos-objects_list.h Udatabases/py-dbf/Makefile Udatabases/py-dbf/distinfo UU x11/fbpanel/pkg-plist UU x11/fbpanel/Makefile Uwww/zenphoto/Makefile Uwww/zenphoto/distinfo Uwww/zenphoto/pkg-plist Awww/p5-HTTP-CookieJar Awww/p5-HTTP-CookieJar/pkg-plist Awww/p5-HTTP-CookieJar/Makefile Awww/p5-HTTP-CookieJar/distinfo Awww/p5-HTTP-CookieJar/pkg-descr Uwww/Makefile Uwww/p5-HTTP-Tiny/Makefile Uwww/p5-HTTP-Tiny/distinfo Udevel/make++/Makefile Udevel/py-shapely/pkg-plist Udevel/py-shapely/Makefile Udevel/py-shapely/distinfo Updated to revision 313805. ___ 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
VirtualBox broken by recent commit -248084
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=revisionrevision=248084 === Registering installation for virtualbox-ose-kmod-4.2.6_1 Installing virtualbox-ose-kmod-4.2.6_1... done === Cleaning for virtualbox-ose-kmod-4.2.6_1 [root@FBSD10 /usr/ports/emulators/virtualbox-ose-kmod]# kldload vboxdrv.ko kldload: can't load vboxdrv.ko: Exec format error From commit log: The KPI results heavilly broken by this commit. Thirdy part ports must be updated accordingly (I can think off-hand of VirtualBox, for example). ___ 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
nvidia-driver broken by recent commit - 248084
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=revisionrevision=248084 From commit log:The KPI results heavilly broken by this commit. Thirdy part ports must be updated accordingly (I can think off-hand of VirtualBox, for example). root@FBSD10 /usr/ports/x11/nvidia-driver]# make clean === Cleaning for nvidia-driver-310.32 [root@FBSD10 /usr/ports/x11/nvidia-driver]# make install clean === License NVIDIA accepted by the user === Found saved configuration for nvidia-driver-304.64 === nvidia-driver-310.32 depends on file: /usr/local/sbin/pkg - found === Extracting for nvidia-driver-310.32 = SHA256 Checksum OK for NVIDIA-FreeBSD-x86_64-310.32.tar.gz. === Patching for nvidia-driver-310.32 === Applying extra patch /usr/ports/x11/nvidia-driver/files/r246085-patch-src-nvidia_linux.c === nvidia-driver-310.32 depends on file: /usr/local/libdata/pkgconfig/xorg-server.pc - found === nvidia-driver-310.32 depends on shared library: GL.1 - found === Configuring for nvidia-driver-310.32 === Building for nvidia-driver-310.32 === src (all) @ - /usr/src/sys machine - /usr/src/sys/amd64/include x86 - /usr/src/sys/x86/include awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\310.32\ -D__KERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O -mno-red-zone -mcmodel=kernel -UDEBUG -U_DEBUG -DNDEBUG -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I. -I@ -I@/contrib/altq -fno-common -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -c nvidia_ctl.c In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:127:2: error: implicit declaration of function 'rw_assert' is invalid in C99 [-Werror,-Wimplicit-function-declaration] VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:2: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:144:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:168:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ In file included from nvidia_ctl.c:14: In file included from ./nv-freebsd.h:77: @/vm/vm_pager.h:191:2: error: use of undeclared identifier 'RA_WLOCKED' VM_OBJECT_ASSERT_WLOCKED(m-object); ^ @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' rw_assert((object)-lock, RA_WLOCKED) ^ 5 errors generated. *** [nvidia_ctl.o] Error code 1 Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-310.32/src. *** [all] Error code 1 Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-310.32. *** [do-build] Error code 1 Stop in /usr/ports/x11/nvidia-driver. *** [install] Error code 1 Stop in /usr/ports/x11/nvidia-driver. [root@FBSD10 /usr/ports/x11/nvidia-driver]# ___ 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
