Autoconf 2.68 vs. 2.67 problem

[Dominik Reichardt]

Hi all,

please disregard this all.

The autogen warnings are just that, warnings, which can be avoided by fixing configure.in files with this information:
http://lists.gnu.org/archive/html/bug-autoconf/2010-09/msg00092.html

The problem with Dosbox was partially that I didn't run into this problem before for some reason, but to build in 32bit the compiler binaries need to be set to arch i386 as well.

Problem fixed :)

Thanks anyway and sorry for the spam :)

Dominik

> 
> Am 05.01.2011 um 00:45 schrieb ~suv:
> 
>>> $ ./autogen.sh
>>> Generating build information using aclocal, autoheader, automake and autoconf
>>> This may take a while ...
>>> configure.in:41: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
>>> ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
>>> ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from...
>>> ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from...
>>> configure.in:41: the top level
>> <...>
>>> Now you are ready to run ./configure.
>> 
>>> Anyone know what is going on here? I have it confirmed by at least
>>> two other users that they ran into this problem.
>>> 
>>> Known issue? Something that DOSBox' autogen.sh/configure.in does
>>> wrong? I couldn't find a tracker for this.
>> 
>> Similar warning messages occur when running autogen.sh on a checkout or
>> local branch of Inkscape trunk (outside of MacPorts, but using the
>> dependencies installed via an up-to-date MacPorts installation) - only
>> noticed after the autoconf port was updated to 2.68. It doesn't cause
>> any configure and/or build failures though for Inkscape AFAICT.
>> 
>> 
>> (Attached log file is from 2010-11-09; warnings still occur when
>> rebuilding after updating the checkout/branch via bazaar)
> 
> On the Autoconf mailinglist I found this http://lists.gnu.org/archive/html/autoconf/2010-09/msg00075.html hinting that libtool 2.4 needs to be installed, but... that is installed.
> 
> To clarify,I was thinking that these were just some odd warnings as well, but found that when I want to compile Dosbox in 32bit by adding some -arch i386 flags this would no longer work with autoconf 2.68 (I'd get host and build each i386-darwin... with autconf 2.68 I get host and build each x86_64-darwin...). 
> Interestingly it would still create a 32bit binary of Dosbox (lipo report) but which would exhibit issues of a 64bit Dosbox built (crash with dosbox setting core=dynamic).
> So there is definitely some issue here.
> 
> Thanks for confirming the warnings, ~suv.
> 
> Take care
> 
> Dom

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20110106/d722dfc9/attachment.html>