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]
Other format:	[Raw text]

Re: Parts 3 and 4 to the vxworks/fixincludes patches

From: rbmj <rbmj at verizon dot net>
To: Bruce Korb <bruce dot korb at gmail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Thu, 01 Nov 2012 09:35:37 -0400
Subject: Re: Parts 3 and 4 to the vxworks/fixincludes patches
References: <508EB477.4080202@gmail.com> <508EE673.4010807@verizon.net> <508F366A.9060001@verizon.net>

On 10/29/2012 10:07 PM, rbmj wrote:

I get a clean build on my end... no stdarg.h issues.  Build
characteristics are given in the previous email.

On 10/29/2012 4:26 PM, rbmj wrote:

The build does eventually die in libstdc++-v3, but that's not due to
these changes (it gives me an internal compiler error while compiling
complex_io.cc inside of <complex>, see bug 55126)


This is fixed by the patch in the comments of bug 54957. With this
applied (along with a very minor gthread fix at 54805) I get a good build.

This fix is applied in 193052, and now my patches will build on top of trunk. Bruce, can you give steps on how to reproduce the error you reported?

Follow-Ups:
- Re: Parts 3 and 4 to the vxworks/fixincludes patches
  - From: Bruce Korb

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