From: Richard Copley <rcopley@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Daniel Colascione <dancol@dancol.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: -znocombreloc?
Date: Sun, 4 Dec 2016 10:36:08 +0000 [thread overview]
Message-ID: <CAPM58ohG65M2KUs9x3=YiJB1A+4iY_owiqtBnXSwt-XCUn-pTQ@mail.gmail.com> (raw)
In-Reply-To: <2f0ed5df-5818-3d68-f52d-f73660b689d3@cs.ucla.edu>
On 4 December 2016 at 05:36, Paul Eggert <eggert@cs.ucla.edu> wrote:
> Daniel Colascione wrote:
>>
>> Does anyone remember _why_ temacs segfaults on startup unless we give ld
>> this
>> option?
>
>
> It doesn't segfault for me, even when I build with -zcombreloc. I think
> -znocombreloc worked around bugs in now-obsolete versions of the GNU linker.
> See, for example:
>
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2004-02/msg00278.html
> https://lists.gnu.org/archive/html/help-gnu-emacs/2003-05/msg00627.html
>
> Looking at recent GCC documentation it appears that this old hack should not
> matter now, so I'm inclined to remove it, as in the proposed patch
> (attached), which I tested on Fedora 24 x86-64 but have not installed.
Not sure where GCC and x86-64 come into it if this was for the Solaris native
linker. (Is Solaris still a thing?)
next prev parent reply other threads:[~2016-12-04 10:36 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 ` Richard Copley [this message]
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 ` -znocombreloc? Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM58ohG65M2KUs9x3=YiJB1A+4iY_owiqtBnXSwt-XCUn-pTQ@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=dancol@dancol.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.