On Tuesday 09 April 2013 02:24:19 Kalle Olavi Niemitalo wrote:
> Kamil Dudka <kdu...@redhat.com> 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.

Yes, just updating config.guess and config.sub should do the job.  We are 
currently discussing an alternative solution -- replacing those files during 
build by our build system.  Nevertheless, it makes still sense to get the 
upstream tarballs working on aarch64 out of the box, which can be achieved
by using up2date config.guess and config.sub in the tarballs of upcoming 
ELinks' releases as you suggest.

elinks-dev mailing list

Reply via email to