Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 116542 - Beecrypt does not compile with march=pentium-m on GCC-3.4.4
Summary: Beecrypt does not compile with march=pentium-m on GCC-3.4.4
Status: RESOLVED DUPLICATE of bug 59890
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-23 14:16 UTC by Bruno
Modified: 2005-12-23 14:31 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno 2005-12-23 14:16:36 UTC
I'm trying to compile beecrypt (dependency of util-vserver) but compilation always fails while using CFLAGS="-march=pentium-m -O3 -fomit-frame-pointer -pipe". Just removing -march from my CFLAGS solves the problem.

Working -march's: athlon-xp, pentium3, <none>

Looks as if one of the optimizations selected by pentium-m but not pentium3 makes C code and generated asembler code incompatible...
All beecrypt version in portage as of 2005-12-22 are affected (3.1.0-r1, 3.1.0-r2, 4.1.2)

The compilation fails during linking (... -march=pentium-m -Wl,-soname -Wl,libbeecrypt.so.6 -o .libs/libbeecrypt.so.6.4.0) with symbols having different sizes in X.o and Xopt.o files.

.libs/blowfishopt.o: In function `blowfishEncrypt':
: multiple definition of `blowfishEncrypt'
.libs/blowfish.o:blowfish.c:(.text+0x0): first defined here
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../i686-pc-linux-gnu/bin/ld: Warning: size of symbol `blowfishEncrypt' changed from 1201 in .libs/blowfish.o to 815 in .libs/blowfishopt.o

Same goes for: blowfishDecrypt, mpzero, mpfill, mpeven, mpodd, mpaddw, mpsubw, mpadd, mpsub, mpdivtwo, mpmultwo, mpsetmul, mpaddmul, mpaddsqrtrc, mppndiv and sha1Process.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2005-12-23 14:31:38 UTC

*** This bug has been marked as a duplicate of 59890 ***