Bug#219595: More information on building 'standalone' libffi

[Matthias Klose <doko@cs.tu-berlin.de>]

Etienne Gagnon writes:
> The inclusion of libffi & gcc in a single .tar.gz that shares scripts,
> configure, and Makefiles, does *not* constitutes a "mere aggregation".

you are wrong. libffi does have it's own configure and Makefile. For
the scripts you have to show that they are licensed under something
stricter than libffi is licensed. both the install-sh and the
config-ml.in do have an appropriate license.

> I am sure that there are no deep dependencies between gcc and libffi.  My
> major problem, right now, is that I seems unable to acually *build* libffi
> using "cd gcc-3.3.2/libffi; ./configure; make" as you suggested.
> 
> Could you tell me what I am doing wrong, below?  Thanks in advance.
> 
> $ 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
> creating cache ./config.cache
> checking for Cygwin environment... no
> checking for mingw32 environment... no
> configure: error: can not find install-sh or install.sh in ../.. ./../..

it seems you need this patch to build libffi from the source dir:

--- libffi/configure.in~	2003-10-22 01:02:59.000000000 +0200
+++ libffi/configure.in		2003-11-11 12:33:40.000000000 +0100
@@ -29,6 +29,7 @@
 else
   libffi_basedir=
 fi
+libffi_basedir=
 AC_SUBST(libffi_basedir)
 AC_CONFIG_AUX_DIR(${libffi_basedir}..)
 

I'm going to close this report.

	Matthias