>>>>> On Thu, 26 Feb 2009 12:20:54 -0800, >>>>> "JK" == Jesse Keating <jkeating@xxxxxxxxxx> wrote: JK> I've created a script[1] to find the latest failed build that hasn't yet JK> been fixed during our mass rebuild. The output is an html page broken JK> down by packager. Each package listed under the packager is a link to JK> the latest failed build attempt. Shortly I'll setup a cron job to keep JK> this list updated every 10 minutes or so. JK> http://jkeating.fedorapeople.org/failed-f11-rebuilds.html for kakasi, fail only happened on ppc64, which looks strange to me: http://koji.fedoraproject.org/koji/getfile?taskID=1169050&name=build.log /bin/sh ../libtool --mode=link gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mminimal-toc -Wall -Wunused -Wuninitialized -Wmissing-prototypes -Wmissing-declarations -pedantic -o libkakasi.la -rpath /usr/lib64 -version-info 3:0:1 -export-dynamic libdict.lo libkakasi.lo libkanjiio.lo liba2.lo libg2.lo libj2.lo libk2.lo libee2.lo libhh2.lo libjj2.lo libkk2.lo libitaiji.lo lib78_83.lo mkdir .libs rm -fr .libs/libkakasi.la .libs/libkakasi.* .libs/libkakasi.* (cd . && ln -s libdict.lo libdict.o) (cd . && ln -s libkakasi.lo libkakasi.o) (cd . && ln -s libkanjiio.lo libkanjiio.o) (cd . && ln -s liba2.lo liba2.o) (cd . && ln -s libg2.lo libg2.o) (cd . && ln -s libj2.lo libj2.o) (cd . && ln -s libk2.lo libk2.o) (cd . && ln -s libee2.lo libee2.o) (cd . && ln -s libhh2.lo libhh2.o) (cd . && ln -s libjj2.lo libjj2.o) (cd . && ln -s libkk2.lo libkk2.o) (cd . && ln -s libitaiji.lo libitaiji.o) (cd . && ln -s lib78_83.lo lib78_83.o) gcc -shared libdict.lo libkakasi.lo libkanjiio.lo liba2.lo libg2.lo libj2.lo libk2.lo libee2.lo libhh2.lo libjj2.lo libkk2.lo libitaiji.lo lib78_83.lo -Wl,-soname -Wl, -o .libs/ /usr/bin/ld: cannot open output file .libs/: Is a directory collect2: ld returned 1 exit status make[2]: *** [libkakasi.la] Error 1 This application is quite old and just suspected any files generated by autotools might affects. then tried to regenerate with libtoolize, aclocal, automake and autoconf. However still no lucks. the result is worst: https://koji.fedoraproject.org/koji/getfile?taskID=1204738&name=build.log checking build system type... Invalid configuration `ppc64-redhat-linux-gnu': machine `ppc64-redhat' not recognized configure: error: /bin/sh ./config.sub ppc64-redhat-linux-gnu failed So what am I missing? either of the above didn't happen on other arches though. Any idea? -- Akira TAGOH
Attachment:
pgpBEO3xZ6YU2.pgp
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
