Opened 14 years ago
Closed 14 years ago
#25509 closed defect (fixed)
autoreconf failure "warning: AC_INIT: not a literal" in autoconf-2.67
Reported by: | dong5600@… | Owned by: | skymoo (Adam Mercer) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.1 |
Keywords: | Cc: | tflynn@…, jeremyhu (Jeremy Huddleston Sequoia), pavlo72@…, mjhsieh@…, fblanch@…, macports@…, ryandesign (Ryan Carsten Schmidt), EJFielding (Eric Fielding), adparker@…, sengupta_jit@…, ghosthound | |
Port: | autoconf pkgconfig xorg-libXp xorg-libXtrap xorg-libAppleWM xorg-libXevie |
Description (last modified by skymoo (Adam Mercer))
I am inexperience in macports. I need to install Arb on Mac OS X 10.6.4. After I installed Xcode and X11 and followed the protocol to install and update MacPorts to 10.9.1, I used "sudo port -d install arb" but the installation cannot be finished and the error information at the end is:
autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force configure.ac:28: warning: AC_INIT: not a literal: https://bugs.freedesktop.org/enter_bug.cgi?product=xorg autoreconf: configure.ac: tracing configure.ac:28: warning: AC_INIT: not a literal: https://bugs.freedesktop.org/enter_bug.cgi?product=xorg autoreconf: running: glibtoolize --copy --force glibtoolize: putting auxiliary files in `.'. glibtoolize: copying file `./ltmain.sh' glibtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and glibtoolize: rerunning glibtoolize, to keep the correct libtool macros in-tree. glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.ac:28: warning: AC_INIT: not a literal: https://bugs.freedesktop.org/enter_bug.cgi?product=xorg autoreconf: running: /opt/local/bin/autoconf --force configure.ac:28: warning: AC_INIT: not a literal: https://bugs.freedesktop.org/enter_bug.cgi?product=xorg configure:10695: error: possibly undefined macro: AS_MESSAGE_LOG_FDdnl If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /opt/local/bin/autoconf failed with exit status: 1 shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-libXp/work/libXp-1.0.0" && autoreconf --install -fvi " returned error 1 Error: Target org.macports.configure returned: autoreconf failure: shell command failed DEBUG: Backtrace: autoreconf failure: shell command failed while executing "$procedure $targetname" Warning: the following items did not execute (for xorg-libXp): org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install Log for xorg-libXp is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-libXp/main.log Error: The following dependencies failed to build: glw openmotif xorg-libXp gsed imake xorg-cf-files lynx openssl sablotron spidermonkey nspr readline tiff Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets>
Change History (28)
comment:1 Changed 14 years ago by skymoo (Adam Mercer)
Cc: | ram@… added |
---|---|
Description: | modified (diff) |
Port: | autoconf added |
Priority: | High → Normal |
Type: | request → defect |
Version: | 1.9.1 |
comment:2 Changed 14 years ago by jmroot (Joshua Root)
Cc: | jeremyhu@… added |
---|---|
Port: | xorg-libXp added |
Version: | → 1.9.1 |
comment:3 Changed 14 years ago by henry.pfister@…
I am having a very similar problem with xorg-libXp (or autoconf) with 10.5.8.
And I am using the latest version @2.66_1 of autoconf.
The error message (starting from where things start to fail) is:
configure.ac:28: warning: AC_INIT: not a literal: https://bugs.freedesktop.org/enter_bug.cgi?product=xorg autoreconf: running: /opt/local/bin/autoconf --force configure.ac:28: warning: AC_INIT: not a literal: https://bugs.freedesktop.org/enter_bug.cgi?product=xorg configure:10695: error: possibly undefined macro: AS_MESSAGE_LOG_FDdnl If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /opt/local/bin/autoconf failed with exit status: 1 shell command " cd "/Users/hpfister/.macports/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-libXp/work/libXp-1.0.0" && autoreconf --install -fvi " returned error 1 Error: Target org.macports.configure returned: autoreconf failure: shell command failed
comment:5 Changed 14 years ago by Zignal64@…
I started getting the same error with the recent release of autoconf v2.66 in trying to build mplayer.
"if this token and others are legitimate, please use m4_pattern_allow."
Loaded macports on one system June 26 2010 no issues.
Loaded macports today July 4 2010 on another system and started receiving the error.
Both systems fresh install of 10.6.3 updated to 10.6.4 with Xcode 3.2.2
Build process still works on the June 26 system which still has autoconf v2.65.
ports installed: autoconf automake libtool pkgconfig freetype fontconfig libiconv ncurses zlib lzo2
Error example with libass:
$ autoreconf -ivf autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I shave autoreconf: configure.ac: tracing autoreconf: running: glibtoolize --copy --force glibtoolize: putting auxiliary files in `.'. glibtoolize: copying file `./ltmain.sh' glibtoolize: putting macros in AC_CONFIG_MACRO_DIR, `shave'. glibtoolize: copying file `shave/libtool.m4' glibtoolize: copying file `shave/ltoptions.m4' glibtoolize: copying file `shave/ltsugar.m4' glibtoolize: copying file `shave/ltversion.m4' glibtoolize: copying file `shave/lt~obsolete.m4' autoreconf: running: /opt/local/bin/autoconf --force configure:12439: error: possibly undefined macro: AS_MESSAGE_LOG_FDdnl If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /opt/local/bin/autoconf failed with exit status: 1
comment:6 Changed 14 years ago by Zignal64@…
Just wanted to clarify this isn't strictly a autoconf xorg-libXp issue and affects other projects.
comment:7 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Does updating to autoconf @2.66_2 and then cleaning the failing port help?
comment:8 follow-up: 10 Changed 14 years ago by Zignal64@…
Same error with autoconf @2.66, Revision 2 (devel)
comment:10 Changed 14 years ago by mjhsieh@…
Replying to Zignal64@…:
Same error with autoconf @2.66, Revision 2 (devel)
I confirm this observation. I still saw the "AC_INIT: not a literal" warnings and "possibly undefined macro: AS_MESSAGE_LOG_FDdnl" error.
comment:11 Changed 14 years ago by fblanch@…
I don't have any experience on macports either and i'm having the same problem when i try to install rabbitMQ
These is my log trace if it helps:
---> Fetching xorg-libXp ---> Attempting to fetch libXp-1.0.0.tar.bz2 from http://lil.fr.distfiles.macports.org/xorg-libXp ---> Verifying checksum(s) for xorg-libXp ---> Extracting xorg-libXp ---> Configuring xorg-libXp Error: Target org.macports.configure returned: autoreconf failure: shell command failed Log for xorg-libXp is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-libXp/main.log Error: The following dependencies failed to build: xmlto texlive texlive-basic texlive-bin openmotif xorg-libXp poppler gtk2 atk glib2 gtk-doc gnome-doc-utils iso-codes p5-xml-parser py26-libxml2 python26 bzip2 db46 gdbm openssl readline sqlite3 tk tcl xorg-libXScrnSaver xorg-scrnsaverproto rarian intltool gnome-common p5-getopt-long p5-pathtools p5-scalar-list-utils jasper pango shared-mime-info xorg-libXcomposite xorg-compositeproto xorg-libXfixes xorg-fixesproto xorg-libXcursor xorg-libXdamage xorg-damageproto xorg-libXi xorg-libXinerama xorg-xineramaproto xorg-libXrandr xorg-randrproto lcms openjpeg poppler-data t1lib texlive-common texlive-documentation-base texlive-bin-extra texlive-context texlive-latex texlive-metapost texlive-documentation-english texlive-fonts-recommended texlive-fontutils texlive-generic-recommended texlive-lang-czechslovak texlive-lang-dutch texlive-lang-french texlive-lang-german texlive-lang-italian texlive-lang-polish texlive-lang-portuguese texlive-lang-spanish texlive-lang-ukenglish texlive-latex-recommended texlive-luatex texlive-math-extra texlive-xetex texlive-htmlxml Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets>
Any idea on how to solve it? My system is Snow Leopard 10.6.3. and autoconf version 2.61
comment:14 follow-up: 15 Changed 14 years ago by macports@…
I had need to get other autoconf-dependent software working quickly, so I needed a workaround.
It appears this was introduced with autoconf 2.66 upstream, and the maintainer indicated official release with fix was a couple weeks out, so I stopped looking for patches, and started looking for a downgrade path to 2.65.
I've never had 2.65 installed on this machine, so here is how I went about installing it - per the howto on installing old ports @ http://trac.macports.org/wiki/howto/InstallingOlderPort
cd /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/autoconf port uninstall autoconf curl https://svn.macports.org/export/66088/trunk/dports/devel/autoconf/Portfile > Portfile curl https://svn.macports.org/export/66088/trunk/dports/devel/autoconf/files/0001-Fix-AC_FUNC_MMAP-regression-with-C-compiler-in-2.65.patch > files/0001-Fix-AC_FUNC_MMAP-regression-with-C-compiler-in-2.65.patch curl https://svn.macports.org/export/66088/trunk/dports/devel/autoconf/files/0002-Fix-2.64-AC_TYPE_INT-_T-macro-body-text-regression.patch > files/0002-Fix-2.64-AC_TYPE_INT-_T-macro-body-text-regression.patch port install autoconf
That installed autoconf @ 2.65_1 and other software was able to successfully build with it
comment:15 Changed 14 years ago by skymoo (Adam Mercer)
Replying to macports@…:
I had need to get other autoconf-dependent software working quickly, so I needed a workaround.
I sent an email to macports-users about an hour ago, I'm going to revert autoconf to 2.65_1 later on this afternoon. Then the upgrade can be revisited once upstream fixes this properly.
comment:16 Changed 14 years ago by skymoo (Adam Mercer)
Resolution: | → fixed |
---|---|
Status: | new → closed |
autoconf has been reverted back to 2.65_1 in r69426
comment:17 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Resolution: | fixed |
---|---|
Status: | closed → reopened |
2.67 was added in r70297 , so this is once again a problem...
comment:18 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Summary: | autoreconf failure → autoreconf failure "warning: AC_INIT: not a literal" in autoconf-2.67 |
---|
observerved with 2.67_0, does not occur with 2.65_2. xorg-server-devel fails due to "warning: AC_INIT: not a literal"
comment:19 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Owner: | changed from macports-tickets@… to ram@… |
---|---|
Status: | reopened → new |
comment:20 Changed 14 years ago by skymoo (Adam Mercer)
Cc: | ryandesign@… added; ram@… removed |
---|---|
Port: | pkgconfig added |
Damn it. The AC_INIT issue was reported upstream yesterday and the maintainer hopes to have a fix soon. I'll give upstream till next week and then revert (again) if a fix hasn't materialised.
Regarding the AS_MESSAGE_LOG_FDdnl
error, this appears to be an underquoting bug in pkg-config: <http://thread.gmane.org/gmane.comp.sysutils.autoconf.general/13133/focus=13153>
comment:23 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Port: | xorg-libXtrap xorg-libAppleWM xorg-libXevie added |
---|
"AC_INIT" problem affects xorg-libXp, xorg-libAppleWM (#25986), xorg-libXtrap, xorg-libXevie
comment:26 follow-up: 28 Changed 14 years ago by skymoo (Adam Mercer)
Patches for pkg-config, added to #26030, to fix the AS_MESSAGE_LOG_FDdnl
error which is the actual cause of the failures as the AC_INIT
issue is only a warning.
comment:28 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
What version of autoconf are you using? The latest is @2.66_1 which was committed an hour or so ago, make sure you using this version.