From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20341 invoked by alias); 6 Jan 2003 15:33:06 -0000 Mailing-List: contact insight-prs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-prs-owner@sources.redhat.com Received: (qmail 20327 invoked by uid 71); 6 Jan 2003 15:33:04 -0000 Date: Mon, 06 Jan 2003 15:33:00 -0000 Message-ID: <20030106153304.20326.qmail@sources.redhat.com> To: kseitz@sources.redhat.com Cc: insight-prs@sources.redhat.com, From: "Rolf Berg" Subject: Re: insight/184: build fails at WINDRES step Reply-To: "Rolf Berg" X-SW-Source: 2003-q1/txt/msg00000.txt.bz2 List-Id: The following reply was made to PR insight/184; it has been noted by GNATS. From: "Rolf Berg" To: , , , Cc: Subject: Re: insight/184: build fails at WINDRES step Date: Mon, 6 Jan 2003 16:34:00 +0100 Hi, I experienced the same problem as Brian McGinley described. Could the problem have anything to do with handling of newline? The error code made me suspect it is an alignnment problem in the file. I noticed that the cursor5e.cur contained the DOS sequence for linefeed, 0xd 0xa. By replacing this with the Unix sequence, 0x0a, the file compiled. I did the similar patch to the other .cur files that failed. After some struggling with other, unrelated problems, I was able to get the gdb up and running. (I have not been able to test it against any target yet, due to lack of HW) Note that this is just a suggestion, I don't have much knowledge of .cur file and WINDRES, so the suggested changes may have disastreous side effects. regards, Rolf Berg