public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Joachim Metz <joachim.metz@gmail.com>
To: cygwin@cygwin.com
Subject: Failing build when using binutils 2.34-1 on Cygwin 32/64-bit
Date: Wed, 04 Mar 2020 14:44:00 -0000	[thread overview]
Message-ID: <CAPq-Lw3nzN7UgCT7u_3m7n5WnzhFLfBVgwRjeYxao-Cx4_bgBA@mail.gmail.com> (raw)

I maintain numerous projects, as part of that I've set up CI tests that use
current Cygwin 32-bit and 64-bit. Recently I've noticed that builds were
failing with errors like:

https://ci.appveyor.com/project/libyal/libfwsi/build/job/7b822r4j4ghfs2m5#L953

/usr/lib/gcc/i686-pc-cygwin/9.2.0/../../../../i686-pc-cygwin/bin/ld:
fwsi_test_error.o: in function `fwsi_test_error_sprint':
/home/appveyor/libfwsi/tests/fwsi_test_error.c:72: undefined reference to
`_imp__libfwsi_error_sprint'

https://ci.appveyor.com/project/libyal/libfwsi/build/job/3qnu5pk3lm4u12pe#L960

/home/appveyor/libfwsi/tests/fwsi_test_error.c:72: undefined reference to
`__imp_libfwsi_error_sprint'
/home/appveyor/libfwsi/tests/fwsi_test_error.c:72:(.text.startup+0x24):
relocation truncated to fit: R_X86_64_PC32 against undefined symbol
`__imp_libfwsi_error_sprint'

Since I did not make significant changes to the project sources I started
analyzing the build environment. I was able to reproduce the issues
with binutils 2.34-1 on Cygwin 64-bit on a separate Windows 10
installation.

When I reverted to binutils 2.31-1 the build issues do NOT surface. I
suspect a change or issue with binutils 2.34-1 is causing the build issues.
Happy to provide additional details / help troubleshooting where possible.

Kind regards,
Joachim

P.S. I tried searching for duplicate issues on
https://sourceware.org/cgi-bin/search.cgi?form=extended&qprev= unfortunately
it returns a lot of results and starts with the oldest results first. Small
request for the future, consider adding an option to return results in
reverse order.

Tracking this for the libyal projects in
https://github.com/libyal/libyal/issues/83

--
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:[~2020-03-04  8:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04 14:44 Joachim Metz [this message]
2020-03-04 14:58 ` JonY

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=CAPq-Lw3nzN7UgCT7u_3m7n5WnzhFLfBVgwRjeYxao-Cx4_bgBA@mail.gmail.com \
    --to=joachim.metz@gmail.com \
    --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).