From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: linker error with gcc flag -mfunction-return=thunk
Date: Mon, 25 Jun 2018 14:08:00 -0000 [thread overview]
Message-ID: <20180625121613.GL28757@calimero.vinschen.de> (raw)
In-Reply-To: <67f4ac9a-5fe8-14d2-031f-288bbfccfc7a@ssi-schaefer.com>
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
On Jun 25 14:08, Michael Haubenwallner wrote:
> Hi,
>
> I'm encountering a package's configure script (openssh-7.7p1) that
> successfully tests for the compiler flag "-mfunction-return=thunk",
> which causes subsequent linker errors (and fails to identify zlib):
> relocation truncated to fit: R_X86_64_32S against `.text'
>
> The compiler used is gcc-7.3.0 with binutils-2.29.1.20171006 (current),
> and the easiest test case here is:
>
> $ echo 'int main() { return 0; }' > conftest.c
> $ gcc -mfunction-return=thunk conftest.c
> /tmp/ccv1Ird0.o:conftest.c:(.text+0x1a): relocation truncated to fit: R_X86_64_32S against `.text'
> collect2: error: ld returned 1 exit status
>
> Not sure though where to finally report this problem:
> * openssh, as they should do a link-test rather than compile-test
> * gcc, as their generated code is wrong for cygwin
> * binutils, as their ld is unable to link that code
> * cygwin, as the maintainers of cygwin support in binutils+gcc
>
> After all, openssh-7.7p1-1.src cygwin package currently fails to compile.
configure with --without-hardening for the time being.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-25 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 12:41 Michael Haubenwallner
2018-06-25 14:08 ` Corinna Vinschen [this message]
2018-06-25 14:25 ` Corinna Vinschen
2018-06-25 18:33 ` Corinna Vinschen
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=20180625121613.GL28757@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).