Opened 7 years ago

Closed 7 years ago

#54033 closed defect (wontfix)

clisp @2.49_4 fails to configure

Reported by: murrayE Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.4.1
Keywords: Cc: easiest
Port: clisp

Description

Under macOS Sierra (10.12.4) with Xcode 8.3.2 (and the Xcode command-line tools just updated today through App Store), trying to upgrade crisp to 2.49_4 gave a build failure.

Error seems to be here (from log):

:info:configure config.status: creating po/Makefile.in
:info:configure dyld: Library not loaded: /opt/local/lib/libreadline.6.dylib
:info:configure   Referenced from: /opt/local/bin/gawk
:info:configure   Reason: image not found
:info:configure ./config.status: line 1771: 16646 Done                    eval sed \"\$ac_sed_extra\" "$ac_file_inputs"
:info:configure      16647 Abort trap: 6           | $AWK -f "$tmp/subs.awk" > $tmp/out
:info:configure config.status: error: could not create po/Makefile.in
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_clisp/clisp/work/clisp-2.49" && ./configure --prefix=/opt/local --with-libreadline-prefix=/opt/local --with-libsigsegv-prefix=/opt/local --with-libiconv-prefix=/opt/local 
:info:configure Exit code: 1
:error:configure Failed to configure clisp: configure failure: command execution failed

Attachments (1)

clisp_main.log (41.6 KB) - added by murrayE 7 years ago.
main.log

Download all attachments as: .zip

Change History (3)

Changed 7 years ago by murrayE

Attachment: clisp_main.log added

main.log

comment:1 Changed 7 years ago by murrayE

OK now: after updating all other ports that did not get updated in same job as the failed clisp build, after cleaning clisp I was able to update that, too, with no error.

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

Keywords: configure fail removed
Resolution: wontfix
Status: newclosed
Summary: clisp-2.49_4 fails to configureclisp @2.49_4 fails to configure

As I said in another ticket today, the problem is that standard configure scripts automatically check for common utilities like gawk which are then used during the build process. So when trying to build clisp, its configure script finds the already-installed broken copy of gawk, and tries to use it during the build, which fails. The solution is to deactivate gawk, then upgrade gawk, before trying to build any ports with such configure scripts.

sudo port -f deactivate gawk
sudo port clean gawk
sudo port -u upgrade gawk
Note: See TracTickets for help on using tickets.