On 07/26/2011 04:51 PM, Yoder Stuart-B08248 wrote:
I am having issues with this in a cross compilation
environment. In Power embedded, almost all our
development is using cross toolchains.
Neither glib or pkg-config are in our cross build environment
and I'm having issues getting them built and installed.
Not even sure if pkg-config is even supposed to work
in a cross development environment...I'm new to that
tool and poking around a bit with google raises
some questions.
You're probably setting up your cross environment incorrectly which,
unfortunately, is very common.
The proper thing to do is to have GCC use a different system include
directory and a different prefix. That will result in a directory where
there are gcc binaries with normal names installed in ${cross_prefix}/bin
You need to build and install pkg-config to this prefix too, and then
when it comes time to actually doing the QEMU configure, you should do
something like:
export PATH=${cross_prefix}/bin:$PATH
export PKG_CONFIG_PATH=${cross_prefix}/lib/pkg-config:$PKG_CONFIG_PATH
Many automated cross compiler environment scripts will install specially
named versions of gcc and binutils in your normal $PATH. The trouble
is, this is a bit of a hack and unless you know to make this hack work
with other build tools, it all comes tumbling down.
Regards,
Anthony Liguori
Wanted to make you aware of the issue...
Stuart
