All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: cross-compiling flags?
Date: Thu, 06 Nov 2008 04:39:46 +0000	[thread overview]
Message-ID: <200811052239.46729.hollisb@us.ibm.com> (raw)
In-Reply-To: <1225814193.15410.17.camel@localhost.localdomain>

On Wednesday 05 November 2008 20:51:18 Liu Yu wrote:
> 
> > -----Original Message-----
> > From: Hollis Blanchard [mailto:hollisb@us.ibm.com] 
> > Sent: Tuesday, November 04, 2008 11:57 PM
> > To: Liu Yu-B13201
> > Cc: kvm-ppc
> > Subject: cross-compiling flags?
> > 
> > Hi Yu, Christian tells me you have some weird cross-build setup that
> > brings you to want to use gcc's -idirafter flag for zlib headers. I
> > don't like using something that obscure. Can you elaborate on 
> > the errors
> > you get when using -I ?
> > 
> 
> I don't know what libc headers are used in your case. The host libc
> header files?

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/powerpc-440-linux-gnu

> 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?

I have heard of LTIB, but I don't know how its toolchain is installed.

-- 
Hollis Blanchard
IBM Linux Technology Center

  parent reply	other threads:[~2008-11-06  4: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 [this message]
2008-11-06  7:44 ` Liu Yu
2008-11-06 15:39 ` Hollis Blanchard

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=200811052239.46729.hollisb@us.ibm.com \
    --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.