[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Fri, 19 May 2006 23:08:38 -0600
From: Vincent Danen <vdanen@...sec.ca>
To: owl-users@...ts.openwall.com
Subject: crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems
I know this isn't exactly owl-specific, but it kinda relates, maybe, to
future owl development (in some sick and twisted fashion I guess).
I don't know what the plans for openwall to move with newer gcc versions
is, but for Annvix I decided to play with gcc 4.0.3 to get some of the
new stuff (like FORTIFY), but I'm not adventerous enough to try 4.1.x to
get SSP. Anyways, compiling gcc was ok, but when I try to compile glibc
with crypt_blowfish, I end up with the following error:
gcc md5-crypt.c -c -std=gnu99 -DNDEBUG=1 -O2 -Wall -Winline
-Wstrict-prototypes -Wwrite-strings -finline-functions -freorder-blocks
-g -march=i586 -mpreferred-stack-boundary=2 -I../include -I.
-I/home/vdanen/svn/2.0-CURRENT/glibc/BUILD/glibc-2.3.5/build-i586-linux/crypt
-I.. -I../libio
-I/home/vdanen/svn/2.0-CURRENT/glibc/BUILD/glibc-2.3.5/build-i586-linux
-I../sysdeps/i386/elf -I../linuxthreads/sysdeps/unix/sysv/linux/i386
-I../linuxthreads/sysdeps/unix/sysv/linux
-I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread
-I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix
-I../linuxthreads/sysdeps/i386/i586 -I../linuxthreads/sysdeps/i386
-I../libidn/sysdeps/unix -I../sysdeps/unix/sysv/linux/i386
-I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common
-I../sysdeps/unix/mman -I../sysdeps/unix/inet
-I../sysdeps/unix/sysv/i386 -I../sysdeps/unix/sysv
-I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix
-I../sysdeps/i386/i586 -I../sysdeps/i386/i486 -I../sysdeps/i386/fpu
-I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96
-I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32
-I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic
-nostdinc -isystem /usr/lib/gcc/i586-annvix-linux-gnu/4.0.3/include
-isystem
/home/vdanen/svn/2.0-CURRENT/glibc/BUILD/glibc-2.3.5/kernel-headers
-D_LIBC_REENTRANT -include ../include/libc-symbols.h -DNOT_IN_libc=1
-DIS_IN_libcrypt=1 -o
/home/vdanen/svn/2.0-CURRENT/glibc/BUILD/glibc-2.3.5/build-i586-linux/crypt/md5-crypt.o
-MD -MP -MF
/home/vdanen/svn/2.0-CURRENT/glibc/BUILD/glibc-2.3.5/build-i586-linux/crypt/md5-crypt.o.dt
-MT
/home/vdanen/svn/2.0-CURRENT/glibc/BUILD/glibc-2.3.5/build-i586-linux/crypt/md5-crypt.o
crypt-entry.c:74: warning: function declaration isn't a prototype
crypt-entry.c:142: error: 'fcrypt' aliased to undefined symbol 'crypt'
make[2]: ***
[/home/vdanen/svn/2.0-CURRENT/glibc/BUILD/glibc-2.3.5/build-i586-linux/crypt/crypt-entry.o]
Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
`/home/vdanen/svn/2.0-CURRENT/glibc/BUILD/glibc-2.3.5/crypt'
make[1]: *** [crypt/others] Error 2
make[1]: Leaving directory
`/home/vdanen/svn/2.0-CURRENT/glibc/BUILD/glibc-2.3.5'
make: *** [all] Error 2
error: Bad exit status from /home/vdanen/tmp/rpm-tmp.55722 (%build)
My glibc is pretty much based on 2.3.5-owl5, with some two patches from
Mandriva to get it to compile with gcc4.
My previous was gcc 3.4.3 with glibc 2.3.5 and crypt_blowfish 1.0 (I
updated to 1.0.1 today in case that fixed it). That one compiled fine
so the only real difference here is gcc 4.0.3.
Any ideas on what might be causing the problem?
Googling wasn't overly helpful.
As an aside, I did compile glibc against gcc 4.0.3 *without*
crypt_blowfish and without the following two patches:
glibc-2.3.5-alt-assume_kernel.diff
glibc-2.3.3-owl-crypt_freesec.diff
which were taken from 2.3.5-owl5 (they failed with rejects, I'm assuming
due to the missing crypt_blowfish bits).
Any ideas on what the problem might be?
--
Annvix - Secure Linux Server: http://annvix.org/
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FEE30AD4 : 7F6C A60C 06C2 4811 FA1C A2BC 2EBC 5E32 FEE3 0AD4}
Wasting time like it was free...
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
