Your message dated Mon, 02 Aug 2010 13:15:39 -0700
with message-id <[email protected]>
and subject line Bug #539761: undefined ac_fn_cxx_try_run
has caused the Debian Bug report #539761,
regarding autoconf: bad interaction between AC_CHECK_LIB and AC_SEARCH_LIBS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
539761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539761
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: autoconf
version: 2.64-2
severity: normal
The new autoconf in squeeze generates configure scripts that error out
with:
checking for socket... ./configure: line 1399: ac_fn_c_try_link: command not
found
when you write code of the form:
AC_CHECK_FUNC([socket], :, AC_CHECK_LIB([socket], [socket]))
followed eventually by
AC_SEARCH_LIBS([socket], [socket])
I've attached a sample configure.in script that reproduces the problem; a
corresponding tarball is available at
<http://web.mit.edu/tabbott/Public/actest.tgz>.
-Tim AbbottAC_INIT
AC_PROG_CC
AC_PROG_INSTALL
AC_PROG_RANLIB
AC_CHECK_FUNC([socket], :, AC_CHECK_LIB([socket], [socket]))
AC_SEARCH_LIBS([socket], [socket])
AC_CONFIG_FILES([Makefile])
AC_OUTPUT
--- End Message ---
--- Begin Message ---
I'm looking through old bugs before uploading Autoconf 2.67.
Amos Jeffries <[email protected]> reported that a configure
script failed due to the ac_fn_cxx_try_run helper function being
undefined on first use.
In a reply, Yavor Doganov <[email protected]> pointed out that using
proper m4 quoting fixes the problem.
This seems to me a proper and complete response (unless Amos or
someone else can point out why the quoting should not be
necessary), so I am closing this bug (with this email).
--
Ben Pfaff
http://benpfaff.org
--- End Message ---
