From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Andreas Schwab <schwab@linux-m68k.org>
Cc: dancol@dancol.org, emacs-devel@gnu.org
Subject: Re: -znocombreloc?
Date: Sun, 4 Dec 2016 18:47:29 -0800 [thread overview]
Message-ID: <c45f560e-a57a-3810-aedb-7e90d94c109c@cs.ucla.edu> (raw)
In-Reply-To: <83lgvvlndb.fsf@gnu.org>
On 12/04/2016 07:34 AM, Eli Zaretskii wrote:
> What about other systems: Solaris, *BSD (when they use GNU ld)? Do
> they also not need this?
They did long ago, with binutils 2.14 (2003) reportedly, but I doubt
whether they need it now. I attempted to reproduce the problem on
Solaris 10 sparc (it ships with binutils 2.15 dated 2004) and failed to
reproduce it. I could well have gotten the recipe wrong, though. I doubt
whether the dwindling band of Solaris users will care about this one way
or another, as they invariably use the Solaris linker, which does not
need this flag.
Following up to other emails:
Yes, Solaris is still a thing and we run it on a few servers here.
Solaris 11.3 was released last month. Oracle plans to support Solaris 10
through 2021 and Solaris 11 through at least 2024.
Daniel's right that -znocombreloc isn't needed if CANNOT_DUMP.
next prev parent reply other threads:[~2016-12-05 2:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 0:12 -znocombreloc? Daniel Colascione
2016-12-04 5:36 ` -znocombreloc? Paul Eggert
2016-12-04 10:36 ` -znocombreloc? Richard Copley
2016-12-04 11:24 ` -znocombreloc? Richard Copley
2016-12-04 15:34 ` -znocombreloc? Eli Zaretskii
2016-12-04 17:14 ` -znocombreloc? Daniel Colascione
2016-12-05 2:47 ` Paul Eggert [this message]
2016-12-07 23:58 ` -znocombreloc? Jeremie Courreges-Anglas
2016-12-08 1:19 ` -znocombreloc? Paul Eggert
-- strict thread matches above, loose matches on Subject: below --
2016-12-05 3:23 -znocombreloc? Ali Bahrami
2016-12-05 15:50 ` -znocombreloc? Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c45f560e-a57a-3810-aedb-7e90d94c109c@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=dancol@dancol.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).