From: Mark H Weaver <mhw@netris.org>
To: "d.henman" <dhenman@gmail.com>
Cc: 14093@debbugs.gnu.org
Subject: bug#14093: configure for build problem
Date: Sat, 30 Mar 2013 19:41:15 -0400 [thread overview]
Message-ID: <877gko78x0.fsf@tines.lan> (raw)
In-Reply-To: <20130319000429.2304@binki> (d. henman's message of "Tue, 19 Mar 2013 00:04:29 +1000")
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
prev parent reply other threads:[~2013-03-30 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 14:04 bug#14093: configure for build problem d.henman
2013-03-30 23:28 ` Ludovic Courtès
[not found] ` <20130331164949.2152@binki>
2013-03-31 15:36 ` Mark H Weaver
2013-03-30 23:41 ` Mark H Weaver [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877gko78x0.fsf@tines.lan \
--to=mhw@netris.org \
--cc=14093@debbugs.gnu.org \
--cc=dhenman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).