SCIENTIFIC-LINUX-USERS Archives

February 2008

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jaroslaw Polok <[log in to unmask]>
Reply To:
Jaroslaw Polok <[log in to unmask]>
Date:
Mon, 4 Feb 2008 11:51:15 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
Hello.

Looks like (quite common) problem of picking up library
for wrong architecture in linker path ...

>>> [root@wan-koi vsftpd-2.0.5]# make
[..]
>>> gcc -o vsftpd main.o utility.o prelogin.o ftpcmdio.o postlogin.o 
>> privsock.o tunables.o ftpdataio.o secbuf.o ls.o postprivparent.o 
>> logging.o str.o netstr.o sysstr.o strlist.o banner.o filestr.o 
>> parseconf.o secutil.o ascii.o oneprocess.o twoprocess.o privops.o 
>> standalone.o hash.o tcpwrap.o ipaddrparse.o access.o features.o 
>> readwrite.o ssl.o sysutil.o sysdeputil.o -Wl,-s `./vsf_findlibs.sh`
>>> /lib/libpam.so.0: could not read symbols: File in wrong format
    ^^^^^^^^^^^^^^^^^

It should link against /lib64/libpam* in your case.
(most likely you have /lib in your LD_LIBRARY_PATH ...
get rid of it and then it'll link fine: or look at
vsf_findlibs.sh to see why it picks up 32bit libraries
instead of 64bit ones ...)


Cheers

Jarek
__
-------------------------------------------------------
_ Jaroslaw_Polok ___________________ CERN - IT/FIO/LA _
_ http://home.cern.ch/~jpolok ___ tel_+41_22_767_1834 _
_____________________________________ +41_78_792_0795 _

ATOM RSS1 RSS2