Re: update to autoconf 2.69

--===============1081714249==
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"

--=-=-=

Kamil Dudka <[email protected]> writes:

> would it be possible to use autoconf 2.69+ for creating the new releases
> of elinks in order to support the ARM 64 bit CPU architecture (aarch64)?

I'm not sure it's permitted under the GPLv2 license of configure.in.
The license requires that source files are distributed under GPLv2.
I think /usr/share/autoconf/autoconf/general.m4 may be a source file
of the resulting configure script, but in Autoconf 2.69, that file
is under GPLv3-or-later + Autoconf Configure Script Exception v3.
The exception grants permission to propagate the configure script,
but not to distribute general.m4 itself under GPLv2.

I don't see any license problems with upgrading just config.guess
and config.sub.  The patch linked from
https://bugzilla.redhat.com/show_bug.cgi?id=925306 does not
change the GPLv2-or-later license of those files.  Even if we
upgraded to the 2013-02-12 versions, which are under
GPLv3-or-later, it seems the "special exception" would allow us
to distribute them under GPLv2 as part of ELinks, which is
licensed under GPLv2 and contains a configure script generated by
Autoconf.  They don't say it has to be the latest version of
Autoconf.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlFjX8AACgkQHm9IGt60eMgrLwCfVmrdPn1Jl2Tn91Ra0CDyosnn
JxIAoLD1jpbmBrITiQ5p41z4zp5Eh7w1
=bW9J
-----END PGP SIGNATURE-----
--=-=-=--

--===============1081714249==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
elinks-dev mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-dev

--===============1081714249==--