Bug#584607: libc6: autoconf configure scripts hang at "checking whether a statically linked program can dlopen itself"

[Aurelien Jarno <aurelien@aurel32.net>]

On Sat, Jun 05, 2010 at 12:45:33AM -0300, Nicolás Alvarez wrote:
> On 6/4/10, Clint Adams <schizo@debian.org> wrote:
> > On Fri, Jun 04, 2010 at 10:08:06PM -0300, Nicolás Alvarez wrote:
> >> I'm using a Debian testing/unstable mix. Most packages are from testing
> >> (squeeze). Today, I upgraded to libc from 2.10.2-9 to the version from
> >> unstable (2.11.1-2). After the upgrade, autoconf-generated configure
> >> scripts stopped working. They hang on this step:
> >>
> >> [...]
> >> checking whether a program can dlopen itself... yes
> >> checking whether a statically linked program can dlopen itself...
> >
> > I cannot reproduce this.  Could you be more specific about which configure
> > script is involved?
> 
> This seems enough to reproduce.
> 
> configure.ac:
> AC_INIT(bug584607, 0.1)
> AM_INIT_AUTOMAKE(foreign)
> AC_LIBTOOL_DLOPEN
> LT_INIT
> AC_CONFIG_FILES([Makefile])
> 
> Makefile.am:
> bin_SCRIPTS=x
> 
> Run autoreconf -i && ./configure.
> 

You also need to have binutils gold instead of the default binutils.

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net