Re: kfreebsd-10 FTBFS with clang
Robert Millan r...@debian.org writes: clang (3.2-10) fails to build my kfreebsd-10 while gcc-4.6 builds it just fine. Is this a known problem somewhere? Found. See #721880. If you need a workaround, you can add -D__FreeBSD_kernel__ to CFLAGS in debian/patches/003_glibc_dev_aicasm.diff Seems to not be enough. I'll wait and try with the fixed clang in the evening. Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/871u53v99p@anonymous.siccegge.de
Re: kfreebsd-10 FTBFS with clang
Christoph Egger christ...@debian.org writes: Robert Millan r...@debian.org writes: clang (3.2-10) fails to build my kfreebsd-10 while gcc-4.6 builds it just fine. Is this a known problem somewhere? Found. See #721880. If you need a workaround, you can add -D__FreeBSD_kernel__ to CFLAGS in debian/patches/003_glibc_dev_aicasm.diff Seems to not be enough. I'll wait and try with the fixed clang in the evening. Seems to fail the same way after that patch as it fails with gcc-4.6 so I guess it's just HEAD being broken Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ob87tsim@anonymous.siccegge.de
Re: kfreebsd-10 FTBFS with clang
Christoph Egger: Christoph Egger christ...@debian.org writes: Robert Millan r...@debian.org writes: clang (3.2-10) fails to build my kfreebsd-10 while gcc-4.6 builds it just fine. Is this a known problem somewhere? Found. See #721880. If you need a workaround, you can add -D__FreeBSD_kernel__ to CFLAGS in debian/patches/003_glibc_dev_aicasm.diff Seems to not be enough. I'll wait and try with the fixed clang in the evening. Seems to fail the same way after that patch as it fails with gcc-4.6 so I guess it's just HEAD being broken Now that I see, it's clang-3.3 that I fixed. Not clang-3.2. I tried these combinations before writing my mail: - Patched clang-3.3 - Unpatched clang-3.3 with workaround and they both worked. Please can you check? (fixed clang-3.3 has been uploaded) -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52289ca8.90...@debian.org
Re: Bug#721886: FTBFS on kfreebsd-*: glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory
Michael Biebl: Source: libgtop2 Version: 2.28.5-1 Severity: serious User: debian-bsd@lists.debian.org Usertags: kfreebsd libgtop2 FTBFS [1] with the following error: make[4]: Entering directory `/«PKGBUILDDIR»/sysdeps/common' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. -I../../sysdeps/freebsd -I../../include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-kfreebsd-gnu/glib-2.0/include -D_FORTIFY_SOURCE=2 -Winline -Wall -std=gnu89 -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith-Wcast-align -Wsign-compare -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o error.lo error.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. -I../../sysdeps/freebsd -I../../include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-kfreebsd-gnu/glib-2.0/include -D_FORTIFY_SOURCE=2 -Winline -Wall -std=gnu89 -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c error.c -fPIC -DPIC -o .libs/error.o In file included from ../../glibtop.h:58:0, from ../../include/glibtop/error.h:30, from error.c:27: ../../sysdeps/freebsd/glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory #include nlist.h ^ Would be great if the kfreebsd porters have a look at this and provide a patch. -#include nlist.h +#include bsd/nlist.h then build-depend on libbsd-dev. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5228a35e.20...@debian.org
Re: Bug#721886: FTBFS on kfreebsd-*: glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory
Am 05.09.2013 17:29, schrieb Robert Millan: Michael Biebl: Source: libgtop2 Version: 2.28.5-1 Severity: serious User: debian-bsd@lists.debian.org Usertags: kfreebsd libgtop2 FTBFS [1] with the following error: make[4]: Entering directory `/«PKGBUILDDIR»/sysdeps/common' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. -I../../sysdeps/freebsd -I../../include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-kfreebsd-gnu/glib-2.0/include -D_FORTIFY_SOURCE=2 -Winline -Wall -std=gnu89 -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith-Wcast-align -Wsign-compare -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o error.lo error.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. -I../../sysdeps/freebsd -I../../include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-kfreebsd-gnu/glib-2.0/include -D_FORTIFY_SOURCE=2 -Winline -Wall -std=gnu89 -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c error.c -fPIC -DPIC -o .libs/error.o In file included from ../../glibtop.h:58:0, from ../../include/glibtop/error.h:30, from error.c:27: ../../sysdeps/freebsd/glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory #include nlist.h ^ Would be great if the kfreebsd porters have a look at this and provide a patch. -#include nlist.h +#include bsd/nlist.h Does that also work with FreeBSD so can be pushed upstream? Apparently libgtop2 has native FreeBSD support and I wonder if nslist.h is using a different location on FreeBSD. [1] seems to indicate that this is rather a bug in libbsd-dev. then build-depend on libbsd-dev. Afaics this should already been pulled in via libkvm-dev. Michael [1] https://lists.debian.org/debian-bsd/2011/07/msg00248.html -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#697015 closed by Mathieu Malaterre ma...@debian.org (Bug#697015: fixed in imagevis3d 3.0.0-2)
This is an automatic notification regarding your Bug report which was filed against the src:imagevis3d package: #697015: enable build on architectures without posix_fadvise() It has been closed by Mathieu Malaterre ma...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Mathieu Malaterre ma...@debian.org by replying to this email. -- 697015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: imagevis3d Source-Version: 3.0.0-2 We believe that the bug you reported is fixed in the latest version of imagevis3d, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 697...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre ma...@debian.org (supplier of updated imagevis3d package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 05 Sep 2013 17:01:08 +0200 Source: imagevis3d Binary: imagevis3d Architecture: source amd64 Version: 3.0.0-2 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Mathieu Malaterre ma...@debian.org Description: imagevis3d - desktop volume rendering application for large data Closes: 72193 693143 697015 713653 Changes: imagevis3d (3.0.0-2) unstable; urgency=low . * fix kfreebsd compilation. Closes: #697015 * fix compilation with missing jpeg symbol. Closes: #713653 * Fix openmp compilation. Closes: #72193 * Fix typos reported by lintian * Requires a g++ compiler post 4.6 release. Closes: #693143 Checksums-Sha1: c1071d827f7c08b220d2a9c6ecef4bc40db45903 2165 imagevis3d_3.0.0-2.dsc 28bed1fa900e76890a848d155468692e7b9e5f89 35270 imagevis3d_3.0.0-2.debian.tar.gz 0ec1169e892090f20a0defb68a2c538da838f86a 2557908 imagevis3d_3.0.0-2_amd64.deb Checksums-Sha256: fcb59ac1dd99e9201c7e33708fb3ac0ef7f2db99907c6a42fd62de8ce48b7ddd 2165 imagevis3d_3.0.0-2.dsc dd86fc60ea2820afd0728ce50394c05cde5d5d1e86e4490c574b9ae745055dea 35270 imagevis3d_3.0.0-2.debian.tar.gz 3be79eaede3d2406edc75b4abf81143f0b2823c800e87ca7f3379789ae36c060 2557908 imagevis3d_3.0.0-2_amd64.deb Files: 348d5c8ac71f6fa0c74b5b1e63eea7c2 2165 science optional imagevis3d_3.0.0-2.dsc cc343d494d171240ce3ad7ed0e92ed40 35270 science optional imagevis3d_3.0.0-2.debian.tar.gz 424f113057a49c5f30a2d2b5b901d8dd 2557908 science optional imagevis3d_3.0.0-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJSKK8aAAoJEAFx4YKK4JNFJ2QQAJY5EEwZVAfKbdtKl7K0JHZm pOdRnQzDaIp25LaTth/Sy6Wro1kVzrkmtFI8NFWu3HIR8jOpz4/+R4+BGsliLml5 s20svQrxkGlboyw4jF3pHPLXVtvv3SIlsvvaWWqdebaW5nd/Z0V+4ea1yHkQNbS2 wONA1VkaGKYGyauUV+HQwlzfesoymVi9B2N3iW2CUa9AmCNYBUoeVAqU89bKKvno YRkfbheLEg1SWWIZIgQGTxPMEcbSbc0iQj+N/1DdGSAp6is8f//l7H4MeMm0Dpan eWkO1GGIazE/h7xFjxqgDc6DYoZ1Uq5bnBqlbr/qG7QazqdcIOkNTiLc+Gjm7nHo XMW9DybUjPRMTGUXrXqma/9WAqlMnJM3HncqX/3rAG9uvOqPTvQ2/AnI5FmP4Wiq 7TP+iprV2O9Rb1deKhYN+QQiGFkWtE2C8DhNQ20SAJwl1n+b9yasrOvZ+0doj3QG qXRweOJTz1i6g04JL3+Rs2ocd9EIv7/6QVyjKqN85unr6kw972qMZAbMBkGdAPrI pvglqIA17THelRIqVZbIZh3ANI2e19o+8fGxrprjAxK4IgC3qXp6TuPiY/fQenBi 1M8aCwEhBnUxfTqGzQwUDKjgD+LgUFFf2V1yCBVBd1BCf//cFzNM0PzUu/fhRdJT I9M5Fi++iMEKjirmAkDO =lfA7 -END PGP SIGNATUREEnd Message--- ---BeginMessage--- Package: src:imagevis3d Version: 3.0.0-1 Severity: serious Tags: sid wheezy User: debian-bsd@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-bsd@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: g++ -c -DPACKAGE_MANAGER -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++0x -fno-strict-aliasing -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -D_REENTRANT -Wall -W -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/glibc-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4 -I. -I3rdParty/GLEW -IIO/3rdParty/boost -IIO/3rdParty/zlib -IBasics -IIO/exception -I/usr/include/lua5.2 -I/usr/X11R6/include -I. -o Build/objects/LargeFileFD.o Basics/LargeFileFD.cpp g++ -c -DPACKAGE_MANAGER -g -O2
Re: Bug#721886: FTBFS on kfreebsd-*: glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory
On Thu, Sep 5, 2013 at 17:50:18 +0200, Michael Biebl wrote: Am 05.09.2013 17:29, schrieb Robert Millan: Michael Biebl: Source: libgtop2 Version: 2.28.5-1 Severity: serious User: debian-bsd@lists.debian.org Usertags: kfreebsd libgtop2 FTBFS [1] with the following error: make[4]: Entering directory `/«PKGBUILDDIR»/sysdeps/common' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. -I../../sysdeps/freebsd -I../../include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-kfreebsd-gnu/glib-2.0/include -D_FORTIFY_SOURCE=2 -Winline -Wall -std=gnu89 -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith-Wcast-align -Wsign-compare -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o error.lo error.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. -I../../sysdeps/freebsd -I../../include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-kfreebsd-gnu/glib-2.0/include -D_FORTIFY_SOURCE=2 -Winline -Wall -std=gnu89 -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c error.c -fPIC -DPIC -o .libs/error.o In file included from ../../glibtop.h:58:0, from ../../include/glibtop/error.h:30, from error.c:27: ../../sysdeps/freebsd/glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory #include nlist.h ^ Would be great if the kfreebsd porters have a look at this and provide a patch. -#include nlist.h +#include bsd/nlist.h Does that also work with FreeBSD so can be pushed upstream? Apparently libgtop2 has native FreeBSD support and I wonder if nslist.h is using a different location on FreeBSD. In xorg-server added `pkg-config --cflags libbsd-overlay` to CPPFLAGS from debian/rules. Lets the code expecting bsd headers on bsd work without patching. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#721886: FTBFS on kfreebsd-*: glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory
Am 05.09.2013 19:53, schrieb Julien Cristau: On Thu, Sep 5, 2013 at 19:52:13 +0200, Michael Biebl wrote: Why do libc-dev and libbsd-dev have conflicting files in the first place and why not move just the conflicting (BSD) files to bsd/ ? I don't understand what you mean here, sorry... This question was not really targetted at you, but the BSD porters. You mentioned that the paths would conflict, I was asking why that is the case (apparently it didn't in the past) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bug#721776: libprelude: FTBFS on kfreebsd (FAIL: test-poll)
On Wed, Sep 4, 2013 at 02:04:10 +0200, Julien Cristau wrote: Source: libprelude Version: 1.0.0-11 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: block 712615 with -1 Hi, libprelude FTBFS on the kfreebsd buildds, see the build logs at https://buildd.debian.org/status/logs.php?pkg=libpreludever=1.0.0-11%2Bb1suite=sid I couldn't reproduce this on falla (ran make check a few times). Can a kfreebsd porter take a look? Thanks, Julien signature.asc Description: Digital signature
Re: Bug#721886: FTBFS on kfreebsd-*: glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory
Am 05.09.2013 19:29, schrieb Julien Cristau: On Thu, Sep 5, 2013 at 17:50:18 +0200, Michael Biebl wrote: Am 05.09.2013 17:29, schrieb Robert Millan: -#include nlist.h +#include bsd/nlist.h Does that also work with FreeBSD so can be pushed upstream? Apparently libgtop2 has native FreeBSD support and I wonder if nslist.h is using a different location on FreeBSD. In xorg-server added `pkg-config --cflags libbsd-overlay` to CPPFLAGS from debian/rules. Lets the code expecting bsd headers on bsd work without patching. That's confusing tbh. Why is libbsd-dev using different paths in the first place which requires such hacks? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bug#721886: FTBFS on kfreebsd-*: glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory
Am 05.09.2013 19:42, schrieb Julien Cristau: On Thu, Sep 5, 2013 at 19:40:18 +0200, Michael Biebl wrote: Am 05.09.2013 19:29, schrieb Julien Cristau: On Thu, Sep 5, 2013 at 17:50:18 +0200, Michael Biebl wrote: Am 05.09.2013 17:29, schrieb Robert Millan: -#include nlist.h +#include bsd/nlist.h Does that also work with FreeBSD so can be pushed upstream? Apparently libgtop2 has native FreeBSD support and I wonder if nslist.h is using a different location on FreeBSD. In xorg-server added `pkg-config --cflags libbsd-overlay` to CPPFLAGS from debian/rules. Lets the code expecting bsd headers on bsd work without patching. That's confusing tbh. Why is libbsd-dev using different paths in the first place which requires such hacks? Because the normal bsd paths would conflict with gnu libc-dev headers (maybe not for nlist.h, but for others). Why do libc-dev and libbsd-dev have conflicting files in the first place and why not move just the conflicting (BSD) files to bsd/ ? Apparently libgtop2 built just fine in the past with libbsd-dev, so this looks like a recent regression in that package. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bug#721886: FTBFS on kfreebsd-*: glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory
On Thu, Sep 5, 2013 at 19:52:13 +0200, Michael Biebl wrote: Why do libc-dev and libbsd-dev have conflicting files in the first place and why not move just the conflicting (BSD) files to bsd/ ? I don't understand what you mean here, sorry... Cheers, Julien signature.asc Description: Digital signature
Re: Bug#721886: FTBFS on kfreebsd-*: glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory
Julien Cristau: That's confusing tbh. Why is libbsd-dev using different paths in the first place which requires such hacks? Because the normal bsd paths would conflict with gnu libc-dev headers (maybe not for nlist.h, but for others). nlist.h is provided by libelf-dev and libelfg0-dev. If another package provides it, then it would have to conflict with libelf. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5228ea0e.7050...@debian.org
Re: Bug#721886: FTBFS on kfreebsd-*: glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory
Hi! On Thu, 2013-09-05 at 19:52:13 +0200, Michael Biebl wrote: Am 05.09.2013 19:42, schrieb Julien Cristau: On Thu, Sep 5, 2013 at 19:40:18 +0200, Michael Biebl wrote: Am 05.09.2013 19:29, schrieb Julien Cristau: On Thu, Sep 5, 2013 at 17:50:18 +0200, Michael Biebl wrote: Am 05.09.2013 17:29, schrieb Robert Millan: -#include nlist.h +#include bsd/nlist.h Please try to avoid this, which cannot be easily upstreamed, or if it can be upstreamed it unnecessarily pollutes the source. Does that also work with FreeBSD so can be pushed upstream? Apparently libgtop2 has native FreeBSD support and I wonder if nslist.h is using a different location on FreeBSD. In xorg-server added `pkg-config --cflags libbsd-overlay` to CPPFLAGS from debian/rules. Lets the code expecting bsd headers on bsd work without patching. Yes, that's the ideal solution, which generally avoids any patching. That's confusing tbh. Why is libbsd-dev using different paths in the first place which requires such hacks? Because the normal bsd paths would conflict with gnu libc-dev headers (maybe not for nlist.h, but for others). Why do libc-dev and libbsd-dev have conflicting files in the first place and why not move just the conflicting (BSD) files to bsd/ ? Most header files provided by libbsd-dev are overlays over the libc ones. For example strlcpy() and friends in bsd/string.h, or slightly different implementations like bsd/sys/queue.h. Then there's partial implementations like bsd/libutil.h which does not conflict with anything, but exposing it directly under /usr/include can confuse software that might assume functionality in libc just because the file is there, for example I think perl suffered from this in Debian at some point. And there's files already shipped by other pre-existing libraries, like bsd/nlist.h, provided by libelfg0-dev and libelf-dev. And no, Replaces does not cut it, because once you remove libbsd-dev then the other libraries will be missing the header. This was a mistake I corrected by namespacing it under bsd/ (the aforementioned link on the list). After all these cases, the only remaining non-conflicting headers are readpassphrase.h, vis.h and md5.h. For md5.h taking over the global namespace seems wrong (it probably belongs in the to-be-uploaded libmd), at which point having the remaining two namespaced seems safer, more future-proof and nicer to other projects. Apparently libgtop2 built just fine in the past with libbsd-dev, so this looks like a recent regression in that package. I went over any package explicitly declaring a Build-Depends on libbsd-dev when I did those changes, if libgtop2 is directly using stuff from libbsd-dev but not declaring it explicitly, that's hardly my fault? :) Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130905210820.ga23...@gaara.hadrons.org
Re: Roll call for porters of architectures in sid and testing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I am not currently a porter but I would like to be one for the architecture parisc/hppa. I currently have lots of parisc hardware (5 workstations and 4 servers), all currently running debian unstable from our own debian repository at www.parisc-linux.org. My involvement for debian-parisc so far: - - I was one of the initiators of parisc-linux port back in 1999. - - I have continuous worked on the ports since then. - - I'm currently one of the two official linux kernel maintainers for the parisc port at kernel.org. - - I've fixed quite some debian bugs reported for parisc in the past, including locking functions in gcc, KDE fixes, udev fixes and many more. - - I do have a strong linux developer background (C/C++, Assembler) and was formerly a developer at a major linux distributor. - - I'm maintaining the parisc-linux website and wikis. I am not a DD/DM but would like to become one. At last, I would be happy if parisc could become again a supported platform in the debian-ports repositories for the lifetime of Jessie. parisc was dropped with debian squeeze, because there were quite some stability issues with the Linux kernel at that time. Currently, upstream kernel 3.10 (stable) and kernel 3.11 do work reliable on all major machines. -- Helge Deller On 09/01/2013 09:33 AM, Niels Thykier wrote: Hi, As we announced in [LAST-BITS], we would like to get a better idea of that status of the ports, to make an informed decision about which port can be released with jessie. One of the steps is to get an overview of which of the porters are (still) active for each port. Once the results from the role-call are in, we will request other information about the status of the ports. In the meantime, feel free to update and collect info about the ports in the Debian wiki[WIKI]. If you are (or intend to become) an active porter for the lifetime of jessie, then please send a signed email explaining your involvement in the port to the Release Team debian-rele...@lists.debian.org before 1st of October 2013. Please explain the level of your involvement in the port. Feel free to use the following template as your reply: Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the jessie release: For ARCH, I - test (most|all) packages on this architecture - fix toolchain issues - triage arch-specific bugs - fix arch-related bugs - maintain buildds - ... I am a DD|I am a DM|I am not a DD/DM YOUR NAME Niels, on behalf of the release team [LAST-BITS] http://lists.debian.org/debian-devel-announce/2013/08/msg6.html [WIKI] https://wiki.debian.org/ArchiveQualification/Jessie -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSKPXJAAoJEIfJwVG1Hjhk1BsH/3nhr6HjGwpGnc6NnQxV3KA2 95LNye6Fi7aOh5NWGrjn8c3fmyJcoHdQFAMOIIulGZW6gLAeu1cX9Y16OAzMKP/H LTCvq0Q8yzl/U75+NKgz9rdozsXds43rmuyBJIZdypGXKjWEIkRz/ISzOL4+hdqh W+HoYWG/fqCsdhJMiUIIUQ7BW6kadJmoi3L5dZBBwLD9bHLY6lCIT4JEdDXKZrQ9 NPIYhEDfCIJl4yS982Q76SwqEkCYG84f0Egez66ADuazCjqGWkrI6EBzOeDvgV26 wdfekcU/Wx3LcFDBnd8clMG/MdmxxQu7c915Uv23DejD0QWVUlimFSTfWI8v59k= =htC/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5228f5c9.3050...@gmx.de
Re: kfreebsd-10 FTBFS with clang
Robert Millan r...@debian.org writes: Christoph Egger: Christoph Egger christ...@debian.org writes: Robert Millan r...@debian.org writes: clang (3.2-10) fails to build my kfreebsd-10 while gcc-4.6 builds it just fine. Is this a known problem somewhere? Found. See #721880. If you need a workaround, you can add -D__FreeBSD_kernel__ to CFLAGS in debian/patches/003_glibc_dev_aicasm.diff Seems to not be enough. I'll wait and try with the fixed clang in the evening. Seems to fail the same way after that patch as it fails with gcc-4.6 so I guess it's just HEAD being broken Now that I see, it's clang-3.3 that I fixed. Not clang-3.2. I tried these combinations before writing my mail: - Patched clang-3.3 - Unpatched clang-3.3 with workaround and they both worked. Please can you check? (fixed clang-3.3 has been uploaded) I have now fixed clang-3.3 -9 trying to build svn 255267 Still failing: clang -O2 -pipe -D_GNU_SOURCE -isystem /usr/include/freebsd -D__FreeBSD_kernel__ -I../../../dev/aic7xxx/aicasm -std=gnu99 -Qunused-arguments -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-pa rameter -Wcast-align -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c ../../../dev/aic7xxx/aicasm/aicasm.c In file included from ../../../dev/aic7xxx/aicasm/aicasm.c:63: ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:149:2: error: type name requires a specifier or qualifier TAILQ_ENTRY(critical_section) links; ^ ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:149:14: error: a parameter list without types is only allowed in a function definition TAILQ_ENTRY(critical_section) links; ^ ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:149:31: error: expected ';' at end of declaration list TAILQ_ENTRY(critical_section) links; ^ ; ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:168:2: error: type name requires a specifier or qualifier TAILQ_ENTRY(scope) scope_links; ^ ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:168:14: error: a parameter list without types is only allowed in a function definition TAILQ_ENTRY(scope) scope_links; ^ ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:168:20: error: expected ';' at end of declaration list TAILQ_ENTRY(scope) scope_links; ^ ; ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:169:2: error: type name requires a specifier or qualifier TAILQ_HEAD(, scope) inner_scope; ^ ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:169:13: error: expected parameter declarator TAILQ_HEAD(, scope) inner_scope; ^ ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:169:15: warning: type specifier missing, defaults to 'int' [-Wimplicit-int] TAILQ_HEAD(, scope) inner_scope; ^ ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:169:21: error: expected ';' at end of declaration list TAILQ_HEAD(, scope) inner_scope; ^ ; ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:178:1: warning: type specifier missing, defaults to 'int' [-Wimplicit-int] TAILQ_HEAD(cs_tailq, critical_section); ^~ ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:178:12: error: a parameter list without types is only allowed in a function definition TAILQ_HEAD(cs_tailq, critical_section); ^ ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:180:1: warning: type specifier missing, defaults to 'int' [-Wimplicit-int] TAILQ_HEAD(scope_tailq, scope); ^~ ../../../dev/aic7xxx/aicasm/aicasm_symbol.h:180:12: error: a parameter list without types is only allowed in a function definition TAILQ_HEAD(scope_tailq, scope); ^ ../../../dev/aic7xxx/aicasm/aicasm.c:124:2: warning: implicit declaration of function 'STAILQ_INIT' is invalid in C99 [-Wimplicit-function-declaration] STAILQ_INIT(patches); ^ ../../../dev/aic7xxx/aicasm/aicasm.c:125:2: warning: implicit declaration of function 'SLIST_INIT' is invalid in C99 [-Wimplicit-function-declaration] SLIST_INIT(search_path); ^ ../../../dev/aic7xxx/aicasm/aicasm.c:127:2: warning: implicit declaration of function 'TAILQ_INIT' is invalid in C99 [-Wimplicit-function-declaration] TAILQ_INIT(cs_tailq); ^ ../../../dev/aic7xxx/aicasm/aicasm.c:240:5: warning: implicit declaration of function 'SLIST_INSERT_HEAD' is invalid in C99 [-Wimplicit-function-declaration] SLIST_INSERT_HEAD(search_path, include_dir, ^ ../../../dev/aic7xxx/aicasm/aicasm.c:241:9: error: use of undeclared identifier 'links'; did you mean 'link'? links);
Re: Bug#721886: FTBFS on kfreebsd-*: glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory
tags 721886 + help thanks Am 05.09.2013 23:08, schrieb Guillem Jover: Hi! On Thu, 2013-09-05 at 19:52:13 +0200, Michael Biebl wrote: Am 05.09.2013 19:42, schrieb Julien Cristau: On Thu, Sep 5, 2013 at 19:40:18 +0200, Michael Biebl wrote: Am 05.09.2013 19:29, schrieb Julien Cristau: On Thu, Sep 5, 2013 at 17:50:18 +0200, Michael Biebl wrote: Am 05.09.2013 17:29, schrieb Robert Millan: -#include nlist.h +#include bsd/nlist.h Please try to avoid this, which cannot be easily upstreamed, or if it can be upstreamed it unnecessarily pollutes the source. Does that also work with FreeBSD so can be pushed upstream? Apparently libgtop2 has native FreeBSD support and I wonder if nslist.h is using a different location on FreeBSD. In xorg-server added `pkg-config --cflags libbsd-overlay` to CPPFLAGS from debian/rules. Lets the code expecting bsd headers on bsd work without patching. Yes, that's the ideal solution, which generally avoids any patching. [..] Thanks for the explanation. So I went ahead and used the CPPFLAGS override trick. libgtop2 still fails to build though: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. -I../../sysdeps/freebsd -I../../include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-kfreebsd-gnu/glib-2.0/include -isystem /usr/include/bsd -DLIBBSD_OVERLAY -Winline -Wall -std=gnu89 -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c procmem.c -fPIC -DPIC -o .libs/procmem.o In file included from procmem.c:36:0: /usr/include/sys/vnode.h:41:27: fatal error: sys/rangelock.h: No such file or directory #include sys/rangelock.h I don't really have any more time to investigate this any further, so it would be great if a kfreebsd porter could provide a *tested* patch, i.e. one which not only makes the package build successfully but ideally also has some runtime testing which ensures that the package actually works on kfreebsd. Apparently libgtop2 built just fine in the past with libbsd-dev, so this looks like a recent regression in that package. I went over any package explicitly declaring a Build-Depends on libbsd-dev when I did those changes, if libgtop2 is directly using stuff from libbsd-dev but not declaring it explicitly, that's hardly my fault? :) Fair enough. Will add an explicit build-depends with the next upload. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bug#721886: FTBFS on kfreebsd-*: glibtop_machine.h:26:19: fatal error: nlist.h: No such file or directory
Am 06.09.2013 02:49, schrieb Michael Biebl: /usr/include/sys/vnode.h:41:27: fatal error: sys/rangelock.h: No such file or directory #include sys/rangelock.h FWIW, this looks like a bug in sys/vnode.h or kfreebsd-kernel-headers. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bug#721776: libprelude: FTBFS on kfreebsd (FAIL: test-poll)
On 05/09/13 18:51, Julien Cristau wrote: I couldn't reproduce this on falla (ran make check a few times). Can a kfreebsd porter take a look? It built successfully for me locally in a wheezy chroot and twice in a sid chroot. It seems test-poll tries to listen on 127.0.0.1:12345 for TCP connections. So that can fail for a couple of reasons: 1. something else listening on that port already 2. connection in the past few minutes is in TIME_WAIT state - for some reason it still fails even though SO_REUSEADDR is requested here (and I think this is important - needs followup). There seems to be a race within the test program that can trigger this problem itself sometimes. Both of those produce exit status 77 and the test is 'skipped', leading to a successful build. If you are 'lucky', the test program gets a bit further, but (only sometimes) hits a different problem in test_socket_pair() expecting POLLHUP after shutdown returning status 2, which is treated as an actual failure. The test sometimes runs fully and passes - especially when running under ktrace. So I think there is a race for the connection over the loopback interface to be fully closed, before poll1_wait() is called. BTW it would be nice if failures in the testsuite would output the contents of libmissing/tests/test-suite.log into the build log. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/522938ef.1010...@pyro.eu.org
where is eclipse?
why eclipse is not in kfreebsd? it's the best ide, i think necessary...
