ld: fatal: use the -z help option for usage information

[Rafael Ostertag]

Hi Maciej

On Tue, Apr 22, 2014 at 11:33:49AM +0100, Maciej (Matchek) Blizi??ski wrote:
> The failing invocation is:
> 
> (cd work/solaris10-sparc/build-isa-sparcv8plus/Python-3.4.0/; \
> ld -mcpu=v9 -Wa,-xarch=v8plus -L/opt/csw/lib/ffi -L/opt/csw/lib
> -lsocket -lresolv -lrt -mcpu=v9 -Wa,-xarch=v8plus -L/opt/csw/lib/ffi
> -L/opt/csw/lib -lsocket -lresolv -lrt -mcpu=v9 -Wa,-xarch=v8plus
> -L/opt/csw/lib/ffi -L/opt/csw/lib -lsocket -lresolv -lrt -g -mcpu=v9
> -Wa,-xarch=v8plus -D_XPG5 -I/opt/csw/include
> build/temp.solaris-2.10-sun4v.32bit-3.4/home/maciej/src/opencsw/pkg/lang-python/python/branches/python-3.4/work/solaris10-sparc/build-isa-sparcv8plus/Python-3.4.0/Modules/_ctypes/_ctypes_test.o
> -L. -L/opt/csw/lib/ffi -L/opt/csw/lib -lpython3.4m -o
> build/lib.solaris-2.10-sun4v.32bit-3.4/_ctypes_test.so)
> 

Is there a particular reason, you set 

 MACHDEP = $(ISA)
 EXTRA_CONFIGURE_EXPORTS += MACHDEP

By doing so, some internal configure variables won't be set which in turn lead
to Makefile using `ld' instead of `gcc'. When MACHDEP is not set, the configure
output looks like

 [...]
 checking LDSHARED... $(CC) -shared
 checking CCSHARED... -fPIC
 checking LINKFORSHARED... 
 checking CFLAGSFORSHARED... $(CCSHARED)
 [...]

which is a good thing. When MACHDEP is set, it looks more like

 [...]
 checking LDSHARED... ld
 checking CCSHARED... 
 checking LINKFORSHARED... 
 checking CFLAGSFORSHARED... 
 [...]

which is bad.

Specifically, setting MACHDEP manually inhibits $ac_sys_system, and
$ac_sys_release to be set, which are used all over the place as quick peek in
configure.ac reveals. I can't tell if that's a bug or not, though.

HTH
rafi