public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: DJGPP cross compiler crashes.
Date: Fri, 19 Apr 2019 14:52:00 -0000	[thread overview]
Message-ID: <d3c01bfa-7efe-aaa1-8003-1550f268af64@t-online.de> (raw)
In-Reply-To: <CADt95777JAis3a0WSUVy7oX5MbGEfTQ95aHtRT-yNb9kvA_pVg@mail.gmail.com>

[A side note, first: this is a traditional mailing list, i.e. the policy
is snipping and bottom-replying...]


Am 19.04.2019 um 01:41 schrieb Carlo B.:

> I have no idea how you can run it without errors, please note that
> i586-pc-msdosdjgpp-gcc works fine until it does not link.

Please note that this quite probably means that it's not the compiler
package itself that's causing you grief, but rather djgpp-binutils.  Or
it could be the runtime base package.

So: did you run cygcheck -c on your djgpp packages?  Check if getting
them from a different cygwin mirror changes anything?

Have you tried adding options to the gcc command line to see what it's
actually doing in some more detail, like '-v' or '-Wl,-v'?

I checked on Win10 Home, originally just 64-bit.  I've had these
packages installed for years, and they haven't changed since, so there's
not really any good reason to assume they should suddenly be broken this
week.  And at least from what I'm looking at, they aren't.

Just for making extra sure, I just added DJGPP to the Cygwin-32
installation on the same machine, and again, it just worked without a hitch.



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2019-04-19 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 14:11 Carlo B.
2019-04-18 21:19 ` Hans-Bernhard Bröker
2019-04-18 23:41   ` Carlo B.
2019-04-19 14:52     ` Hans-Bernhard Bröker [this message]

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=d3c01bfa-7efe-aaa1-8003-1550f268af64@t-online.de \
    --to=hbbroeker@t-online.de \
    --cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).