On 7/4/05, Ken Moffat <[EMAIL PROTECTED]> wrote: > On Mon, 4 Jul 2005, Ahmed El-Daly wrote: > > > I swear by all things holy that perl is in the PATH. After chrooting, > > if I type perl -v from anywhere in the file structure, I get: > > This is perl, v5.8.5 built for x86_64-linux > > > [...] > > > > Still in config.make I have this line: > > PERL = no > > > > What does perl -V show (capital V) ? It ought to show _rather_more_ > than just Larry's version and copyright stuff, particularly the contents > of @INC which is often where the problems occur. > > And out of interest, is this a multilib build, or just 64-bit stuff in > /lib ? > > Ken > -- > das eine Mal als Tragödie, das andere Mal als Farce > > perl -V showed @INC pointing to all sorts of lib64 directories in all different places. You are correct (how the heck did you know :0) ?) I am building a pure-64 system and doing away with the lib64 thing. I figure if I ever do need 32-bit programs, I will make a 32-bit toolchain and put it in /lib32.
So now that I know what the problem is, I tried recompiling perl, and for some reason I am gettting this: cc -L/usr/local/lib -o miniperl \ miniperlmain.o opmini.o libperl.a libperl.a(pp.o)(.text+0x2803): In function `Perl_pp_pow': : undefined reference to `pow' libperl.a(pp.o)(.text+0x357d): In function `Perl_pp_modulo': : undefined reference to `floor' [... some more undefined references to math functions...] collect2: ld returned 1 exit status make: *** [miniperl] Error 1 I know that there is a patch out there (from Chris Lingard) that would fix this, but this was made to change perl from looking for /lib to /lib64, I have everything in /lib anyways. Oh well, more digging. Just can't figure out why it worked before (unless I went ahead and wrote over a change I made earlier :( ! ) -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
