Bug#419742: quantlib-swig: FTBFS on mips/mipsel due to relocation error
reassign 419742 quantlib-swig found 419742 0.3.14-1 thanks Dirk, This reassignment of an RC bug to the toolchain has blocked all of lenny for another day, because it happened right when glibc was ready to enter testing. Please consider when reassigning bugs to the toolchain whether these bugs are RC for the toolchain, as distinct from being RC for your package. I'm reassigning this bug back to quantlib-swig, because this *is* the package with the RC bug; as Thiemo noted, the build failure happens as a consequence of the special-case use of -O0 on mips* in the package's build rules. The build failure is of this package, and it can be resolved without any changes to the toolchain. The toolchain, further, works fine on mips for almost all other packages. There are limits to the number of symbols the toolchain supports on mips, yes, but even mozilla is able to work within those limits -- this simply does not make the toolchain unreleasable (we've released the toolchain with this limitation for as long as we've been releasing mips). The eaccess issue in glibc might be considered RC, though I haven't seen anything before now to indicate people consider it a bug in glibc instead of bugs in the packages with conflicting declarations for eaccess(). The number of packages affected by this issue is quite small (compared to the number of packages that are waiting on glibc right now for testing propagation, definitely!), and in all such cases involves unnecessary shadowing of a system declaration, so unless someone shows that the new glibc declaration is just plain *wrong*, I don't see any reason yet to consider it a glibc bug. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419742: quantlib-swig: FTBFS on mips/mipsel due to relocation error
On Fri, Jun 01, 2007 at 05:25:01PM -0500, Dirk Eddelbuettel wrote: | I'm reassigning this bug back to quantlib-swig, because this *is* the | package with the RC bug; as Thiemo noted, the build failure happens as a | consequence of the special-case use of -O0 on mips* in the package's build | rules. The build failure is of this package, and it can be resolved without | any changes to the toolchain. Hm, I must have overlooked this in his mail. Building under the default -O2 will succeed on mips as it used to? I shall prepare a fixed package rather quickly then. His comment in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419742;msg=30 was that dropping the mips* special-casing fixed /this/ failure, and got him on to the next failure. The next failure after that is an incompatibility between current ruby1.8-dev and current libc6-dev (nothing in quantlib-swig's source refers to eaccess() directly); so while dropping the special-casing in your package won't be enough to get it to build on mips*, you can upload it with confidence that the remaining bug is Not Your Problem. :) On to Brown Bag mode and preparing a fresh ql-swig. Thanks :) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419742: quantlib-swig: FTBFS on mips/mipsel due to relocation error
Package: quantlib-swig Severity: serious Version: 0.3.14-1 Hi Your package fails to build from source on mips and mipsel due to relocation errors according to the build logs. Note that this indicates that some part of the code (or library build dependencies) might not be compiled with the PIC (Position Independent Code) flag enabled... Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419742: quantlib-swig: FTBFS on mips/mipsel due to relocation error
Hi Luk, On Tue, Apr 17, 2007 at 07:20:08PM +0200, Luk Claes wrote: Package: quantlib-swig Severity: serious Version: 0.3.14-1 Hi Your package fails to build from source on mips and mipsel due to relocation errors according to the build logs. Note that this indicates that some part of the code (or library build dependencies) might not be compiled with the PIC (Position Independent Code) flag enabled... Could that not also be indicative of a bug in the toolchain? After all, i) it used to build on these arches with the same flags, build-depends, ... ii) it builds on the other arches What do you think? Dirk -- Hell, there are no rules here - we're trying to accomplish something. -- Thomas A. Edison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419742: quantlib-swig: FTBFS on mips/mipsel due to relocation error
Dirk Eddelbuettel wrote: Hi Luk, On Tue, Apr 17, 2007 at 07:20:08PM +0200, Luk Claes wrote: Package: quantlib-swig Severity: serious Version: 0.3.14-1 Hi Your package fails to build from source on mips and mipsel due to relocation errors according to the build logs. Note that this indicates that some part of the code (or library build dependencies) might not be compiled with the PIC (Position Independent Code) flag enabled... Could that not also be indicative of a bug in the toolchain? After all, i) it used to build on these arches with the same flags, build-depends, ... New upstream versions... you might want to test compiling 0.3.13 with current build dependencies? ii) it builds on the other arches relocation errors are more likely to occur on mips than on other architectures, because it's more strict in this regard. What do you think? I think a toolchain bug is unlikely, though maybe it's caused by quantlib or boost. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419742: quantlib-swig: FTBFS on mips/mipsel due to relocation error
On Tue, Apr 17, 2007 at 10:07:55PM +0200, Luk Claes wrote: Dirk Eddelbuettel wrote: Hi Luk, On Tue, Apr 17, 2007 at 07:20:08PM +0200, Luk Claes wrote: Package: quantlib-swig Severity: serious Version: 0.3.14-1 Hi Your package fails to build from source on mips and mipsel due to relocation errors according to the build logs. Note that this indicates that some part of the code (or library build dependencies) might not be compiled with the PIC (Position Independent Code) flag enabled... Could that not also be indicative of a bug in the toolchain? After all, i) it used to build on these arches with the same flags, build-depends, ... New upstream versions... you might want to test compiling 0.3.13 with current build dependencies? ii) it builds on the other arches relocation errors are more likely to occur on mips than on other architectures, because it's more strict in this regard. What do you think? I think a toolchain bug is unlikely, though maybe it's caused by quantlib or boost. Not QuantLib. Remember that this is a swig package -- there is exactly _one_ call to g++ in the build log (indented for mail) g++ -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes -O0 \ -g0 -fPIC -I/usr/include -I/usr/include/python2.4 -c \ QuantLib/quantlib_wrap.cpp -o \ build/temp.linux-mips-2.4/QuantLib/quantlib_wrap.o -Wno-unused -O0 -g0 and given that this comes from the QuantLib / Swig / Python templates, it also hasn't changed in a while. And of course contains -fPIC. It is a monster compilation though: this slows i86 down as well and consumes tons of memory due to the heavy templating. I still think it is a toolchain issue. Dirk -- Hell, there are no rules here - we're trying to accomplish something. -- Thomas A. Edison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
