-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dave Korn wrote:
| This bit causes me problems. For some reason the autoreconf stage only
| regenerates the configure scripts in the top level and in the libstdc++-v3
| subdir. The original configure scripts in the gcc tarball are built by
| autoconf-2.59, but I've got 2.61 on my build machine. The consequence is
| that I end up with a mixture of 2.59 and 2.61 configure scripts, and
| confargs are set appropriately for the top-level 2.61-built script, which
| means that when we configure in the subdirs based on 2.59-built
scripts, it
| errors out:
| Is the autoreconf step meant to regenerate all configure scripts,
| regardless, or is this (mixed-version configure scripts in one build)
just a
| corner-case that isn't handled?
autoreconf will regenerate subdir configure scripts that are defined in
AC_CONFIG_SUBDIRS. Running subdir configure's without this macro is
definitely a corner case; you'll need to do something like:
src_compile() {
local d
cd ${S}
for d in $(find . -name configure.ac)
do
(cd ${S}/${d%/*}; cygautoreconf)
done
cd ${B}
...
}
Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkhDMcYACgkQpiWmPGlmQSNqGQCeMcxrRMUvo1IQy2v7OugwTcbd
5U0An1bt5TtTlpRW8fwrMAXic1IpxA05
=f5i9
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Cygwin-ports-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
