[Slackbuilds-users] libgda compile is "brittle" fix

John Vogel jvogel4 at stny.rr.com
Sat Aug 1 22:25:21 UTC 2015

On Sat, 1 Aug 2015 15:03:01 -0700
King Beowulf <kingbeowulf at gmail.com> wrote:

> On Saturday, August 1, 2015, John Vogel <jvogel4 at stny.rr.com> wrote:
> >
> >
> > I wonder if this is a pkg-config issue. So maybe builds could add
> > something like:
> >
> >
> Uncertain. compiling on pure Slack64 VM worked fine.
> -ed

Yep, makes sense. If you are building from pure 64bit or pure
32bit system, then pkg-config already knows where to look
(in most cases and if you aren't like me and have stuff in
/opt and various non-standard places).
On a multilib/multiarch system, there are different pkg-config
directories for each arch's .pc files:

/usr/lib64/pkgconfig and /usr/lib/pkgconfig.

Manipulating pkg-config can save a lot of grief when library and
header paths can be different based on compile time arch.
I often have to mess with pkg-config when I'm cross compiling,
so I thought I'd chime in. I'm probably just muddying the
waters, and if so, my apologies in advance.


More information about the SlackBuilds-users mailing list