From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hollis Blanchard Date: Thu, 06 Nov 2008 04:39:46 +0000 Subject: Re: cross-compiling flags? Message-Id: <200811052239.46729.hollisb@us.ibm.com> List-Id: References: <1225814193.15410.17.camel@localhost.localdomain> In-Reply-To: <1225814193.15410.17.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-ppc@vger.kernel.org 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