discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNUstep on 10.7


From: Stefan Bidi
Subject: Re: GNUstep on 10.7
Date: Sat, 27 Aug 2011 15:08:31 -0500

I had similar issues with Slackware a few years ago.  The libffi version packaged with GCC was installed in a weird location (can remember the whole path, but it was a gcc specific location not picked up by -base's configure script).  Anyway, you can just specify the path for --with-ffi-include and --with-ffi-library.  At the time, I remember aving to specify both of those to make it work.

On Sat, Aug 27, 2011 at 2:57 PM, artware <address@hidden> wrote:
Guys,

Thanks to your help, I'm much closer now. I think the configure in
gnustep-base is finding FFI, but it's just not liking what it's
finding:

"checking FFI library usage... configure: error: The ffi library
(libffi) does not appear to be working."

I've recompiled and reinstalled libffi 3.0.10 a few times now, but it
doesn't seem to help. pkg-config is hosed on my system, and trying to
recompile it fails, because it requires... pkg-config.

Any thoughts?

Ben

On Sat, Aug 27, 2011 at 12:09 PM, Truls Becken <address@hidden> wrote:
> On 27 Aug 2011 at 10:08, Ondřej Hošek wrote:
>
>> libffi installed its headers into /usr/lib/libffi-$FFIVERSION/include
>> instead of /usr/include. Naturally, no software can find it now
>> (without additional ./configure flags).
>
> On the other hand, it could get messy if all headers were thrown into
> /usr/include. That's why pkg-config exists. My system (Archlinux) has
> libffi headers in the same place as yours (probably where the makefile
> puts it by default), and this works fine for me by using the
> following:
>
> ./configure --with-ffi-include=`pkg-config --variable=includedir libffi`
>
> -Truls
>

_______________________________________________
Discuss-gnustep mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnustep


reply via email to

[Prev in Thread] Current Thread [Next in Thread]