Bug 113600 – cryptsetup-luks-1.0.1-r1 doesn't compile on ppc64 with -dynamic

• Product: Gentoo Linux
• Status: VERIFIED FIXED

[Description Joshua (RETIRED) 2005-11-25 17:31:28 UTC]

Without dynamic flag set get a whole load of linker errors.  Below is a small
initial selection.

powerpc64-unknown-linux-gnu-gcc -O2 -pipe -o cryptsetup -static cryptsetup.o  /u
sr/lib64/libpopt.a ../lib/.libs/libcryptsetup.a -ldevmapper -L/usr/lib64 /usr/li
b64/libgcrypt.a -lnsl /usr/lib64/libgpg-error.a -luuid
/usr/lib64/libgcrypt.a(mpi-add.o): In function `.gcry_mpi_add':
mpi-add.c:(.text+0x4d4): undefined reference to `._gcry_mpih_sub_n'
mpi-add.c:(.text+0x524): undefined reference to `._gcry_mpih_sub_n'
mpi-add.c:(.text+0x5b4): undefined reference to `._gcry_mpih_add_n'
mpi-add.c:(.text+0x69c): undefined reference to `._gcry_mpih_sub_n'
/usr/lib64/libgcrypt.a(mpi-bit.o): In function `.gcry_mpi_rshift':
mpi-bit.c:(.text+0x44c): undefined reference to `._gcry_mpih_rshift'
/usr/lib64/libgcrypt.a(mpi-div.o): In function `._gcry_mpi_tdiv_qr':
mpi-div.c:(.text+0x21c): undefined reference to `._gcry_mpih_lshift'
mpi-div.c:(.text+0x234): undefined reference to `._gcry_mpih_lshift'
mpi-div.c:(.text+0x5c4): undefined reference to `._gcry_mpih_rshift'


With dynamic flag set it compiles fine.


Could it be that libgcrypt.a is not being built correctly?

Reproducible: Always
Steps to Reproduce:
1.  emerge cryptsetup-luks
2.
3.

Actual Results:  
Many link errors.  

Expected Results:  
Compiled fine.

Portage 2.0.51.22-r3 (default-linux/ppc/2005.1/ppc64/64bit-userland/970/pmac,
gcc-3.4.4, glibc-2.3.4.20041102-r1, 2.6.12-gentoo-r6 ppc64)
=================================================================
System uname: 2.6.12-gentoo-r6 ppc64 PPC970FX, altivec supported
Gentoo Base System version 1.6.13
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="ppc64"
AUTOCLEAN="yes"
CBUILD="powerpc64-unknown-linux-gnu"
CFLAGS="-O2 -pipe"
CHOST="powerpc64-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
LANG="en_GB.UTF-8"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.asia.gentoo.org/gentoo-portage"
USE="ppc64 X alsa altivec audiofile berkdb bitmap-fonts bzip2 cdr cjk crypt curl
dga dmx dts dvd emacs encode ethereal exif exiscan-acl expat fam gdbm gif glut
gnome gpm gtk gtk2 idn ipv6 jpeg lcms libwww live mbox mng motif mule ncurses
nls nptl ogg oggvorbis opengl oss pam pcre perl png python readline real sdl
server spell ssl tcltk tcpd tetex threads tiff truetype truetype-fonts
type1-fonts udev unicode usb vorbis xinerama xml2 xmms xv zlib userland_GNU
kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS

[Comment 1 Joshua (RETIRED) 2005-11-25 18:04:40 UTC]

Possible dependency on bug 90211.

[Comment 2 Benjamin Smee (strerror) (RETIRED) 2005-11-25 18:17:24 UTC]

i had a few other 64 bit tests and they came back fine. I suspect the problem is
related to bug 90211, however, I'll leave this open a little longer to give
myself more time to verify and for other reports to come in.

[Comment 3 Benjamin Smee (strerror) (RETIRED) 2005-11-25 18:21:04 UTC]

can you drop back to cryptsetup-luks-1.0.1 and see if that compiles? I suspect
it will not, either with or without the static use flag.

[Comment 4 Joshua (RETIRED) 2005-11-25 18:39:44 UTC]

O.k.  Summary so far:

1.0.1 without static:  Compiles.
1.0.1 with  static:    Fails, in similar manner.

1.0.1-r1 without dynamic: Fails, as before.
1.0.1-r1 with dynamic:  Compiles.

1.0.1-r1 is the same with and without multilib.

[Comment 5 Tom Gall (RETIRED) 2005-11-25 20:26:47 UTC]

with the fix for libgcrypt, this seems to build just fine ... I'm going to
attach to 90211 and close

[Comment 6 Tom Gall (RETIRED) 2005-11-25 20:27:09 UTC]

stick a fork in it