From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: RE: cross-compiling flags?
Date: Thu, 06 Nov 2008 15:39:01 +0000 [thread overview]
Message-ID: <1225985941.8620.22.camel@localhost.localdomain> (raw)
In-Reply-To: <1225814193.15410.17.camel@localhost.localdomain>
On Thu, 2008-11-06 at 15:44 +0800, Liu Yu wrote:
> >
> > When I cross-compile qemu, it's using the cross-toolchain
> > glibc headers. Since
> > my toolchain is from crosstool, those headers are
> > at
> > /opt/crosstool/gcc-3.4.5-glibc-2.3.6/powerpc-440-linux-gnu/pow
> > erpc-440-linux-gnu
>
> Yes, me too.
>
> >
> > > In my case, the libc headers are already appointed to a
> > > toolchain-combined version in LTIB(assume you know it).
> > > But zlib.h is not existing so I had to use qemu-cflag to
> > appoint another
> > > dir
> >
> > If your zlib headers are mixed in with the target libc
> > headers, then why do
> > you need any -I at all?
>
> The zlib headers are mixed in powerpc local libc headers not the toolchain cross libc headers.
> And it seems the local libc headers is unfit for cross building.
Since I'm not familiar with LTIB, I chatted with Kumar Gala about this
briefly, and he suggested that you post your issue to the internal
Freescale LTIB list.
My understanding is that you have a special directory for target
headers, which is used by the cross toolchain. Without understanding the
details, my suggestion would be to build a second copy of zlib from
source, and configure it with --prefix=/target/specific/directory.
--
Hollis Blanchard
IBM Linux Technology Center
prev parent reply other threads:[~2008-11-06 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 15:56 cross-compiling flags? Hollis Blanchard
2008-11-06 2:51 ` Liu Yu
2008-11-06 4:39 ` Hollis Blanchard
2008-11-06 7:44 ` Liu Yu
2008-11-06 15:39 ` Hollis Blanchard [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1225985941.8620.22.camel@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.