This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc_tooldir


"H. J. Lu" <hjl@lucon.org> writes:

> On Fri, Sep 12, 2003 at 09:52:10PM +0200, Marcus Comstedt wrote:
> > 
> > Hello.
> > 
> > gcc/Makefile defines gcc_tooldir as
> > 
> >   gcc_tooldir = $(libsubdir)/$(unlibsubdir)/../$(target_alias)
> > 
> > where $(unlibsubdir) is ../../..
> > 
> > Is there any reason for this convolution as opposed to just setting
> > 
> 
> So you can relocate gcc to a different directory.

Um.  Please explain this.  Not only do the paths get compiled into
gcc, but they also go through an unrelated directory so that they will
be wrong even if you move _that_ directory.  Just how does this
arrangement make gcc more relocatable?


> > ?  The construction with all the ..'s is rather inconvenient since it
> > depends on the existence of $(libsubdir), and on the absence of
> > symlinks along the way.
> 
> That is a known problem.

So what is the proposed solution?


  // Marcus



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]