On Thu, 2010-09-09 at 09:58 -0400, Ward, David - 0663 - MITLL wrote: > After patching the source code of wpa_supplicant 0.6.10, building > under RHEL 6 x86_64 fails at: So add -fPIC to your CFLAGS before building then perhaps... What CFLAGS are you using to build it? I've been able to easily get it to build on F13 x86_64 (which is quite similar to RHEL6). I was using the normal F13 build flags from RPM macros that packages would use if rebuilt using rpmbuild. Dan > cc -shared ../utils/common.o ../utils/os_unix.o ../utils/wpa_debug.o > .../utils/base64.o ../utils/wpabuf.o ../crypto/md5.o ../crypto/rc4.o > .../crypto/md4.o ../crypto/sha1.o ../crypto/des.o ../crypto/aes_wrap.o > .../crypto/aes.o ../crypto/ms_funcs.o ../crypto/sha256.o > .../eap_common/eap_peap_common.o ../eap_common/eap_psk_common.o > .../eap_common/eap_pax_common.o ../eap_common/eap_sake_common.o > .../eap_common/eap_gpsk_common.o ../eap_common/chap.o > .../crypto/tls_openssl.o ../crypto/crypto_openssl.o ../eap_peer/eap_tls.o > .../eap_peer/eap_peap.o ../eap_peer/eap_ttls.o ../eap_peer/eap_md5.o > .../eap_peer/eap_mschapv2.o ../eap_peer/mschapv2.o ../eap_peer/eap_otp.o > .../eap_peer/eap_gtc.o ../eap_peer/eap_leap.o ../eap_peer/eap_psk.o > .../eap_peer/eap_pax.o ../eap_peer/eap_sake.o ../eap_peer/eap_gpsk.o > .../eap_peer/eap.o ../eap_common/eap_common.o ../eap_peer/eap_methods.o > .../eap_peer/eap_tls_common.o -Wl,-soname -Wl,libeap.so.0 -o > libeap.so.0.0.0 -lssl -lcrypto > /usr/bin/ld: ../utils/common.o: relocation R_X86_64_32 against `.bss' > can not be used when making a shared object; recompile with -fPIC > .../utils/common.o: could not read symbols: Bad value > collect2: ld returned 1 exit status > > If I do not apply the patch then building wpa_supplicant 0.6.10 is > successful. > > David > _______________________________________________ > wimax mailing list > wimax at linuxwimax.org > http://lists.linuxwimax.org/listinfo/wimax
