Opened 11 years ago
Last modified 11 years ago
#39345 new defect
spim @7.4 build failed - Command execution failed
Reported by: | labyrinthinsidious@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | ||
Port: | spim |
Description
On attempting to install spim, I get the following:
Error: org.macports.build for port spim returned: command execution failed Please see the log file for port spim for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulators_spim/spim/main.log
When I check main.log, I see this:
:info:build ../CPU/spim-utils.c:500: error: expected ‘)’ before numeric constant :info:build ../CPU/spim-utils.c:503: error: expected identifier or ‘(’ before ‘{’ token :info:build ../CPU/spim-utils.c:519: error: conflicting types for ‘strtol’ :info:build /usr/include/stdlib.h:181: error: previous declaration of ‘strtol’ was here :info:build make[1]: *** [spim-utils.o] Error 1 :info:build make: *** [spim] Error 2 :info:build Command failed: cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulators_spim/spim/work/spim-7.4/spim && make prefix=/opt/local spim :info:build Exit code: 2 :error:build org.macports.build for port spim returned: command execution failed :debug:build Error code: NONE :debug:build Backtrace: command execution failed while executing "$procedure $targetname" :info:build Warning: targets not executed for spim: org.macports.activate org.macports.build org.macports.destroot org.macports.install
I tried fiddling with the source code in spim-utils.c, but my C programming is still fairly amateur.
Change History (2)
comment:1 Changed 11 years ago by labyrinthinsidious@…
Cc: | labyrinthinsidious@… added |
---|
comment:2 Changed 11 years ago by mf2k (Frank Schima)
Cc: | labyrinthinsidious@… removed |
---|---|
Port: | spim added; 2.1.3 removed |
In the future, please fill in the Port field with the name of the failed port. You do not need to Cc yourself since you are the reporter. As always, attach the complete main.log file after cleaning the port first.
Note: See
TracTickets for help on using
tickets.
Cc Me!