This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Chromium ISSUE with GCC 4.8
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: awarecons at gmail dot com
- Cc: Paolo Carlini <paolo dot carlini at oracle dot com>, gcc at gcc dot gnu dot org
- Date: Sun, 16 Dec 2012 14:32:31 -1000 (TAHT)
- Subject: Re: Chromium ISSUE with GCC 4.8
- References: <CACGq7x3dYjZvTYGzRTV7LpUxWg_D4n3XfqUBiUdtaAo745AJag@mail.gmail.com> <50B7A2C6.7040607@oracle.com>
On Thu, 29 Nov 2012, Paolo Carlini wrote:
>> FreeBSD 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC
>> 2012 root@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
>> i386
>>
>> chromium-23.0.1271.64_1 compiled perfectly.
>>
>> But chromium-23.0.1271.91 fails:
> Looks like you aren't building with current mainline and your tree doesn't
> include the fix for PR55337.
Yes, in fact also
/proc/self/exe: No such file or directory
indicates that the version of GCC you are using is of some GCC 4.8.0
vintage, alas a bit older and does not yet feature
2012-11-12 Ian Lance Taylor <iant@google.com>
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Gerald Pfeifer <gerald@pfeifer.com>
* configure.ac: Check for getexecname.
* fileline.c: #include <errno.h>. Define getexecname if not
available.
(fileline_initialize): Try to find the executable in a few
different ways.
* print.c (error_callback): Only print the filename if it came
from the backtrace state.
* configure, config.h.in: Rebuild.
If you are using GCC built yourself from upstream sources, I recommend
you upgrade to current SVN.
If you are using the lang/gcc48 port in FreeBSD, on December 5th (which
is a few days after your report), I updated that one to include the change
above.
Can you please try updating GCC and advise whether this fixes the issue?
(If it does not, it's probably best to report a bug following the
instructions at http://gcc.gnu.org/bugs as indicated in the error
message you quoted to us.)
Gerald