Well the build failed in BeeCrypt ;( /bin/sh ./libtool --mode=compile --tag=CC /usr/bin/gcc -DHAVE_CONFIG_H -I. -I. -I. -I./.. -DOPTIMIZE_POWERPC -O -fsigned-char -DNDEBUG -fomit-frame-pointer -c -o hmacsha384.lo hmacsha384.c /usr/bin/gcc -DHAVE_CONFIG_H -I. -I. -I. -I./.. -DOPTIMIZE_POWERPC -O -fsigned-char -DNDEBUG -fomit-frame-pointer -c hmacsha384.c -o hmacsha384.o /bin/sh ./libtool --mode=compile --tag=CC /usr/bin/gcc -DHAVE_CONFIG_H -I. -I. -I. -I./.. -DOPTIMIZE_POWERPC -O -fsigned-char -DNDEBUG -fomit-frame-pointer -c -o hmacsha512.lo hmacsha512.c ~ [EMAIL PROTECTED] openpkg-2.3.0-2.3.0.src]$ tail -f LOG blowfishopt.s:640: Error: unsupported relocation against r1 blowfishopt.s:640: Error: unsupported relocation against r1 make[2]: *** [blowfishopt.lo] Error 1 make[2]: Leaving directory `/QOpenSys/tmp/openpkg-2.3.0/beecrypt-4.1.2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/QOpenSys/tmp/openpkg-2.3.0/beecrypt-4.1.2' make: *** [all] Error 2 + exit 2 + exit 2 openpkg.boot:ERROR: script returned non-null value
Any idea ? FYI, I'm using gcc 3.3.2 2005/5/13, Henri Gomez <[EMAIL PROTECTED]>: > I do my openpkg boot from the the .sh (openpkg-2.3.0-2.3.0.src.sh) > > cd /QOpenSys/builds/ > > sh openpkg-2.3.0-2.3.0.src.sh --prefix=/QOpenSys/openpkg > > cd openpkg-2.3.0-2.3.0 > export TMPDIR=/QOpenSys/tmp > sh openpkg.boot --prefix=/QOpenSys/openpkg/ > > Also I doing it under PASE (iSeries), I should specify that TMPDIR is > under /QOpenSys/tmp instead of /tmp (via export TMPDIR=/QOpenSys/tmp). > > Why because on iSeries file system, stuff under /QOpenSys is case > sensitive, but under / it's not the case ,( > > As such gzip couldn't be built since _match.s == _match.S and > configure saw an inexisting asm support. > > > 2005/5/13, Ralf S. Engelschall <[EMAIL PROTECTED]>: > > On Fri, May 13, 2005, Henri Gomez wrote: > > > > > Hi Ralf, long time I didn't talk to you (openssl rpm time). > > > BTW, did these 'fixed' config.* are used in openpkg.boot ? > > > How can I inject/patch modifications in openpkg.boot process ? > > > > Oh, you are speaking about the "openpkg" package. No, there are local > > copies because this package cannot depent on the "config" package. I've > > upgraded now the config.* scripts to the latest GNU CVS version as of > > today and rolled a new "openpkg" package in CURRENT. Retry with this > > one, please. > > Ralf S. Engelschall > > [EMAIL PROTECTED] > > www.engelschall.com > > > > ______________________________________________________________________ > > The OpenPKG Project www.openpkg.org > > Developer Communication List openpkg-dev@openpkg.org > > > ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List openpkg-dev@openpkg.org
