Yep, I'm wrong about the license. It is GPL v2 on those files.
Moreover, it is not necessary for them to be LGPL (our current ones
are not) as they don't end up being linked when the library is built.
So we can use them.

We should first grep for changes to configfsf.sub which we have
heavily modified and make sure those changes go across to the new
versions. I see Jason Moxham has opened a trac ticket for this. I've
slated it for the mpir-1.2 release, but not made it a blocker. If it
should be made a blocker, let me know.

Bill.

On 17 Apr, 05:44, Jason Moxham <ja...@njkfrudils.plus.com> wrote:
> Tryhttp://savannah.gnu.org/projects/config
> orhttp://www.gnu.org/software/gnulib/
>
> On Friday 17 April 2009 02:12:42 Bill Hart wrote:
>
> > I believe we have done quite a bit of hacking to that too.
>
> > The link you gave is not working for me for some reason - I think
> > because it is ftp and I am in an apartment complex with strange
> > internet connection, but I think from memory all those config.guess
> > and configfsf.guess etc were all incompatible license. I could be
> > wrong about this and I cannot check at the moment.
>
> > But if there are specific things that you believe are missing from our
> > version of configfsf.guess, I'm sure we can add them.
>
> > Bill.
>
> > 2009/4/16 Mariah Lenox <mariah.le...@gmail.com>:
> > > I applaud the fact that config.guess
> > > gives a better representation of the CPU
> > > type.
>
> > > A suggestion - upgrade configfsf.guess
>
> > > configfsf.guess in mpir-1.1 is version 2004-10-07'
>
> > > The latest config.guess is 2009-02-03.
> > > (Seeftp://ftp.gnu.org/pub/gnu/config)
>
> > > Mariah
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to mpir-devel@googlegroups.com
To unsubscribe from this group, send email to 
mpir-devel+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to