Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sources.redhat.com
Subject: gdb and older cygwins
Date: Thu, 26 Aug 2004 11:10:00 -0000	[thread overview]
Message-ID: <5.2.0.9.1.20040826130046.01d35970@NT_SERVER> (raw)

Hi

We need to stay with a 2.95.3 cross compiled gcc. This versions has some
errors regarding line endings, especially macro continuers (#define \) are
not recognized if the source file has Windows CRLF endings. I tried to
compile it anew with a recent cygwin version (1.5.10) but I can't get over
with this error. For some reason it seems to work when compiled with
a much older cygwin version. As I also need a cross compiled gdb they
both need to rely on the same cygwin.dll. When trying to run a gdb
compiled with a new cygwin together with an old cygwin.dll I got
missing entry point errors. So I need to compile it with the older
cygwin environment.

Now to the real question: What are the requirements to the cygwin
environment to build an actual gdb? Is there a minimum version
required or will configure take care of it?

Thanks

bye  Fabi

PS: The other solution would be to fix the 2.95.3 source about this
CRLF bug. I looked into the gcc list but couldn't find simple patches,
I guess it needs a bigger change. If anyone has some hints about it...



             reply	other threads:[~2004-08-26 11:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 11:10 Fabian Cenedese [this message]
2004-08-26 12:53 ` Michael Chastain
2004-08-26 13:23   ` Fabian Cenedese
2004-08-26 14:23   ` Dave Korn
2004-08-26 14:56     ` Fabian Cenedese
2004-08-26 16:10       ` Dave Korn
2004-08-27  7:28         ` Fabian Cenedese

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=5.2.0.9.1.20040826130046.01d35970@NT_SERVER \
    --to=cenedese@indel.ch \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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