Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#32460 closed defect (fixed)

beanstalkd failed to build

Reported by: conradwt (Conrad Taylor) Owned by: nick@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: lion Cc:
Port: beanstalkd

Description (last modified by ryandesign (Ryan Carsten Schmidt))

beanstalkd failed to build on Mac OS 10.7.2 using Xcode 4.2.1.

Attachments (2)

main.log (14.0 KB) - added by conradwt (Conrad Taylor) 12 years ago.
beanstalkd-main-log-transacript
config.log (7.6 KB) - added by conradwt (Conrad Taylor) 12 years ago.
config.log

Download all attachments as: .zip

Change History (6)

Changed 12 years ago by conradwt (Conrad Taylor)

Attachment: main.log added

beanstalkd-main-log-transacript

comment:1 in reply to:  description Changed 12 years ago by nick@…

Owner: changed from macports-tickets@… to nick@…

Hi, could you also add in config.log ? That contains the exact problem you're seeing with the build.

Changed 12 years ago by conradwt (Conrad Taylor)

Attachment: config.log added

config.log

comment:2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: nick@… removed
Description: modified (diff)
Summary: beanstalks failed to buildbeanstalkd failed to build

The config log shows the not unexpected:

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

Xcode 4.2 of course does not include GCC anymore.

Nick, read PortfileRecipes#compiler for the correct solution.

comment:3 in reply to:  2 Changed 12 years ago by nick@…

Resolution: fixed
Status: newclosed

Replying to ryandesign@…:

The config log shows the not unexpected:

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

Xcode 4.2 of course does not include GCC anymore.

Nick, read PortfileRecipes#compiler for the correct solution.

Ryan, you're right I completely missed the line about missing gcc. Given there are issues with building this with clang, I think it's best to force this back to use llvm-gcc-4.2 rather than gcc-4.2. I've updated the Portfile appropriately.

comment:4 Changed 12 years ago by conradwt (Conrad Taylor)

Has these changes been added to the port file? I ask because I'm seeing the following build errors:

:info:build In file included from /opt/local/include/event2/event.h:195,
:info:build                  from /opt/local/include/event.h:71,
:info:build                  from conn.h:23,
:info:build                  from prot.h:22,
:info:build                  from tube.c:25:
:info:build /usr/include/stdio.h:446: error: expected identifier or ‘(’ before ‘void’
:info:build /usr/include/stdio.h:446: error: expected ‘)’ before numeric constant
:info:build make[1]: *** [tube.o] Error 1
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_beanstalkd/beanstalkd/work/beanstalkd-1.4.6'
:info:build make: *** [all] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_beanstalkd/beanstalkd/work/beanstalkd-1.4.6'
:info:build shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_beanstalkd/beanstalkd/work/beanstalkd-1.4.6" && /usr/bin/make -j4 -w all " returned error 2
:error:build Target org.macports.build returned: shell command failed (see log for details)
:debug:build Backtrace: shell command failed (see log for details)
    while executing
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"
:info:build Warning: the following items did not execute (for beanstalkd): org.macports.activate org.macports.build org.macports.destroot org.macports.install
:notice:build Log for beanstalkd is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_beanstalkd/beanstalkd/main.log
Note: See TracTickets for help on using tickets.