From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23678 invoked by alias); 17 Apr 2009 23:31:14 -0000 Received: (qmail 23670 invoked by uid 22791); 17 Apr 2009 23:31:14 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 17 Apr 2009 23:31:09 +0000 Received: from spaceape14.eur.corp.google.com (spaceape14.eur.corp.google.com [172.28.16.148]) by smtp-out.google.com with ESMTP id n3HNV6mX007449; Fri, 17 Apr 2009 16:31:07 -0700 Received: from localhost.localdomain.google.com (dhcp-172-22-125-203.mtv.corp.google.com [172.22.125.203]) (authenticated bits=0) by spaceape14.eur.corp.google.com with ESMTP id n3HNV2sB012155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 17 Apr 2009 16:31:04 -0700 To: LinuxUser9 Cc: gcc-help@gcc.gnu.org Subject: Re: ld: error no .eh_frame_hdr table will be created. References: <23105607.post@talk.nabble.com> <23106711.post@talk.nabble.com> From: Ian Lance Taylor Date: Fri, 17 Apr 2009 23:31:00 -0000 In-Reply-To: <23106711.post@talk.nabble.com> (LinuxUser9's message of "Fri\, 17 Apr 2009 14\:55\:40 -0700 \(PDT\)") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2009-04/txt/msg00226.txt.bz2 LinuxUser9 writes: > Thanks for the explanation of the error. Now just want understand the > debugging process on how I can fix this issue. Following is some more > information: > > - libx.o is compiled by the current version of gcc (4.3.2) > - If the above object is removed from the build, I no longer see the > eh_frame error. > - Is there any C++ implementation problem, that would cause an issue in the > object? > - Note that all objects use the same compiler but only inclusion of certain > objects cause this error. If you get this error with objects compiled with the same version of the compiler, then this sounds like a bug. I don't know if the bug is in gcc or in the linker. If you have time and you can provide the object file, please open a bug report against gcc; there are instructions in http://gcc.gnu.org/bugs.html . Thanks! Ian