lör 2011-03-19 klockan 17:32 +0100 skrev Kurt Roeckx: > On Fri, Mar 18, 2011 at 05:19:10PM +0100, Mattias Ellert wrote: > > Hi! > > > > Something went very wrong with the build of globus-gsi-callback 2.8-1 on > > s390. The build completed, and packages were created, but they are > > broken. The build log says ... > > > > eval: 1: libtool_args+=: not found > > eval: 1: compile_command+=: not found > > eval: 1: finalize_command+=: not found > > eval: 1: libtool_args+=: not found > > eval: 1: compile_command+=: not found > > eval: 1: finalize_command+=: not found > > eval: 1: libtool_args+=: not found > > eval: 1: compile_command+=: not found > > eval: 1: finalize_command+=: not found > > eval: 1: libtool_args+=: not found > > > > and continues like that for a while more. This did not happen for the > > other architectures, and the previous version built fine, so it looks > > like some temporary glitch. I would like to request a binNMU to try to > > build again. > > I've just scheduled a binNMU. That didn't quite work - the same thing happened again. After some investigation I have tracked down the problem to that the libtool file for s390 is using /bin/sh instead of /bin/bash. If I check the contents of the globus-core package I see that the libtool file installed has the wrong shebang, but only for s390: $ head -1 */usr/sbin/globus-libtool-* ==> alpha/usr/sbin/globus-libtool-gcc64pthr <== #! /bin/bash ==> armel/usr/sbin/globus-libtool-gcc32pthr <== #! /bin/bash ==> hppa/usr/sbin/globus-libtool-gcc32pthr <== #! /bin/bash ==> i386/usr/sbin/globus-libtool-gcc32pthr <== #! /bin/bash ==> mipsel/usr/sbin/globus-libtool-gcc32pthr <== #! /bin/bash ==> mips/usr/sbin/globus-libtool-gcc32pthr <== #! /bin/bash ==> powerpc/usr/sbin/globus-libtool-gcc32pthr <== #! /bin/bash ==> s390/usr/sbin/globus-libtool-gcc32pthr <== #! /bin/sh So the problem is inherited form that something went wrong for the globus-core build on s390 - so can I request a binNMU for globus-core on s390 first? > > Other builds that have tried to use this broken version of > > globus-gsi-callback on s390 as a build dependency have failed: > > globus-gass-copy, globus-gram-job-manager and globus-gssapi-gsi. > > Please let us know if you want us to retry those. Not quite yet, the first dependencies should be fixed first. > Kurt Mattias
Attachment:
signature.asc
Description: This is a digitally signed message part