This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: canadian cross trouble with libiberty location
- From: DJ Delorie <dj at redhat dot com>
- To: dank at kegel dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 14 May 2004 22:16:36 -0400
- Subject: Re: canadian cross trouble with libiberty location
- References: <40A56347.5040308@kegel.com>
> --build=i686-pc-linux-gnu \
> --host=x86_64-unknown-linux-gnu \
> --target=i686-unknown-linux-gnu \
This isn't a true canadian, since build==target. I refer to these as
"crossback" builds and they are even more rare than canadians. The
documentation section "Configure Terms and History" talks about the
different types of builds.
> So perhaps gcc's build system made the libiberty in question one level
> up because the build system name looked local (duh)?
Most likely, there's somewhere testing "$build != $target" where it
should test "$build != $host" (or something similar, like
$build_alias), or getting the build vs target subdirectories confused.
But one drawback to even getting this right is that the build
libiberty and the target libiberty reside in the same directory yet
are built with different compilers, which may cause problems. More
recent sources use build-<foo> to avoid this conflict.
One workaround is to use --build=i586-pc-linux-gnu instead of i686,
just so that build and target are different.