Opened 16 years ago
Closed 15 years ago
#18253 closed defect (wontfix)
emacs-app on 10.4 PPC: C compiler cannot create executables
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | cssdev |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.7.0 |
Keywords: | Cc: | joda@… | |
Port: | emacs-app |
Description
emacs-app does not pass configuration on Mac OS X 10.4.11 on PowerPC with Xcode 2.5 and MacPorts 1.7.0:
$ port install emacs-app ---> Fetching emacs-app ---> Verifying checksum(s) for emacs-app ---> Extracting emacs-app ---> Configuring emacs-app ---> Building emacs-app Error: Target org.macports.build returned: shell command " cd "/mp/var/macports/build/_Volumes_data_macports_ports_aqua_emacs-app/work/emacs-23.0.0_NS-9.0rc3/nextstep" && nice -n 10 ./compile " returned error 1 Command output: ./configure --with-ns --without-x --prefix=/mp/var/macports/build/_Volumes_data_macports_ports_aqua_emacs-app/work/emacs-23.0.0_NS-9.0rc3/nextstep/build/Emacs.app/Contents/Resources --exec_prefix=/mp/var/macports/build/_Volumes_data_macports_ports_aqua_emacs-app/work/emacs-23.0.0_NS-9.0rc3/nextstep/build/Emacs.app/Contents/MacOS --libexecdir=/mp/var/macports/build/_Volumes_data_macports_ports_aqua_emacs-app/work/emacs-23.0.0_NS-9.0rc3/nextstep/build/Emacs.app/Contents/MacOS/libexec --with-pop --enable-font-backend --without-freetype checking build system type... powerpc-apple-darwin8.11.0 checking host system type... powerpc-apple-darwin8.11.0 checking for gcc... gcc-4.0 checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. *** Configure run failed. *** Please examine the above output to determine what went wrong, edit this script (\'compile\') to fix it, and rerun. Error: Status 1 encountered during processing.
Joe Davison originally reported this on macports-users.
The bigger problem is that emacs-app tries to build itself universal, even if the +universal variant has not been selected.
Furthermore, it has its own ideas about which deployment target and SDK it wants to use and for what architectures it will build. It should use the values the user has specified in macports.conf.
Finally there is a section in the portfile which reads
# Don't attempt to build universal on darwin 7, so apply a patch # to modify the compile script. platform darwin 7 { patchfiles-append patch-compile.diff }
but the patch has nothing to do with universal building. All it does is change CC from "gcc-4.0" (which exists only on Tiger and up) to "gcc", but neither of these values is correct; on all versions of Mac OS X, should always use the MacPorts variable ${configure.cc}.
Change History (3)
comment:1 Changed 16 years ago by cssdev
Status: | new → assigned |
---|
comment:3 Changed 15 years ago by tobypeterson
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
no response in 7 months - unsupported platform - closing
Given the complexity of the
compile
script, I would look upstream for a fix. That's not likely to come for this particular version since emacs-app has been integrated into the official emacs development trunk. Could you try building emacs-app-devel instead to see if that works any better?