This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: gcc-3.3 fixincludes patch. (Was: [Autogen-bugs] autogen-5.5.5)
- From: Peter Breitenlohner <peb at mppmu dot mpg dot de>
- To: Bruce Korb <bkorb at veritas dot com>
- Cc: GCC-patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 12 Jun 2003 18:07:11 +0200 (CEST)
- Subject: Re: gcc-3.3 fixincludes patch. (Was: [Autogen-bugs] autogen-5.5.5)
- References: <Pine.LNX.4.55.0306121507290.5993@pcl321.mppmu.mpg.de> <3EE883E7.D3878DDE@veritas.com> <Pine.LNX.4.55.0306121617330.5993@pcl321.mppmu.mpg.de><3EE89F9B.CC567931@veritas.com>
On Thu, 12 Jun 2003, Bruce Korb wrote:
> You didn't explain the third diff: DUMMY_VA_LIST
> I guess you have a situation where you wound up with a double dummy list?
Indeed: in stdio.h from glibc-2.2.5. In order not to have it fixed by every
new gcc version, I had modified the original file as per gcc's fix, but then
that was fixed again from
# ifndef _DUMMY_VA_LIST_DEFINED
typedef _G_va_list __not_va_list__;
# define _DUMMY_VA_LIST_DEFINED
to
# ifndef _DUMMY_DUMMY_VA_LIST_DEFINED
typedef _G_va_list __not_va_list__;
# define _DUMMY_DUMMY_VA_LIST_DEFINED
I hope all that is automatically taken care of in glibc-2.3.2.
The whole fixinclude business is really a mess. Whenever one installs some
new headers for some libraries (which I do fairly often), one really ought
to rerun fixincludes, but I doubt many people actually do that.
regards
Peter Breitenlohner <peb@mppmu.mpg.de>