Opened 10 years ago

Closed 10 years ago

#45953 closed defect (fixed)

libast @0.7: error: required file './compile' not found

Reported by: henry.debens@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.3.2
Keywords: Cc:
Port: libast

Description

Problems installing libast port on OS X 10.10 (Xcode 6.1):

sudo port install -v libast
--->  Computing dependencies for libast
--->  Fetching archive for libast
--->  Attempting to fetch libast-0.7_5.darwin_14.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/libast
--->  Attempting to fetch libast-0.7_5.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/libast
--->  Attempting to fetch libast-0.7_5.darwin_14.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/libast
--->  Fetching distfiles for libast
--->  Verifying checksums for libast
--->  Extracting libast
--->  Applying patches to libast
--->  Configuring libast
Error: org.macports.configure for port libast returned: autoreconf failure: command execution failed
Please see the log file for port libast for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libast/libast/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port libbers failed

Log file attached - any help much appreciated!

Attachments (1)

main.log (59.1 KB) - added by henry.debens@… 10 years ago.
Log file

Download all attachments as: .zip

Change History (6)

Changed 10 years ago by henry.debens@…

Attachment: main.log added

Log file

comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Summary: libast @ 0.7 Configure error - build failurelibast @0.7: error: required file './compile' not found

comment:2 in reply to:  description ; Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to henry.debens@…:

sudo port install -v libast

Note that single-letter flags like -v do nothing unless placed immediately after the word port, i.e. sudo port -v install libast.

comment:3 in reply to:  2 Changed 10 years ago by henry.debens@…

Replying to ryandesign@…:

Replying to henry.debens@…:

sudo port install -v libast

Note that single-letter flags like -v do nothing unless placed immediately after the word port, i.e. sudo port -v install libast.

I see, thank you for your reply - the terminal output is now as follows:

sudo port -v install libast
--->  Computing dependencies for libast.
--->  Fetching archive for libast
--->  libast-0.7_5.darwin_14.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified
--->  Attempting to fetch libast-0.7_5.darwin_14.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/libast
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0--->  Attempting to fetch libast-0.7_5.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/libast
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0--->  Attempting to fetch libast-0.7_5.darwin_14.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/libast
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0--->  Fetching distfiles for libast
--->  Verifying checksums for libast
--->  Checksumming libast-0.7.tar.gz
--->  Extracting libast
--->  Extracting libast-0.7.tar.gz
--->  Applying patches to libast
--->  Applying patch-automake-1.13.diff
patching file configure.in
--->  Configuring libast
autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal -I /opt/local/share/aclocal -I . --force 
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:50: warning: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET
../../lib/autoconf/general.m4:1833: AC_CANONICAL_TARGET is expanded from...
configure.in:50: the top level
autoreconf: configure.in: tracing
configure.in:50: warning: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET
../../lib/autoconf/general.m4:1833: AC_CANONICAL_TARGET is expanded from...
configure.in:50: the top level
autoreconf: configure.in: not running libtoolize: --install not given
autoreconf: running: /opt/local/bin/autoconf --force
configure.in:50: warning: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET
../../lib/autoconf/general.m4:1833: AC_CANONICAL_TARGET is expanded from...
configure.in:50: the top level
autoreconf: running: /opt/local/bin/autoheader --force
configure.in:50: warning: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET
../../lib/autoconf/general.m4:1833: AC_CANONICAL_TARGET is expanded from...
configure.in:50: the top level
autoreconf: running: automake --force-missing
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:50: warning: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET
../../lib/autoconf/general.m4:1833: AC_CANONICAL_TARGET is expanded from...
configure.in:50: the top level
configure.in:22: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated.  For more info, see:
configure.in:22: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.in:52: error: required file './compile' not found
configure.in:52:   'automake --add-missing' can install 'compile'
src/Makefile.am:5: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
test/Makefile.am:5: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
autoreconf: automake failed with exit status: 1
Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libast/libast/work/libast-0.7" && autoreconf -fv 
Exit code: 1
Error: org.macports.configure for port libast returned: autoreconf failure: command execution failed
Warning: targets not executed for libast: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install
Please see the log file for port libast for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libast/libast/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port libast failed
Last edited 10 years ago by henry.debens@… (previous) (diff)

comment:4 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned

The problem is that in a recent version of MacPorts base some default autoreconf args moved from autoreconf.pre_args to autoreconf.args. This port runs autoreconf and requires the -i argument, and expected MacPorts to set it in autoreconf.pre_args, but now MacPorts sets it in autoreconf.args. This port overrides autoreconf.args, so -i wasn't being set anymore.

comment:5 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.