Klemen Košir wrote:
> I get the same error. It's a normal warning, but gcc treats it as an error.
>
>
> On Sun, Sep 1, 2013 at 6:56 PM, Bruce Dubbs <bruce.du...@gmail.com> wrote:
>
>> Klemen Košir wrote:
>>> I followed the instructions, but I set several environment variables:
>>>
>>> MAKEFLAGS="-j 4"
>>> CFLAGS="-march=corei7 -Os -pipe"
>>> CXXFLAGS="${CFLAGS}"
>>>
>>> The error:
>>>
>>> ../../binutils-2.23.2/binutils/stabs.c: In function 'parse_stab_type':
>>> ../../binutils-2.23.2/binutils/stabs.c:2797:57: error: 'physname' may be
>>> used uninitialized in this function [-Werror=maybe-uninitialized]
>>> variants[cvars] = debug_make_static_method_variant (dhandle,
>>> ^
>>> ../../binutils-2.23.2/binutils/stabs.c:2596:16: note: 'physname' was
>>> declared here
>>> const char *physname;
>>> ^
>>> cc1: all warnings being treated as errors
>>> make[4]: *** [stabs.o] Error 1
>>
>> OK, what happens if you unset CFLAGS and CXXFLAGS?
Don't top post on this list.
It's curious that you get a warning and we don't. It's also curious
that you get the error in line 2797, but not on line 2792. We are both
using the same compiler (gcc-4.8.1).
I'm confused by the code too. Line 2596 says 'const char *physname;'
and then the code assigns a value at line 2762. Not very constant. I
don't know why they don't just use 'char *physname = NULL;'.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
