From: Yaakov (Cygwin/X) <yselkowitz@users.sourceforge.net>
To: cygwin-developers@cygwin.com
Subject: Error building libffi on x86_64
Date: Wed, 13 Mar 2013 04:27:00 -0000 [thread overview]
Message-ID: <20130312232736.3f71531b@YAAKOV04> (raw)
I have encountered the following error attempting to build
libffi-3.0.12 on Cygwin:
src/x86/.libs/win64.o:/usr/src/debug/libffi-3.0.12-1/src/x86/win64.S:298:(.text+0x69): relocation truncated to fit: R_X86_64_32S against symbol `ffi_closure_win64_inner' defined in .text section in src/x86/.libs/ffi.o
The only matches on Google for this sort of error were for >2GB code on
Linux, but I suspect the problem here is with the medium code model.
Here's what I'm working with:
http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/libffi
Yaakov
next reply other threads:[~2013-03-13 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 4:27 Yaakov [this message]
2013-03-13 9:25 ` Kai Tietz
2013-03-13 10:14 ` Yaakov
2013-03-13 10:38 ` Teemu Nätkinniemi
2013-03-13 9:28 ` Kai Tietz
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=20130312232736.3f71531b@YAAKOV04 \
--to=yselkowitz@users.sourceforge.net \
--cc=cygwin-developers@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).