This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Should fixinc be linked with libiberty.a?
- To: law at cygnus dot com
- Subject: Re: Should fixinc be linked with libiberty.a?
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Date: Tue, 7 Sep 1999 09:39:51 -0400 (EDT)
- Cc: egcs at egcs dot cygnus dot com, fixincludes at autogen dot freeservers dot com
> From: Jeffrey A Law <law@cygnus.com>
>
> In message <199909062036.QAA12908@caip.rutgers.edu>you write:
> >
> > I noticed that fixincl is linked with libiberty.a. I'm
> > wondering whether it should be given host vs build platform concerns.
>
> fixincl is a build tool and should generally be handled like the gen*
> programs.
Okay, that's what I thought.
> Actually, one could claim it does not belong inside gcc itself and
> that by having it inside the gcc dir we complicate things.
>
> ie, it may be better off outside the gcc subdir much like bison, flex,
> texinfo other build tools work. Nobody ever explained to me the value
> of keeping it inside the gcc subdir (much to my aggravation).
>
> jeff
I don't see how that would solve the canadian cross case. We
still don't compile a "build" version of libiberty.a (yet.)
--Kaveh
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Qwest Internet Solutions