See below.
Etienne Gagnon wrote:
I have a problem actually building the sources. e.g.:
$ apt-get source libffi2
$ cd gcc-3.3-3.3.2ds4/
$ tar -xjvf gcc-3.3.2.tar.bz2
$ cd gcc-3.3.2/libffi/
$ ./configure
which results in:
creating cache ./config.cache
checking for Cygwin environment... no
checking f
Hmmm,
I have a problem actually building the sources. e.g.:
$ apt-get source libffi2
$ cd gcc-3.3-3.3.2ds4/
$ tar -xjvf gcc-3.3.2.tar.bz2
$ cd gcc-3.3.2/libffi/
$ ./configure
I can trust gcc people might have been careful about license, but it seems
pretty difficult to me to build libffi without b
Etienne Gagnon writes:
> Matthias Klose wrote:
> > why do you think it's derivative work? It's IMO clear, that libffi
> > comes with it's own license (fastjar as well). sure you can build
> > libffi without building gcc:
> >
> >cd libffi; ./configure; make
> >
> > I don't see any RC bug h
Matthias Klose wrote:
why do you think it's derivative work? It's IMO clear, that libffi
comes with it's own license (fastjar as well). sure you can build
libffi without building gcc:
cd libffi; ./configure; make
I don't see any RC bug here.
It's not as simple, unfortunately.
The following d
Etienne Gagnon writes:
> Package: libffi2
> Version: 1:3.3.2-3
> Severity: serious
> Justification: Policy 2.3 Copyright considerations
>
> Hi!
>
> Libffi2 is supposed to be licensend under a very permissive license of
> the type "do whatever you want with the code"[0]. Yet, the build
> procedur
Package: libffi2
Version: 1:3.3.2-3
Severity: serious
Justification: Policy 2.3 Copyright considerations
Hi!
Libffi2 is supposed to be licensend under a very permissive license of
the type "do whatever you want with the code"[0]. Yet, the build
procedure of the Debian libffi2 source package make
6 matches
Mail list logo
