x11/nvidia-driver: fails to build: @/sys/filedesc.h:37:10: fatal error: 'opt_capsicum.h' file not found

2014-10-05 Thread O. Hartmann
Most recent CURRENT (Revision: 272559) is unwilling to compile the port
x11/nvidia-driver. The error occurs with all avaiable nVidia BLOBs.

Sorry for the messy output, claws-mail seems to kill the line terminating 
character.

I also filed a PR to make this recorded:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194148


[...]
cc  -O2 -pipe -O3 -O3 -pipe -march=native -fno-strict-aliasing -O3 -O3 -pipe
-march=native  -DNV_VERSION_STRING=\343.22\ -D__KERNEL__ -DNVRM 
-Wno-unused-function
-Wuninitialized -O2 -fno-strict-aliasing -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-omit-leaf-frame-pointer  
-mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float  -fno-asynchronous-unwind-tables
-ffreestanding -fstack-protector -mno-aes -mno-avx -Qunused-arguments 
-std=iso9899:1999
-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
-Wno-error-unused-function  -mno-aes -mno-avx -Qunused-arguments -c 
nvidia_acpi.c In file
included from nvidia_acpi.c:14: In file included from ./nv-freebsd.h:89:
@/sys/filedesc.h:37:10: fatal error: 'opt_capsicum.h' file not found 
#include opt_capsicum.h ^ 1 error generated. *** Error code 1

Stop.
make[6]: stopped
in 
/usr/obj/usr/src/sys/HERMANN/usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-343.22/src
*** Error code 1


Regards,

Oliver


signature.asc
Description: PGP signature


Re: py-imaging vs. py-pillow

2014-10-05 Thread Stefan Ehmann

On 03.10.2014 13:37, William Grzybowski wrote:

Coexist how? They are essentially the same package. I don't see how
thats possible.

py-imaging is deprecated, they should be switched to py-pillow and thats it.


Thanks for taking care of this issue!
___
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 you maintain which are out of date

2014-10-05 Thread portscout
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
+-+
comms/ser2net   | 2.9.1   | 2.10.0
+-+
editors/vile| 9.8n| 9.8o
+-+
editors/xvile   | 9.8n| 9.8o
+-+
multimedia/lsdvd| 0.16| 0.17
+-+


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

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


Re: x11/nvidia-driver: fails to build: @/sys/filedesc.h:37:10: fatal error: 'opt_capsicum.h' file not found

2014-10-05 Thread David Wolfskill
On Sun, Oct 05, 2014 at 10:02:15AM +0200, O. Hartmann wrote:
 Most recent CURRENT (Revision: 272559) is unwilling to compile the port
 x11/nvidia-driver. The error occurs with all avaiable nVidia BLOBs.
 
 Sorry for the messy output, claws-mail seems to kill the line terminating 
 character.
 
 I also filed a PR to make this recorded:
 
 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194148
 
 
 [...]
 cc  -O2 -pipe -O3 -O3 -pipe -march=native -fno-strict-aliasing -O3 -O3 -pipe
 -march=native  -DNV_VERSION_STRING=\343.22\ -D__KERNEL__ -DNVRM 
 -Wno-unused-function
 -Wuninitialized -O2 -fno-strict-aliasing -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-omit-leaf-frame-pointer  
 -mcmodel=kernel
 -mno-red-zone -mno-mmx -mno-sse -msoft-float  -fno-asynchronous-unwind-tables
 -ffreestanding -fstack-protector -mno-aes -mno-avx -Qunused-arguments 
 -std=iso9899:1999
 -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
 -Wno-error-unused-function  -mno-aes -mno-avx -Qunused-arguments -c 
 nvidia_acpi.c In file
 included from nvidia_acpi.c:14: In file included from ./nv-freebsd.h:89:
 @/sys/filedesc.h:37:10: fatal error: 'opt_capsicum.h' file not found 
 #include opt_capsicum.h ^ 1 error generated. *** Error code 1
 
 Stop.
 make[6]: stopped
 in 
 /usr/obj/usr/src/sys/HERMANN/usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-343.22/src
 *** Error code 1
 ...

I also see this, and note that it is quite similar to the failure I saw
yesterday during make buildworld for head@272513; in that case I saw:

...
--- lib/libkvm__L ---
In file included from /usr/src/lib/libkvm/kvm_minidump_i386.c:34:
In file included from /usr/obj/usr/src/tmp/usr/include/sys/user.h:49:
In file included from /usr/obj/usr/src/tmp/usr/include/sys/proc.h:45:
/usr/obj/usr/src/tmp/usr/include/sys/filedesc.h:36:10: fatal error: 
'opt_capsicum.h' file not found
#include opt_capsicum.h
 ^
--- lib/libmd__L ---
...

while for nvidia-driver, I'm seeing:

: opt_global.h
clang -O2 -pipe -fno-strict-aliasing  -DNV_VERSION_STRING=\331.67\ 
-D__KERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O -UDEBUG -U_DEBUG 
-DNDEBUG -Werror -D_KERNEL -DKLD_MODULE -nostdinc  -I. -I. -I@ -I@/contrib/altq 
-fno-common   -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector 
-mno-aes -mno-avx -Qunused-arguments -std=iso9899:1999 -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 -Wno-error-unused-function  -mno-aes -mno-avx 
-Qunused-arguments -c nvidia_acpi.c
In file included from nvidia_acpi.c:14:
In file included from ./nv-freebsd.h:89:
@/sys/filedesc.h:37:10: fatal error: 'opt_capsicum.h' file not found
#include opt_capsicum.h
 ^
1 error generated.
*** Error code 1
...

(Yes, I'll plan on updating the PR, after I flip back to stable/9; I've
needed to run service netif restart wlan0 way too many times while
trying to write email while running head on my laptop.)

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Taliban: Evil cowards with guns afraid of truth from a 14-year old girl.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgpwo2esCxAa0.pgp
Description: PGP signature


Release generation failure from 10.0-RELEASE to RELENG_10_0

2014-10-05 Thread Egoitz Aurrekoetxea
Good afternoon,

Have found what seems to be a bug in the generate-release.sh script. When 
running the command for example : 

sh generate-release.sh releng/10.0 /expert/release-generada

it fails when stats building pkg in the chrooted env. I think this is because 
in the chroot env are not created the shared library 
cache hint files…. so it seems to be solved when modifying the script int he 
following way : 

--- /root/generate-release.sh-defecto   2014-10-05 08:30:49.0 +0200
+++ /usr/src/release/generate-release.sh2014-10-05 08:30:57.0 
+0200
@@ -108,6 +108,8 @@
 if [ -d ${CHROOTDIR}/usr/doc ]; then 
cp /etc/resolv.conf ${CHROOTDIR}/etc/resolv.conf
 
+   ${CHROOT_CMD} /etc/rc.d/ldconfig onerestart
+
# Install docproj to build release documentation
${CHROOT_CMD} /bin/sh -c \
'make -C /usr/ports/textproc/docproj \

I think this is similar as reported in ports/186554 bug.

Could someone say if this should had been solved in another way?. I think this 
is correct. Isn’t it?.

Best 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


QAT script or Finding a list of dependent ports

2014-10-05 Thread Muhammad Moinur Rahman
Hi,

I was planning to setup a Quality Assurance Tinderbox definitely from a
port maintainer's point of view. Are those scripts available in open or is
it restricted.

If it is restricted can anyone point some light towards finding a list of
dependent ports. Like say I am working on port X and I need to know which
ports depend on port X. In a short I need the reverse of make
all-depends-list.

Thanks in advance.

BR,
Muhammad
___
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: QAT script or Finding a list of dependent ports

2014-10-05 Thread Matthew Seaman
On 06/10/2014 06:02, Muhammad Moinur Rahman wrote:
 If it is restricted can anyone point some light towards finding a list of
 dependent ports. Like say I am working on port X and I need to know which
 ports depend on port X. In a short I need the reverse of make
 all-depends-list.

This information is distilled into the ports INDEX, and you can extract
all the ports that depend on your port of interest by a fairly simple
combination of grep(1) and cut(1).  It's slightly harder if you need to
distinguish between runtime and buildtime dependencies, but only very
slightly.  See PORTINDEX(5) for the format of the file.

The biggest problem with this approach is accounting for local OPTIONS
settings, which can make significant changes to the dependency tree of
many ports.  ie. you should build your own INDEX for best results.
(Here I make the obligatory plug for ports-mgmt/p5-FreeBSD-Portindex,
which I think is a great solution to doing that efficiently, but I'm
clearly biased because I wrote it.)

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.

PGP: http://www.infracaninophile.co.uk/pgpkey
JID: matt...@infracaninophile.co.uk



signature.asc
Description: OpenPGP digital signature