Re: Builds disturbed by the usage of a 64bit kernel.
Le Fri, May 18, 2007 at 07:26:06PM +1000, jim a écrit : sorry in advance if i have missed the point - but this might be relevant ;) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=251149 Thanks all for your answers, it seems that linux32 is the solution. However, I remain puzzled by the fact that in the absence of this workaround, some pacakges guess well and other guess wrong. Shall I report a bug for the ones guessing wrong? Or against the one(s) failing to build because they guess wrong? Or maybe it does not desserve a bug? In any case, it seems that the linux32 could be better documented... Any idea on the best place for this? The port homepage? Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Builds disturbed by the usage of a 64bit kernel.
Charles Plessy a écrit : Dear all, Starting from the observation that a pre-release debian pacakge of root-system and the current xaralx (non-free) pacakge fail to build from source on G5 powerpc machines but not on G4, I started to get worried that that kind of failures would be more widespread. The core of the problem is that the configure scripts sometimes mistake the build system type to be powerpc64-unknown-linux-gnu instead of powerpc-unknown-linux-gnu. I am wondering similar things happen on sparc running a 32-bit userland with a 64-bits kernel, hence the crosspost. Have you tried to use linux32? This is how sparc build daemons are building packages when using a 64-bit kernel. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Builds disturbed by the usage of a 64bit kernel.
Charles Plessy wrote: Dear all, Starting from the observation that a pre-release debian pacakge of root-system and the current xaralx (non-free) pacakge fail to build from source on G5 powerpc machines but not on G4, I started to get worried that that kind of failures would be more widespread. The core of the problem is that the configure scripts sometimes mistake the build system type to be powerpc64-unknown-linux-gnu instead of powerpc-unknown-linux-gnu. I am wondering similar things happen on sparc running a 32-bit userland with a 64-bits kernel, hence the crosspost. To investigate a bit more, I am rebuilding the maching with a cowbuildd, and in this email, I would like to give preliminary results before the week-end. Out of 500 packages already build, ~140 tried to detect the build system type, and ~30 of them guessed wrongly (powerpc64 instead of powerpc). Three of them failed to build and in one case the wrong guess is the obvious reason: In file included from /usr/include/features.h:346, from /usr/include/stdlib.h:25, from argus.c:40: /usr/include/gnu/stubs.h:9:27: error: gnu/stubs-64.h: No such file or directory make[2]: *** [argus.o] Error 1 I will continue the experiment during the week-end, but I do not think that I can manage to rebuild the whole archive. I woudld be especially intersted by the opinion of the sparc porters: do you use sparc64-powered buildd with 32-bit userlands? Do you often run in that kind of problem? Another think I am wondering is wether the pacakges built successfully with the wrong build system type are useful on normal 32-bit processors. Have a nice day, sorry in advance if i have missed the point - but this might be relevant ;) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=251149 jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Builds disturbed by the usage of a 64bit kernel.
Dear all, Starting from the observation that a pre-release debian pacakge of root-system and the current xaralx (non-free) pacakge fail to build from source on G5 powerpc machines but not on G4, I started to get worried that that kind of failures would be more widespread. The core of the problem is that the configure scripts sometimes mistake the build system type to be powerpc64-unknown-linux-gnu instead of powerpc-unknown-linux-gnu. I am wondering similar things happen on sparc running a 32-bit userland with a 64-bits kernel, hence the crosspost. To investigate a bit more, I am rebuilding the maching with a cowbuildd, and in this email, I would like to give preliminary results before the week-end. Out of 500 packages already build, ~140 tried to detect the build system type, and ~30 of them guessed wrongly (powerpc64 instead of powerpc). Three of them failed to build and in one case the wrong guess is the obvious reason: In file included from /usr/include/features.h:346, from /usr/include/stdlib.h:25, from argus.c:40: /usr/include/gnu/stubs.h:9:27: error: gnu/stubs-64.h: No such file or directory make[2]: *** [argus.o] Error 1 I will continue the experiment during the week-end, but I do not think that I can manage to rebuild the whole archive. I woudld be especially intersted by the opinion of the sparc porters: do you use sparc64-powered buildd with 32-bit userlands? Do you often run in that kind of problem? Another think I am wondering is wether the pacakges built successfully with the wrong build system type are useful on normal 32-bit processors. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Builds disturbed by the usage of a 64bit kernel.
On Fri, May 18, 2007 at 12:13:34PM +0900, Charles Plessy wrote: Dear all, Starting from the observation that a pre-release debian pacakge of root-system and the current xaralx (non-free) pacakge fail to build from source on G5 powerpc machines but not on G4, I started to get worried that that kind of failures would be more widespread. The core of the problem is that the configure scripts sometimes mistake the build system type to be powerpc64-unknown-linux-gnu instead of powerpc-unknown-linux-gnu. I am wondering similar things happen on sparc running a 32-bit userland with a 64-bits kernel, hence the crosspost. To investigate a bit more, I am rebuilding the maching with a cowbuildd, and in this email, I would like to give preliminary results before the week-end. Interesting, notice that Andreas Jochens has gotten a serie of patches applied to some packages for his pure-64 effort. I wonder if this effort helps in this case, or causes problems. Do you know what exactly is causing this problem ? Or could you list the 140 packages which you already detected to be problematic ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
