[MacPorts] #31834: sbcl 1.0.52 doesn't build on 10.6.8
#31834: sbcl 1.0.52 doesn't build on 10.6.8 --------------------------------+------------------------------------------- Reporter: jrjsmrtn@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: sbcl --------------------------------+------------------------------------------- Hello... I just found that installing sbcl 1.0.52 on 10.6.8 ends with: {{{ ... gcc -g -Wall -O2 -fdollars-in-identifiers -mmacosx-version-min=10.5 -D_DARWIN_USE_64_BIT_INODE -arch x86_64 -fno-omit-frame-pointer -pagezero_size 0x100000 -I. -DSBCL_PREFIX=\"'/opt/local'\" -c -o alloc.o alloc.c cc1: error: unrecognized command line option "-arch" make: *** [alloc.o] Error 1 shell command "ulimit -s 8192 && unset LD_PREBIND && unset LD_PREBIND_ALLOW_OVERLAP && cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_sbcl/sbcl/work/sbcl-1.0.52 && CC=/Developer/usr/bin/llvm-gcc-4.2 CXX=/Developer/usr/bin/llvm-g++-4.2 CPP=/Developer/usr/bin/llvm-cpp-4.2 sh make.sh "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_sbcl/sbcl/work/sbcl-1.0.48-x86-darwin/src/runtime/sbcl --core /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_sbcl/sbcl/work/sbcl-1.0.48-x86-darwin/output/sbcl.core --disable-debugger --sysinit /dev/null --userinit /dev/null" --prefix=/opt/local" returned error 2 Error: Target org.macports.build returned: shell command failed (see log for details) Warning: the following items did not execute (for sbcl): org.macports.activate org.macports.build org.macports.destroot org.macports.install Log for sbcl is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_sbcl/sbcl/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> }}} Log file is enclosed. -- Ticket URL: <https://trac.macports.org/ticket/31834> MacPorts <http://www.macports.org/> Ports system for Mac OS
#31834: sbcl: cc1: error: unrecognized command line option "-arch" --------------------------------+------------------------------------------- Reporter: jrjsmrtn@… | Owner: easieste@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: sbcl --------------------------------+------------------------------------------- Changes (by ryandesign@…): * cc: gwright@…, waqar@…, ryandesign@… (added) * owner: macports-tickets@… => easieste@… Comment: What is "gcc" on your system? It sounds like you have made a different compiler the default than /usr/bin/gcc-4.2, using "sudo port select gcc" or manually changing the symlink. It's not surprising that sbcl isn't UsingTheRightCompiler since we already know it's not using the right archflags (#29832). It looks like the port is trying to use the right compiler, but apparently some edge case was missed. I had been working on a fix to #29832 that included changes for using the right compiler... I'll see if I can dust that off and finish it. -- Ticket URL: <https://trac.macports.org/ticket/31834#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#31834: sbcl: cc1: error: unrecognized command line option "-arch" --------------------------------+------------------------------------------- Reporter: jrjsmrtn@… | Owner: easieste@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: sbcl --------------------------------+------------------------------------------- Comment(by jason.swails@…): Replying to [comment:1 ryandesign@…]:
What is "gcc" on your system? It sounds like you have made a different compiler the default than /usr/bin/gcc-4.2, using "sudo port select gcc" or manually changing the symlink. It's not surprising that sbcl isn't UsingTheRightCompiler since we already know it's not using the right archflags (#29832). It looks like the port is trying to use the right compiler, but apparently some edge case was missed.
I had been working on a fix to #29832 that included changes for using the right compiler... I'll see if I can dust that off and finish it.
I saw the same behavior when my gcc was set to mp-gcc44. Resetting to gcc42 and rebuilding fixed the issue, which is a temporary workaround. Obviously if a command uses "gcc" instead of /usr/bin/gcc-4.2, it'll just pull the currently selected MacPorts one... -- Ticket URL: <https://trac.macports.org/ticket/31834#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#31834: sbcl: cc1: error: unrecognized command line option "-arch" --------------------------------+------------------------------------------- Reporter: jrjsmrtn@… | Owner: easieste@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: sbcl --------------------------------+------------------------------------------- Comment(by ryandesign@…): Georges sent me this reply by email:
Indeed... I switched to mp-gcc44 and forgot to get back to llvm-gcc42. [[br]] [[br]] sbcl is now building fine.
So indeed sbcl needs changes to ensure it's UsingTheRightCompiler in all cases. -- Ticket URL: <https://trac.macports.org/ticket/31834#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#31834: sbcl: cc1: error: unrecognized command line option "-arch" --------------------------------+------------------------------------------- Reporter: jrjsmrtn@… | Owner: easieste@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: sbcl --------------------------------+------------------------------------------- Comment(by jonathan.braud@…): Replying to [comment:1 ryandesign@…]:
I had been working on a fix to #29832 that included changes for using the right compiler... I'll see if I can dust that off and finish it.
I'm having the same problem (my `gcc` is `/opt/local/bin/gcc`), so I tracked down the problem. I see the portfile exports `CC`, but this is not enough because `tools-for-build/Makefile` includes `src/runtime/Config`, which defines `CC = gcc`. So I attached a patch that removes that line. I don't know how to integrate it into the tarball. Should I contact the owner directly or is it enough that they are Cc-ed? -- Ticket URL: <https://trac.macports.org/ticket/31834#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#31834: sbcl: cc1: error: unrecognized command line option "-arch" ---------------------------------+------------------------------------------ Reporter: jrjsmrtn@… | Owner: easieste@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: fixed | Keywords: Port: sbcl | ---------------------------------+------------------------------------------ Changes (by easieste@…): * status: new => closed * resolution: => fixed Comment: Let the macport envirnoment supply the determination of gcc. [r90328](): Supplemented the attached 'patch-use-right-gcc' diff which deletes reference to SBCL platform specific 'src/runtime/Config.x86-64-darwin. Probably not necessary to push back upstream (???). [r90328]: https://trac.macports.org/changeset/90328 -- Ticket URL: <https://trac.macports.org/ticket/31834#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts