This is the mail archive of the gcc-patches@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]

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

To: zackw at Stanford dot EDU
Subject: Re: [3.0 critical] Make fixproto deal with assert.h(bootstrap fails)
From: Mark Mitchell <mark at codesourcery dot com>
Date: Sat, 12 May 2001 15:40:02 -0700
Cc: ghazi at caip dot rutgers dot edu, gcc-bugs at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, jsm28 at cam dot ac dot uk
Organization: CodeSourcery, LLC
References: <200105121259.IAA22988@caip.rutgers.edu><20010512113828P.mitchell@codesourcery.com><20010512120028.T9305@stanford.edu>

>>>>> "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.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

Follow-Ups:
- Re: [3.0 critical] Make fixproto deal with assert.h (bootstrap fails)
  - From: Russ Allbery
- Re: [3.0 critical] Make fixproto deal with assert.h (bootstrap fails)
  - From: Zack Weinberg

References:
- Re: [3.0 critical] Make fixproto deal with assert.h (bootstrap fails)
  - From: Kaveh R. Ghazi
- Re: [3.0 critical] Make fixproto deal with assert.h(bootstrap fails)
  - From: Mark Mitchell
- Re: [3.0 critical] Make fixproto deal with assert.h (bootstrap fails)
  - From: Zack Weinberg

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