config bug

[Carter Bullard]

Hey Peter,
Sorry for the delayed response.

So, we get the FILE_OFFSET_BITS from autoconf.1 m4 macros,
and they are suppose to provide the results of default compiler
runs, so you can determine what additional flags are needed for
the installed compiler.  So, I'm wondering if your 'gcc' isn't properly
installed?

Carter


On Jul 10, 2008, at 7:00 PM, Peter Van Epp wrote:

> 	While poking at whats wrong with my machine Lixin noticed that
> configure isn't quite correct. It needs to use -m64 and -FPIC while
> compiling in configure to be entirely correct:
>
> ./configure
> ...
> checking for netinet/ether.h... yes
> checking whether ether_hostton is declared... yes
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... 64
> checking for local pcap library... not found
> checking for main in -lpcap... yes
> checking for extraneous pcap header directories... not found
> ...
>
> # CC="gcc -m64 -fPIC" ./configure
> ...
> checking whether ether_hostton is declared... yes
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... no
> checking for local pcap library... not found
> checking for main in -lpcap... yes
> checking for extraneous pcap header directories... not found
> checking for pcap_list_datalinks... yes
> ...
>
> with a 64 bit kernel no offset is needed for large files. I of  
> course have
> no idea how you would cause configure to use the -m64 and -fPIC (and  
> m64
> may be in fact the only one it needs) for itself. It appears to have  
> it
> at some time in VOPTS but isn't itself using that.
>
> Peter Van Epp / Operations and Technical Support
> Simon Fraser University, Burnaby, B.C. Canada
>