public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/40332] (.eh_frame); no .eh_frame_hdr table will be created.
Date: Tue, 09 Jun 2009 09:37:00 -0000 [thread overview]
Message-ID: <20090609093656.5806.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40332-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from jakub at gcc dot gnu dot org 2009-06-09 09:36 -------
Couldn't reproduce (just built cp2k on x86_64-linux with trunk gfortran and
.eh_frame_hdr has been created just fine). I'm using binutils 2.19.51.0.2.
Anyway, you should probably just tar up the .a library and other things you are
linking together and with that report it in binutils bugzilla.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40332
next prev parent reply other threads:[~2009-06-09 9:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 17:05 [Bug target/40332] New: " jv244 at cam dot ac dot uk
2009-06-03 17:09 ` [Bug target/40332] " pinskia at gcc dot gnu dot org
2009-06-03 17:14 ` jv244 at cam dot ac dot uk
2009-06-09 8:34 ` jv244 at cam dot ac dot uk
2009-06-09 8:38 ` jakub at gcc dot gnu dot org
2009-06-09 8:54 ` jv244 at cam dot ac dot uk
2009-06-09 9:37 ` jakub at gcc dot gnu dot org [this message]
2009-06-09 10:26 ` jv244 at cam dot ac dot uk
2009-06-09 10:52 ` jv244 at cam dot ac dot uk
2009-06-20 17:56 ` jv244 at cam dot ac dot uk
2010-01-17 18:56 ` gary at intrepid dot com
2010-01-18 14:42 ` [Bug target/40332] [4.5 Regression] " jv244 at cam dot ac dot uk
2010-01-20 18:53 ` rguenth at gcc dot gnu dot org
2010-02-17 17:16 ` mmitchel at gcc dot gnu dot org
2010-02-19 15:59 ` jason at gcc dot gnu dot org
2010-02-19 18:00 ` jason at gcc dot gnu dot org
2010-02-20 3:50 ` jason at gcc dot gnu dot org
2010-02-20 3:50 ` jason at gcc dot gnu dot org
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=20090609093656.5806.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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.
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).