Opened 2 years ago
Closed 17 months ago
#65736 closed defect (fixed)
ffcall fails on Rosetta
Reported by: | barracuda156 | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.2 |
Keywords: | powerpc, rosetta, snowleopard | Cc: | mascguy (Christopher Nielsen), MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
Port: | ffcall |
Description (last modified by barracuda156)
:info:build cd avcall && /usr/bin/make all :info:build make[1]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ffcall/ffcall/work/libffcall-2.4/avcall' :info:build /usr/bin/gcc-4.2 -std=gnu99 -E `if test true = true; then echo '-DASM_UNDERSCORE'; fi` -I./../common - < ./avcall-i386-macro.S | grep -v '^ *#line' | grep -v '^#' | sed -e 's,% ,%,g' -e 's,\. ,.,g' -e 's,@ ,@,g' -e 's,//.*$,,' -e 's/##//g' > avcall-i386.s :info:build /bin/sh ../libtool --mode=compile /usr/bin/gcc-4.2 -std=gnu99 -x none -c avcall-i386.s :info:build libtool: compile: /usr/bin/gcc-4.2 -std=gnu99 -x none -c avcall-i386.s -fno-common -DPIC -o .libs/avcall-i386.o :info:build avcall-i386.s:8:suffix or operands invalid for `push' :info:build avcall-i386.s:10:suffix or operands invalid for `push' :info:build avcall-i386.s:11:suffix or operands invalid for `push' :info:build avcall-i386.s:72:suffix or operands invalid for `pop' :info:build avcall-i386.s:74:suffix or operands invalid for `pop' :info:build make[1]: *** [avcall-i386.lo] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ffcall/ffcall/work/libffcall-2.4/avcall' :info:build make: *** [all-subdirs] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ffcall/ffcall/work/libffcall-2.4' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ffcall/ffcall/work/libffcall-2.4" && /usr/bin/make -j1 -w all :info:build Exit code: 2 :error:build Failed to build ffcall: command execution failed :debug:build Error code: CHILDSTATUS 18665 2
Attachments (1)
Change History (12)
Changed 2 years ago by barracuda156
Attachment: | ffcall.log added |
---|
comment:1 Changed 2 years ago by barracuda156
Description: | modified (diff) |
---|
comment:2 Changed 2 years ago by barracuda156
comment:3 Changed 2 years ago by barracuda156
Looks like arch flags fail to be added, despite configure setting those.
comment:4 Changed 2 years ago by barracuda156
This worked:
platform darwin 10 powerpc { configure.args-append \ --build=powerpc-apple-darwin${os.major} \ CC="${configure.cc} -arch ${build_arch}" }
UPD. I guess this is a better way:
platform darwin 10 powerpc { configure.args-append \ --build=powerpc-apple-darwin${os.major} \ CC="${configure.cc} [get_canonical_archflags cc]" }
comment:5 follow-up: 7 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)
You have a tendency to propose fixes that are specific to your esoteric scenario of compiling for PowerPC on 10.6 Intel. It seems to me that the problem would also happen on 10.5 or 10.4 Intel but your fix would not cover that case. What do you think? What about the case of compiling for Intel on 10.4 or 10.5 PowerPC — wouldn't that also need a fix? Can you generalize this fix, and the fixes you propose for other ports, to cover all cases?
comment:6 Changed 2 years ago by mascguy (Christopher Nielsen)
Cc: | mascguy added |
---|
comment:7 Changed 2 years ago by barracuda156
Replying to ryandesign:
You have a tendency to propose fixes that are specific to your esoteric scenario of compiling for PowerPC on 10.6 Intel. It seems to me that the problem would also happen on 10.5 or 10.4 Intel but your fix would not cover that case. What do you think? What about the case of compiling for Intel on 10.4 or 10.5 PowerPC — wouldn't that also need a fix? Can you generalize this fix, and the fixes you propose for other ports, to cover all cases?
I cannot test it on <10.6 at the moment, but I can try on 10.6 Intel. It seems to me that default archs will build correctly though (in Rosetta case there is a mismatch, causing the error above).
At the same time perhaps CC="${configure.cc} [get_canonical_archflags cc]"
can be made a general case indeed – could you advise me if this is a correct way, considering general case includes FAT builds as well?
comment:8 follow-up: 9 Changed 2 years ago by kencu (Ken)
the discussion about this is also ongoing in your PR, where generalized fixes were also requested...so perhaps either discuss there, or close the PR and discuss here?
comment:9 Changed 2 years ago by barracuda156
Replying to kencu:
the discussion about this is also ongoing in your PR, where generalized fixes were also requested...so perhaps either discuss there, or close the PR and discuss here?
Sure, moving all discussion to the PR.
comment:10 Changed 17 months ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Cc: | MarcusCalhoun-Lopez added |
---|
comment:11 Changed 17 months ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Owner: | set to MarcusCalhoun-Lopez |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Interestingly, with
--build=powerpc-apple-darwin
it also fails, though differently: