> -----Original Message----- > From: Hollis Blanchard [mailto:hollisb@xxxxxxxxxx] > Sent: Thursday, November 06, 2008 12:40 PM > To: Liu Yu-B13201 > Cc: kvm-ppc > Subject: Re: cross-compiling flags? > > On Wednesday 05 November 2008 20:51:18 Liu Yu wrote: > > > > > -----Original Message----- > > > From: Hollis Blanchard [mailto:hollisb@xxxxxxxxxx] > > > 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/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. -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
