Re: [3.0 critical] Make fixproto deal with assert.h (bootstrap fails)

["Zack Weinberg" <zackw at Stanford dot EDU>]

On Sat, May 12, 2001 at 03:40:02PM -0700, Mark Mitchell wrote:
> >>>>> "Zack" == Zack Weinberg <zackw@Stanford.EDU> writes:
> 
>     Zack> As a last resort, we could put __eprintf back in libgcc.a.
> 
> I guess we'd better.  I don't see a tidy way around this problem, and
> this solution seems easiest.
> 
> Did we ever actually install stuff in ${prefix}/include directly,
> rather than in some subdirectory?  That was a mistake, in hindsight --
> we have no way of avoiding it when compiling new versions of GCC.

I don't think we ever installed stuff directly in $(prefix)/include,
but assert.h has been installed in $(tooldir)/include,
i.e. $(prefix)/TARGET/include, at least as far back as 2.7.2.  I never
knew why, and when I did GCC installs back in the day, I used to move
it to gcc-lib/TARGET/VERSION/include by hand - this never caused
problems.

I tend to agree with Russ that we can't be expected to support this
sort of thing, and that "move it to gcc-lib" may be an adequate
answer.

-- 
zw    To shield children right up to the age of 18 from exposure to violent
      descriptions and images would not only be quixotic, but deforming;
      it would leave them unequipped to cope with the world as we know it.
      	-- American Amusement Machine Association vs. Indianapolis