public inbox for
help / color / mirror / Atom feed
From: "Rolf Berg" <>
Subject: Re: insight/184: build fails at WINDRES step
Date: Mon, 06 Jan 2003 15:33:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR insight/184; it has been noted by GNATS.

From: "Rolf Berg" <>
To: <>,
Subject: Re: insight/184: build fails at WINDRES step
Date: Mon, 6 Jan 2003 16:34:00 +0100

 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
 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.
 Rolf Berg

             reply	other threads:[~2003-01-06 15:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06 15:33 Rolf Berg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19 20:18 kseitz
2002-11-05 14:43 BrianMcGinley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).