Opened 3 years ago

Last modified 3 years ago

#62987 closed defect

p5.30-socket6 fails to configure 10.5.8 PPC — at Version 4

Reported by: bryancn Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: powerpc leopard ppc Cc:
Port: p5-socket6

Description (last modified by jmroot (Joshua Root))

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

Change History (6)

Changed 3 years ago by bryancn

Attachment: main.log added

main.log

comment:1 Changed 3 years ago by bryancn

Keywords: powerpc leopard ppc added
Port: p5.30-socket6 added

comment:2 Changed 3 years ago by 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!

comment:3 Changed 3 years ago by jmroot (Joshua Root)

Port: p5-socket6 added; p5.30-socket6 removed

comment:4 Changed 3 years ago by jmroot (Joshua Root)

Description: modified (diff)

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?

Changed 3 years ago by bryancn

Attachment: config.log added

config.log

Note: See TracTickets for help on using tickets.