From: Petr Hracek <phracek@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 20190@debbugs.gnu.org
Subject: bug#20190: Building emacs-24.4 against GCC-5.0
Date: Thu, 26 Mar 2015 16:06:16 +0100 [thread overview]
Message-ID: <55142068.9070806@redhat.com> (raw)
In-Reply-To: <55130B64.2010503@cs.ucla.edu>
On 03/25/2015 08:24 PM, Paul Eggert wrote:
> On 03/25/2015 05:27 AM, Petr Hracek wrote:
>> Starting program: /builddir/build/BUILD/emacs-24.5/src/temacs --batch
>> --load loadup bootstrap
>> Error in re-setting breakpoint 1: Cannot access memory at address
>> 0x17a563
>> Error in re-setting breakpoint 2: Cannot access memory at address
>> 0x19f9ef
>
> This makes it look like there's something wrong with your compiler,
> linker, or debugger. At this point Emacs should just be a normal C
> program, and there should be no errors in setting breakpoints.
>
> I suggest comparing the output of 'configure' and 'make' and 'gdb'
> with that of Fedora 21, to see if there are some options missing or
> extra. I'm attaching my output. For example, look at the command
> that created temacs (it's long, and says '-o temacs' in it).
>
> Also, you might want to look at Debian bug 684788 for
> possibly-relevant ideas:
>
> http://bugs.debian.org/684788
Finally I have found an issue.
If I specify in LDFLAGS file like -spec=<some_file> which contains:
<some_file>
*self_spec:
+ %{!shared:-pie}
*link:
+ -z now
Then the build fails.
If I remove it then all goes fine.
Just for information.
--
Petr Hracek
Software Engineer
Developer Experience
Red Hat, Inc
Mob: +420777056169
email: phracek@redhat.com
next prev parent reply other threads:[~2015-03-26 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 12:51 bug#20190: Building emacs-24.4 against GCC-5.0 Petr Hracek
2015-03-24 17:38 ` Paul Eggert
2015-03-25 12:27 ` Petr Hracek
2015-03-25 19:24 ` Paul Eggert
2015-03-26 15:06 ` Petr Hracek [this message]
2015-03-26 17:10 ` Paul Eggert
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=55142068.9070806@redhat.com \
--to=phracek@redhat.com \
--cc=20190@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.