Your message dated Thu, 13 Nov 2003 08:04:57 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#219595: More information on building 'standalone' libffi
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 7 Nov 2003 15:08:03 +0000
>From [EMAIL PROTECTED] Fri Nov 07 09:07:51 2003
Return-path: <[EMAIL PROTECTED]>
Received: from (gandalf) [132.208.137.233]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AI8DE-0002kS-00; Fri, 07 Nov 2003 09:07:48 -0600
Received: from egagnon by gandalf with local (Exim 3.36 #1 (Debian))
id 1AI8DG-0000IW-00; Fri, 07 Nov 2003 10:07:50 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Etienne Gagnon <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: libffi2: Licensing problems
X-Mailer: reportbug 2.36
Date: Fri, 07 Nov 2003 10:07:50 -0500
Message-Id: <[EMAIL PROTECTED]>
Sender: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-4.0 required=4.0
tests=BAYES_70,HAS_PACKAGE
version=2.53-bugs.debian.org_2003_11_7
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_11_7
(1.174.2.15-2003-03-30-exp)
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 it impossible to
build libffi2 *without* the GCC source code, which is licensed under
the GNU GPL. So, because of this direct dependency, the libffi2
binary becomes a derivative work of GCC, and must then be licensed
under the GPL, which can have unfortunate consequences on any
non-GPL software that depends on libffi2 [SableVM comes to mind:-)].
There are of course 2 solutions:
1- Put the appropriate license on the libffi2 binary package
(e.g. GPL), and cause problems to dependent packages (not
recommended).
2- Remove the build dependency on gcc's GPL source code, and for
safety (and simplicity), split libffi2's source package from the gcc
source package (highly recommended).
I would be willing to help, if help is needed, to help the gcc/libffi2
maintainers do the split.
Etienne
[0] More precisely, /usr/share/doc/libffi2/copyright says:
--- BEGIN ---
libffi - Copyright (c) 1996-1999 Cygnus Solutions
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
``Software''), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL CYGNUS SOLUTIONS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
--- END ---
-- System Information:
Debian Release: testing/unstable
Architecture: powerpc
Kernel: Linux gandalf 2.4.20-ben1 #1 Sun Feb 2 20:00:49 EST 2003 ppc
Locale: LANG=C, LC_CTYPE=C
Versions of packages libffi2 depends on:
ii gcc-3.3-base 1:3.3.2-3 The GNU Compiler Collection (base
ii libc6 2.3.2.ds1-9 GNU C Library: Shared libraries an
-- no debconf information
---------------------------------------
Received: (at 219595-done) by bugs.debian.org; 13 Nov 2003 07:05:17 +0000
>From [EMAIL PROTECTED] Thu Nov 13 01:05:16 2003
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AKBXX-0007IY-00; Thu, 13 Nov 2003 01:05:15 -0600
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id IAA04049;
Thu, 13 Nov 2003 08:04:57 +0100 (MET)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id hAD74vfL008614;
Thu, 13 Nov 2003 08:04:57 +0100 (MET)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 13 Nov 2003 08:04:57 +0100
To: Etienne Gagnon <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#219595: More information on building 'standalone' libffi
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-5.7 required=4.0
tests=EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT
version=2.53-bugs.debian.org_2003_11_9
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_11_9
(1.174.2.15-2003-03-30-exp)
closing ...
Etienne Gagnon writes:
> Nathanael Nerode wrote:
> > Libffi and install-sh & friends are "identifiable sections", "not
> > derived from the Program" ('the Program' meaning any work available only
> > under the GPL), "can be reasonably considered independent and separate
> > works in themselves", and so they can be distributed as separate works.
>
> OK.
>
> > Try this.
> > mkdir build
> > cd build
> > ../gcc-3.3.2/libffi/configure
> > make
>
> OK. This works. :-) It would be a good idea to put a little note about it
> in the libffi directory. It is not obvious to a newby to know that this
> unusual build mechanism does not only apply to gcc itself (documented in
> gcc-3.2.2/INSTALL/).
>
> You may close this bug.
>
> Thanks a lot for answering my questions and concerns.
>
> Etienne
>
> PS: I might still file a different bug about the source package; it is not
> very
> convenient to have to download all of GCC's sources (megabytes and megabytes
> of data) just for looking at libbffi's sources (few kilobytes).
tags +wontfix
severity minor-wishlist
close after-some-time
I don't care. libgcj does use the included version anyway and doesn't
link to libffi directly.
Matthias
