Andrew Benton <[email protected]> wrote:

> It's up to you. Your system, your rules. On my systems I try to put all
> the headers into /usr/include. With libffi I use these commands:
> sed -i 's#${libdir}/#/usr/include/#;s#/include$##' libffi.pc.in
> sed -i 's#sdir = $(libdir)#sdir = /usr/include#;s#/include$##' \
> include/Makefile.in
>

You have no idea how wonderful it is to read that response.  I have been
trying several Linux distributions attempting to find the right one(s) to
replace my Windows systems.  It seems like every system I've tried, it's
expected that you do things that distribution's way.  Right now, I have
Debian netinst (minimal Debian distribution) installed on one system and
was hoping to build a lot of the applications I needed from scratch
(similar to BLFS) since many aren't in the Debian archive or aren't built
the way I need them.  However, the more I read about LFS, the more I keep
thinking about trying to build the entire system from scratch.  It really
does seem to be the best way to get a system customized the way you want it
to be.

Thanks for the patches to libffi.pc.  I believe I did something similar.

I was attempting to get gtk3 to build with libffi, but hit some issues with
the configure script and a few other problems.  I'm able to get glib to
build, but it needed some patching with my system to make it do so.  When I
tried to file a bug report (as mentioned on
http://developer.gnome.org/glib/2.30/glib-resources.html) they were
anything but friendly about it.  I already prefer a lot of console, sdl,
fltk, wxWidgets applications to some of the gtk+ ones.  I'm seriously
considering replacing the gtk+ applications I use with applications created
using other GUI frameworks.  It's so much nicer for a developer when a
project is positive about listening to suggestions or looking at suggested
patches.

Sincerely,
Laura
http://www.distasis.com/cpp
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to