conflict with ioctl.h and ioccom.h?
Hello all, While going through some of the packages in NOTES [1] I noticed that the darkice package is FTBFS again after being claimed fixed. It used to be FTBFS because of bad build-deps but now it is something different: from the build log [2]: g++ -DHAVE_CONFIG_H -I. -I. -I.-O2 -pedantic -Wall -g -Wall -O2 -c -o OssDspSource.o `test -f 'OssDspSource.cpp' || echo './'`OssDspSource.cpp /usr/include/sys/ioctl.h:42: error: declaration of 'int ioctl(int, long unsigned int, ...) throw ()' throws different exceptions /usr/include/sys/ioccom.h:66: error: from previous declaration 'int ioctl(int, long unsigned int, ...)' make[3]: *** [OssDspSource.o] Error 1 , which belongs to glibc, includes which in turn includes belonging to kfreebsd-kernel-headers. It seems that these two header files are in conflict. Any ideas why? [1] http://glibc-bsd.alioth.debian.org/NOTES [2] http://experimental.ftbfs.de/fetch.php?&pkg=darkice&ver=0.17.1-3&arch=kfreebsd-i386&stamp=1162652787&file=log&as=raw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: conflict with ioctl.h and ioccom.h?
Hi. While going through some of the packages in NOTES [1] I noticed that the darkice package is FTBFS again after being claimed fixed. It used to be FTBFS because of bad build-deps but now it is something different: from the build log [2]: It looks like we are currently doing the same thing :-( Look at r1727 on http://svn.debian.org/wsvn/glibc-bsd/?op=log&rev=0&sc=0&isdir=1 My working copy of "claimed fixed" is currently: allegro4.1_4.1.15-6+kbsdBTS darkice_0.16-1+kbsd kfreebsd-kernel-headers dictd_1.10.2-3+cfg fixed, should not be in unreleased gamin_0.1.7-3+kbsd BTS glew_1.3.4-3+kbsd BTS gnome-applets_2.10.1-5+kbsd gst-plugins-base0.10_0.10.10-1+kbsd fixed with new cdparanoia gtk-engines_0.12-8.1+libtool kaquarium_1.0-beta-5+libtool+b1 BTS kde-style-lipstik_2.2.1-1+libtool kdeedu_3.5.1-1+kbsd libapache-mod-encoding_0.0.20021209-6.1+libtool BTS libgtkhtml2_2.6.3-1+libtool+b1 fixed libibtk_0.0.14-10+libtool BTS ocamlgsl_0.3.5-3+kbsd pyopengl_2.0.1.09-1.1+kbsd realtimebattle_1.0.6-2+cfg ? showimg_0.9.4.1-3+libtool+b1? build-dep koffice-dev sidplay_2.0.9-2+kbsd+b1 BTS, pending solfege_3.0.2-1+kbsdfixed tktable_2.9-1+kbsd fixed in tktable2.9, tktable scheduled for removal totem_1.4.5-1+kbsd BTS, pending xdb_1.2.0-7.libtool.1 BTS BTS = an updated fix is again in BTS fixed = it is really fixed, needs "just" rebuild Petr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: conflict with ioctl.h and ioccom.h?
On Sat 18 Nov 2006 14:07, Petr Salinger wrote: > Hi. > > > While going through some of the packages in NOTES [1] I noticed that the > > darkice package is FTBFS again after being claimed fixed. It used to be > > FTBFS because of bad build-deps but now it is something different: > > from the build log [2]: > > It looks like we are currently doing the same thing :-( > > Look at r1727 on > http://svn.debian.org/wsvn/glibc-bsd/?op=log&rev=0&sc=0&isdir=1 I see. Well I suppose we should be doing different things then, maybe I'll focus on the packages with no bug in BTS. Btw darkice's build-deps need the same fix for kfreebsd-amd64 and hurd-i386 as it did for kfreebsd-i386. Should I reopen the bug and add this information? Kostas Koukopoulos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: conflict with ioctl.h and ioccom.h?
Look at r1727 on http://svn.debian.org/wsvn/glibc-bsd/?op=log&rev=0&sc=0&isdir=1 I see. Well I suppose we should be doing different things then, maybe I'll focus on the packages with no bug in BTS. Btw darkice's build-deps need the same fix for kfreebsd-amd64 and hurd-i386 as it did for kfreebsd-i386. Should I reopen the bug and add this information? No, please open new one, with text (mainly subject) like in #361455 - #361495. It allows me to exclude kfreebsd-amd64 only bugs during update of NOTES. BTW, please use severity important for bugs with ***tested*** patches/updated dependencies. There is higher probability they will not be overlooked. Thanks for your help. Petr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kfreebsd-5 5.4-20 MIGRATED to testing
FYI: The status of the kfreebsd-5 source package in Debian's testing distribution has changed. Previous version: 5.4-19 Current version: 5.4-20 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
