From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: [ITA] binutils, mingw64-{i686,x86_64}-binutils
Date: Sat, 09 Jan 2021 17:49:21 +0100 [thread overview]
Message-ID: <87k0sm838u.fsf@Rainer.invalid> (raw)
I have finally figured out why building binutils (whatever version)
didn't work correctly with gcc-10, so I was able to build the current
release version of binutils 2.35.1 finally (and re-build the same
binutils version with itself). Enabling to move libbfd/libopcodes into
shared libraries has been prepared, but so far I have not been able to
build binutils that actually work (already the tests are failing).
The updated cygport file (and patches, albeit non-active for the actual
configuration) is available on the playground branch:
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/binutils.git;a=shortlog;h=refs/heads/playground
The build results on the CI:
https://ci.appveyor.com/project/cygwin/scallywag/builds/37184120
I have not yet started to work on the mingw64 packages.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
next reply other threads:[~2021-01-09 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 16:49 Achim Gratz [this message]
2021-01-09 17:18 ` Marco Atzeri
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=87k0sm838u.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@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).