On Tue, 24 Jan 2006, Justin wrote:
Hi Dan,
thanks for replying so fast,. I found the initial problem, glib was
incorrectly installed for 64bit. I re-ran the glib install and the problem
disappeared. I now have a perl problem to look into. I am getting
make[2]: Entering directory `/mnt/main/home/justin/src/rpm-4.4.4/perl'
gcc -m64 -c -I../lib -I../rpmdb -I../rpmio -I../popt -fPIC
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"0.66\"
-DXS_VERSION=\"0.66\" -fpic
"-I/usr/lib64/perl5/5.8.7/x86_64-linux-thread-multi-ld/CORE" -DRPM_RPM41
RPM.c
In file included from
/usr/lib64/perl5/5.8.7/x86_64-linux-thread-multi-ld/CORE/op.h:496,
from
/usr/lib64/perl5/5.8.7/x86_64-linux-thread-multi-ld/CORE/perl.h:2600,
from RPM.xs:16:
/usr/lib64/perl5/5.8.7/x86_64-linux-thread-multi-ld/CORE/reentr.h:611: error:
field '_crypt_struct' has incomplete type
This looks as if you've installed a 64-bit perl compiler. There is a
reason for the note in 10.33.1 of the multilib book, perl predates
almost everything else, and behaves very badly with multilib (typically,
things like 'perl -V' show the wrong libs, and when we used to build 32
and 64 bit perl for the temp system, it didn't work correctly). Most
people only want to run perl code, and 32-bit will do. In this case,
rpm seems to be trying to compile against perl headers, in which case
32-bit probably won't do - it certainly *seems* to have the correct
headers, but maybe one of them is not finding the right includes.
If you installed the 64-bit perl after the 32-bit, the headers _should_
be correct for 64-bit types.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page