This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: header search path change with 2003-03-02 commit
On Tue, Mar 25, 2003 at 11:57:12AM -0500, Hans-Peter Nilsson wrote:
> I hope I got attribution right.
>
> On Tue, 25 Mar 2003, Daniel Jacobowitz wrote:
> > Answering slightly out of order.
> > > On Tue, Mar 25, 2003 at 06:44:20AM +0000, Neil Booth wrote:
> > > > How many of the paths in cpp_include_defaults can begin with
> > > > cpp_GCC_INCLUDE_DIR? Can it be more than one?
> > >
>
> > On Tue, Mar 25, 2003 at 07:30:56PM +1030, Alan Modra wrote:
> > > I've seen two. $prefix/$target/sys-include and
> > > $prefix/$target/include.
> >
> > Hooold on a second. $prefix/$target has nothing to do with
> > cpp_GCC_INCLUDE_DIR.
>
> (From the cross-perspective, no sysroot:)
>
> Err, it seems it has. cpp_GCC_INCLUDE_DIR is the installation
> point, the starting point for a ../../../.../stuff sequence
> suffixed to cpp_GCC_INCLUDE_DIR or the moved equivalence,
> yielding $prefix/$target/include and sys-include.
>
> > It's normally "$(libsubdir)/include" minus the
> > last eight characters ("/include"). There shouldn't be more than the
> > one include directory there normally.
>
> Sure, but I think you forgot the ../ stuff.
Crap, you're right of course. I really vehemently dislike the way we
use libsubdir to find the relocated prefix. We have better mechanisms
now but every time I try to change a quirk in this code, someone pops
up who relied on that quirk. It's worse than C extensions :)
However, I stand by my point that it probably doesn't matter if you use
iprefix translation on the sysroot directories or not.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer