p5.30-socket6 fails to configure 10.5.8 PPC

[bryancn]

This is an upgrade & was installing fine previously.

--->  Configuring p5.30-socket6
Error: Failed to configure p5.30-socket6: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5-socket6/p5.30-socket6/work/Socket6-0.29/config.log
Error: Failed to configure p5.30-socket6: configure failure: command execution failed

This config log doesn't exist

:info:configure checking for gcc... /usr/bin/gcc-4.2
:info:configure checking whether the C compiler works... no
:info:configure configure: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5-socket6/p5.30-socket6/work/Socket6-0.29':
:info:configure configure: error: C compiler cannot create executables

[bryancn]

main.log

[kencu (Ken)]

99      :info:configure checking for gcc... /usr/bin/gcc-4.2
100	:info:configure checking whether the C compiler works... no

would you please try that compiler out on the simplest "hello_world.c" source you can find and verify that it works at all?

If it does, then we'll need to see the config.log to see why it is not working here.

Thanks!

[jmroot (Joshua Root)]

Base is deciding not to use the compiler in /usr/bin:

:debug:configure CC='/Developer/usr/bin/gcc-4.2'

So that supports the theory that it might not be working. Possibly missing Command Line Tools, or whatever they were called on Leopard?

[bryancn]

config.log

[bryancn]

After another clean, config log appeared and now attached. Assume my error, sorry. Other p5 packages install just fine/

[kencu (Ken)]

The config log shows:

/usr/bin/gcc-4.2: No such file or directory

On the 10.5 DVD with the Xcode installation package there should be the option to install the tools that are needed for Unix development, along with a few SDKs that Xcode had available besides the 10.5 SDK.

You do need to install the "Tools for Unix Development" or much of MacPorts won't really be able to work.

Basically, in the end, this needs to exist, and work:

/usr/bin/gcc-4.2

I'm not sure how other things installed, exactly -- but even if they did somehow install using the SDK in /Developer, there are lots of things that won't install.

[bryancn]

Apologies. I had not installed the XCode 3.1.4 Developer Tools package. Works perfectly now.