From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3617 invoked by alias); 20 Nov 2005 17:56:02 -0000 Received: (qmail 3592 invoked by uid 48); 20 Nov 2005 17:56:00 -0000 Date: Sun, 20 Nov 2005 17:56:00 -0000 Message-ID: <20051120175600.3591.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug testsuite/23400] [4.1 Regression] "make check" fixinclude failure In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "bauhaus at futureapps dot de" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2005-11/txt/msg02830.txt.bz2 List-Id: ------- Comment #7 from bauhaus at futureapps dot de 2005-11-20 17:56 ------- > PR 23400 > * inclhack.def: Add newline to the replace text for string.h. > * fixincl.x: Regenerate. Similarly, removing \n from last line of the string.h in the fixincludes source directory works for me (seemingly, make check is running). (-rw-r--r-- 1 georg staff 328 2005-11-20 16:42 ../src/gcc/fixincludes/tests/base/string.h) Why is there an Ultrix fix in string.h in the first place? Does it just happen to be there because that is how fixinclude had finished writing headers at some point? -- bauhaus at futureapps dot de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bauhaus at futureapps dot de http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23400