public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brett dot albertson at stratech dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/33100]  New: on bootstrap getting section .eh_frame: bad cie version 0: offset 0x0
Date: Fri, 17 Aug 2007 20:59:00 -0000	[thread overview]
Message-ID: <bug-33100-9993@http.gcc.gnu.org/bugzilla/> (raw)

I now get this during bootstrap on Solaris x86 using the native linker
(/usr/ccs/bin/ld):

ld: fatal: unwind table: file
/u01/var/tmp/gcc_trunk_svn/gcc_20070817/./gcc/amd64/crtend.o: section
.eh_frame: bad cie version 0: offset 0x0

collect2: ld returned 1 exit status
gmake[5]: *** [libgcc_s.so] Error 1
gmake[5]: Leaving directory
`/u01/var/tmp/gcc_trunk_svn/gcc_20070817/i386-pc-solaris2.11/amd64/libgcc'

Let me know if you need more information.  It seems to occur when linking the
64bit libgcc.

Brett Albertson


-- 
           Summary: on bootstrap getting section .eh_frame: bad cie version
                    0: offset 0x0
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: brett dot albertson at stratech dot com
 GCC build triplet: i386-pc-solaris2.11
  GCC host triplet: i386-pc-solaris2.11
GCC target triplet: i386-pc-solaris2.11


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33100


             reply	other threads:[~2007-08-17 20:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 20:59 brett dot albertson at stratech dot com [this message]
2007-09-04 18:10 ` [Bug bootstrap/33100] [4.3 regression] " ro at gcc dot gnu dot org
2007-09-06  3:21 ` hjl at lucon dot org
2007-09-06 13:03 ` brett dot albertson at stratech dot com
2007-09-06 13:25 ` ro at techfak dot uni-bielefeld dot de
2007-09-06 17:47 ` hjl at lucon dot org
2007-09-10 14:41 ` ro at techfak dot uni-bielefeld dot de
2007-09-11 11:49 ` jsm28 at gcc dot gnu dot org
2007-09-11 12:24 ` hjl at lucon dot org
2007-09-11 12:46 ` ro at gcc dot gnu dot org
2007-09-11 12:47 ` ro at gcc dot gnu dot org
2007-09-11 12:48 ` ro at techfak dot uni-bielefeld dot de
2007-09-11 13:44 ` hjl at lucon dot org
2007-10-10 17:49 ` mmitchel at gcc dot gnu dot org
2008-03-14 21:28 ` [Bug bootstrap/33100] [4.3/4.4 " jcea at hispasec dot com
2008-03-15  0:43 ` jsm28 at gcc dot gnu dot org
2008-05-22  3:15 ` Daniel dot Davies at xerox dot com
2008-05-29  2:30 ` cnstar9988 at gmail dot com
2008-06-06 14:59 ` rguenth at gcc dot gnu dot org
2008-06-09 16:24 ` bugzilla-gcc at thewrittenword dot com
2008-06-11 14:42 ` hjl dot tools at gmail dot com
2008-07-18  3:38 ` cnstar9988 at gmail dot com
2008-08-27 22:13 ` jsm28 at gcc dot gnu dot org
2008-10-08 17:21 ` ro at techfak dot uni-bielefeld dot de
2008-10-08 17:24 ` ebotcazou at gcc dot gnu dot org
2008-10-09  7:17 ` cnstar9988 at gmail dot com
2008-10-09 11:02 ` cnstar9988 at gmail dot com
2008-10-09 11:24 ` ebotcazou at gcc dot gnu dot org
2008-10-09 17:36 ` ebotcazou at gcc dot gnu dot org
2008-10-10  0:43 ` cnstar9988 at gmail dot com
2008-10-10  5:16 ` ebotcazou at gcc dot gnu dot org
2008-10-10 14:42 ` ro at techfak dot uni-bielefeld dot de
2008-11-06 15:44 ` ro at gcc dot gnu dot org
2008-11-06 15:46 ` ro at techfak dot uni-bielefeld dot de
2008-11-06 15:46 ` ro at gcc dot gnu dot org
2008-11-20 17:12 ` ro at gcc dot gnu dot org
2008-11-20 17:15 ` ro at gcc dot gnu dot org
2008-11-20 17:16 ` ro at techfak dot uni-bielefeld dot de
2008-11-20 17:35 ` ro at gcc dot gnu dot org
2009-02-11 19:03 ` bugzilla-gcc at thewrittenword dot com

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=bug-33100-9993@http.gcc.gnu.org/bugzilla/ \
    --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).