Re: __stack_chk_fail in regexp is not defined

[Glenn Washburn]

On Sun, 10 Nov 2013 09:40:58 +0400
Andrey Borzenkov <address@hidden> wrote:

> В Sat, 9 Nov 2013 23:33:54 -0600
> Glenn Washburn <address@hidden> пишет:
> 
> > On Sat, 09 Nov 2013 12:37:08 +0100
> > Vladimir 'φ-coder/phcoder' Serbinenko <address@hidden> wrote:
> > 
> > > On 09.11.2013 05:11, Andrey Borzenkov wrote:
> > > > В Fri, 8 Nov 2013 14:42:43 -0600
> > > > Glenn Washburn <address@hidden> пишет:
> > > > 
> > > >> On Fri, 08 Nov 2013 19:54:43 +0100
> > > >> Vladimir 'φ-coder/phcoder' Serbinenko <address@hidden>
> > > >> wrote:
> > > >>
> > > >>> On 08.11.2013 19:42, Glenn Washburn wrote:
> > > >>>> Now, I'm getting this error while building.  Bug in the awk
> > > >>>> script?
> > > >>>>
> > > >>>> cat syminfo.lst | sort | gawk
> > > >>>> -f ./grub.git/grub-core/genmoddep.awk
> > > >>>>> moddep.lst || (rm -f moddep.lst; exit 1) __stack_chk_fail in
> > > >>>>> regexp is
> > > >>>> not defined
> > > >>>>
> > > >>> What compiler do you use and which additional options did you
> > > >>> pass to it? It inserted this function call. We need either to
> > > >>> provide this function or inhibit compiler from emiting such
> > > >>> calls.
> > > >>
> > > >> I'm using gcc 4.7 on Ubuntu from the ubuntu-toolchain-r/test
> > > >> ppa. I do see a reference to __stack_chk_fail at
> > > >> grub-core/efiemu/runtime/efiemu.c:192.  It doesn't look like
> > > >> that file is generated.  Perhaps that function was
> > > >> accidentally added to that file?
> > > > 
> > > > It comes from using -fstack-protector GCC option. But configure
> > > > should have added -fno-stack-protector in this case.
> > > > 
> > > > Could you check defaults using
> > > > 
> > > > /path/to/your/gcc -Q --help=common
> > > > 
> > > > whether it is active by default? Also whether
> > > > -fno-stack-protector was used during compilation?
> > > > 
> > > You're right.
> > > @Glenn: can you tell us exact version of GRUB (e.g. git commit)
> > > and attach config.log?
> > 
> > I can confirm that adding -fno-stack-protector to CFLAGS allows the
> > compile to be successful.  So it does indeed seem to be a problem
> > with the configure script.
> 
> CFLAGS or TARGET_CFLAGS? CFLAGS should not be a problem, it is host
> tools which should work. It is TARGET_CFLAGS that are needed. If it is
> fixed by changing CFLAGS, we have another problem ...

You may have discovered already the problem, but I wanted to confirm
that it was CFLAGS, not TARGET_CFLAGS, that I set to
-fno-stack-protector.

signature.asc
Description: PGP signature