bug#14093: configure for build problem

bug#14093: configure for build problem

[d.henman]

I'm not sure if this is a confgure script problem or not.  Please take a look at the related configure error message.

$ configure
....

checking for LIBFFI... configure: error: Package requirements (libffi) were not met:

No package 'libffi' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables LIBFFI_CFLAGS
and LIBFFI_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

#
# However when I do:

$ ls /bin/*ffi*
/bin/cygffi-4.dll 

This location is standard in my opion.
it shows that the ffi library is installed.  This is a cygwin platform and library names by convention us 'cyg' as a filename prefix.  

I'd appreciate any informatio that would help get this built.
Thank you.

bug#14093: configure for build problem

[Ludovic Courtès]

Hi,

"d.henman" <dhenman@gmail.com> skribis:

> checking for LIBFFI... configure: error: Package requirements (libffi) were not met:
>
> No package 'libffi' found

[...]

> # However when I do:
>
> $ ls /bin/*ffi*
> /bin/cygffi-4.dll 
>
> This location is standard in my opion.

The configure script checks for libffi via the pkg-config tool.

What does ‘pkg-config libffi --cflags --libs’ return on your machine?

If it shows an error, this means that either the PKG_CONFIG_PATH
environment variable does not contain the directory where libffi.pc is,
or that the file libffi.pc is missing from your libffi installation.

HTH,
Ludo’.

bug#14093: configure for build problem

[Mark H Weaver]

Hi,

Please keep <14093@debbugs.gnu.org> in the CC line, so that your
messages related to this bug will be included in the relevant entry in
our bug tracking system.

     Thanks,
       Mark


"d.henman" <dhenman@gmail.com> writes:

> Ludovic and Mark,
>   thanks for answering my query.
>
>> The configure script checks for libffi via the pkg-config tool.
>> 
>> What does ‘pkg-config libffi --cflags --libs’ return on your machine?
>
>  $ pkg-config libffi --cflags --libs
> Package libffi was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libffi.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'libffi' found
>
> I'm looking for information at cygwin and also 
> about gettnig the ffi.h file as Mark suggested.
>
>
> Regards

"d.henman" <dhenman@gmail.com> writes:

> Mark H Weaver <mhw@netris.org> wrote:
>> > $ configure
>> > ....
>> > checking for LIBFFI... configure: error: Package requirements (libffi) were not met:
>> >
>> > No package 'libffi' found
>> 
>> A few questions:
>> * Do you have "ffi.h" on your system?  If so, where?
>
> I found  ffi.h in /usr/lib/gcc/i686-pc-cygwin/4.5.3/include/ffi.h
>
>> * Do you have "libffi.pc" on your system?  If so, where?
> .. but there is no libffi.pc
>
>> * Do you have the 'pkg-config' command installed?
> yes
>  
>> I'm not very familiar with cygwin, so maybe someone else could help you
>> more efficiently, but if you have the 'pkg-config' command and can find
>> "libffi.pc", then it might be sufficient to do (before running
>> ./configure):
>> 
>>   export PKG_CONFIG_PATH=/DIRECTORY_THAT_CONTAINS_LIBFFI_DOT_PC
>> 
>> Otherwise, as a fall-back plan: if you can find "ffi.h", then it might
>> be sufficient to do (before running ./configure):
>> 
>>   export LIBFFI_CFLAGS=-I/DIRECTORY_THAT_CONTAINS_FFI_DOT_H
>>   export LIBFFI_LIBS=-lffi
>
> I'll try this on the morrow.
>  
>> Please let us know how this works out.
>> 
>>     Regards,
>>       Mark

bug#14093: configure for build problem

[Mark H Weaver]

Hi,

"d.henman" <dhenman@gmail.com> writes:

> I'm not sure if this is a confgure script problem or not.  Please take a look at the related configure error message.
>
> $ configure
> ....
>
> checking for LIBFFI... configure: error: Package requirements (libffi) were not met:
>
> No package 'libffi' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables LIBFFI_CFLAGS
> and LIBFFI_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> #
> # However when I do:
>
> $ ls /bin/*ffi*
> /bin/cygffi-4.dll 
>
> This location is standard in my opion.
> it shows that the ffi library is installed.  This is a cygwin platform
> and library names by convention us 'cyg' as a filename prefix.  

A few questions:

* Do you have "ffi.h" on your system?  If so, where?
* Do you have "libffi.pc" on your system?  If so, where?
* Do you have the 'pkg-config' command installed?

I'm not very familiar with cygwin, so maybe someone else could help you
more efficiently, but if you have the 'pkg-config' command and can find
"libffi.pc", then it might be sufficient to do (before running
./configure):

  export PKG_CONFIG_PATH=/DIRECTORY_THAT_CONTAINS_LIBFFI_DOT_PC

Otherwise, as a fall-back plan: if you can find "ffi.h", then it might
be sufficient to do (before running ./configure):

  export LIBFFI_CFLAGS=-I/DIRECTORY_THAT_CONTAINS_FFI_DOT_H
  export LIBFFI_LIBS=-lffi

If you can't find "ffi.h", then you need to get it somehow.  I don't
know how it works in the cygwin world, but in most GNU/Linux
distributions, library packages are split into at least two parts: the
portion needed to run pre-built packages, and the "development" package
that includes things like *.h files.

If you don't have 'pkg-config', then you'll probably need to do
something similar with BDW_GC_CFLAGS and BDW_GC_LIBS.

Please let us know how this works out.

    Regards,
      Mark