Re: __stack_chk_fail in regexp is not defined

2013-11-09 Thread Andrey Borzenkov
В Sun, 10 Nov 2013 09:39:06 +0400
Andrey Borzenkov  пишет:

> В Sat, 9 Nov 2013 23:09:35 -0600
> Glenn Washburn  пишет:
> 
> > On Sat, 09 Nov 2013 12:37:08 +0100
> > Vladimir 'φ-coder/phcoder' Serbinenko  wrote:
> > 
> > > On 09.11.2013 05:11, Andrey Borzenkov wrote:
> > > > В Fri, 8 Nov 2013 14:42:43 -0600
> > > > Glenn Washburn  пишет:
> > > > 
> > > >> On Fri, 08 Nov 2013 19:54:43 +0100
> > > >> Vladimir 'φ-coder/phcoder' Serbinenko  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?
> > 
> > The commit for these logs is 9612ebc00ef5f186e9084b60ceeb1606d34f1d23.
> > 
> > It looks like stack protector is disabled in gcc and I don't believe
> > that -fno-stack-protector is being used.
> > 
> 
> Check for -fstack-protector is broken (always fails).

The problem is this commit:

commit 24f4e57c4684471da088c504dec0380886eece0c
Author: Vladimir Serbinenko 
Date:   Thu Nov 7 03:17:37 2013 +0100

* configure.ac: Prevent cflags leaking to subsequent tests by always
resetting cflags to target_cflags in target tests.

It removed restoring of CFLAGS causing leakage of temporary CFLAGS into
subsequent tests that do not explicitly reset CFLAGS. This is also broke efiemu 
tests:

efiemu runtime: No (cannot compile with -m64 -mcmodel=large -mno-red-zone 
-nostdlib)

And reason why all tests fail

gcc ... -march=i386 -m32 -mrtd -mregparm=3 -falign-jumps=1
-falign-loops=1 -falign-functions=1 -freg-struct-return -mno-mmx -mno-sse 
-mno-sse2 -mno-3dnow -fno-dwarf2-cfi-asm -fno-asynchronous-unwind-tables -m64 
-mcmodel=large -mno-red-zone -nostdlib -Wall -W '-I$(top_srcdir)/include' 
'-I$(top_builddir)/include' -DGRUB_MACHINE_PCBIOS=1 -DGRUB_MACHINE=I386_PC 
-DGRUB_TARGET_CPU_I386=1 conftest.c -S -fstack-protector -o conftest.s
conftest.c:1:0: error: CPU you selected does not support x86-64 instruction set
conftest.c:1:0: error: CPU you selected does not support x86-64 instruction set
conftest.c:1:0: warning: -mregparm is ignored in 64-bit mode [enabled by 
default]

CFLAGS need to be preserved and restored around all compiler flag tests; or all 
tests need to explicitly set them.




signature.asc
Description: PGP signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Re: __stack_chk_fail in regexp is not defined

2013-11-09 Thread Andrey Borzenkov
В Sun, 10 Nov 2013 09:39:06 +0400
Andrey Borzenkov  пишет:

> В Sat, 9 Nov 2013 23:09:35 -0600
> Glenn Washburn  пишет:
> 
> > On Sat, 09 Nov 2013 12:37:08 +0100
> > Vladimir 'φ-coder/phcoder' Serbinenko  wrote:
> > 
> > > On 09.11.2013 05:11, Andrey Borzenkov wrote:
> > > > В Fri, 8 Nov 2013 14:42:43 -0600
> > > > Glenn Washburn  пишет:
> > > > 
> > > >> On Fri, 08 Nov 2013 19:54:43 +0100
> > > >> Vladimir 'φ-coder/phcoder' Serbinenko  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?
> > 
> > The commit for these logs is 9612ebc00ef5f186e9084b60ceeb1606d34f1d23.
> > 
> > It looks like stack protector is disabled in gcc and I don't believe
> > that -fno-stack-protector is being used.
> > 
> 
> Check for -fstack-protector is broken (always fails).


The problem is this commit:

commit 24f4e57c4684471da088c504dec0380886eece0c
Author: Vladimir Serbinenko 
Date:   Thu Nov 7 03:17:37 2013 +0100

* configure.ac: Prevent cflags leaking to subsequent tests by always
resetting cflags to target_cflags in target tests.

It removed restoring of CFLAGS causing leakage of temporary CFLAGS into
subsequent tests. This is also broke efiemu tests:

efiemu runtime: No (cannot compile with -m64 -mcmodel=large -mno-red-zone 
-nostdlib)

And reason why all tests fail

gcc ... -march=i386 -m32 -mrtd -mregparm=3 -falign-jumps=1
-falign-loops=1 -falign-functions=1 -freg-struct-return -mno-mmx -mno-sse 
-mno-sse2 -mno-3dnow -fno-dwarf2-cfi-asm -fno-asynchronous-unwind-tables -m64 
-mcmodel=large -mno-red-zone -nostdlib -Wall -W '-I$(top_srcdir)/include' 
'-I$(top_builddir)/include' -DGRUB_MACHINE_PCBIOS=1 -DGRUB_MACHINE=I386_PC 
-DGRUB_TARGET_CPU_I386=1 conftest.c -S -fstack-protector -o conftest.s
conftest.c:1:0: error: CPU you selected does not support x86-64 instruction set
conftest.c:1:0: error: CPU you selected does not support x86-64 instruction set
conftest.c:1:0: warning: -mregparm is ignored in 64-bit mode [enabled by 
default]

CFLAGS need to be preserved and restored around all compiler flag tests.


signature.asc
Description: PGP signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


grub_machine_fini definition inconsistencies

2013-11-09 Thread Glenn Washburn
I'm now getting compilation errors for platform efi.

/home/crass/development/bootloader/grub2-src/grub.git/grub-core/lib/efi/halt.c:
In function
‘grub_halt’: 
/home/crass/development/bootloader/grub2-src/grub.git/grub-core/lib/efi/halt.c:30:3:
error: too few arguments to function ‘grub_machine_fini’ In file
included
from 
/home/crass/development/bootloader/grub2-src/grub.git/grub-core/lib/efi/halt.c:24:0:
 
/home/crass/development/bootloader/grub2-src/grub.git/include/grub/kernel.h:117:6:
note: declared here

grub_machine_fini is defined to take one int argument in
include/grub/kernel.h, however grub-core/lib/efi/halt.c is calling
grub_machine_fini with no arguments.  Grep has shown several such
invocations.

___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Re: __stack_chk_fail in regexp is not defined

2013-11-09 Thread Andrey Borzenkov
В Sun, 10 Nov 2013 09:39:06 +0400
Andrey Borzenkov  пишет:

> В Sat, 9 Nov 2013 23:09:35 -0600
> Glenn Washburn  пишет:
> 
> > On Sat, 09 Nov 2013 12:37:08 +0100
> > Vladimir 'φ-coder/phcoder' Serbinenko  wrote:
> > 
> > > On 09.11.2013 05:11, Andrey Borzenkov wrote:
> > > > В Fri, 8 Nov 2013 14:42:43 -0600
> > > > Glenn Washburn  пишет:
> > > > 
> > > >> On Fri, 08 Nov 2013 19:54:43 +0100
> > > >> Vladimir 'φ-coder/phcoder' Serbinenko  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?
> > 
> > The commit for these logs is 9612ebc00ef5f186e9084b60ceeb1606d34f1d23.
> > 
> > It looks like stack protector is disabled in gcc and I don't believe
> > that -fno-stack-protector is being used.
> > 
> 
> Check for -fstack-protector is broken (always fails).

OK I know what happens (grub checks misuse $ac_compile internal
variable and as result mix host and target flags). Need some time to
come up with a fix though.


signature.asc
Description: PGP signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Re: __stack_chk_fail in regexp is not defined

2013-11-09 Thread Andrey Borzenkov
В Sat, 9 Nov 2013 23:33:54 -0600
Glenn Washburn  пишет:

> On Sat, 09 Nov 2013 12:37:08 +0100
> Vladimir 'φ-coder/phcoder' Serbinenko  wrote:
> 
> > On 09.11.2013 05:11, Andrey Borzenkov wrote:
> > > В Fri, 8 Nov 2013 14:42:43 -0600
> > > Glenn Washburn  пишет:
> > > 
> > >> On Fri, 08 Nov 2013 19:54:43 +0100
> > >> Vladimir 'φ-coder/phcoder' Serbinenko  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 ...


signature.asc
Description: PGP signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Re: __stack_chk_fail in regexp is not defined

2013-11-09 Thread Andrey Borzenkov
В Sat, 9 Nov 2013 23:09:35 -0600
Glenn Washburn  пишет:

> On Sat, 09 Nov 2013 12:37:08 +0100
> Vladimir 'φ-coder/phcoder' Serbinenko  wrote:
> 
> > On 09.11.2013 05:11, Andrey Borzenkov wrote:
> > > В Fri, 8 Nov 2013 14:42:43 -0600
> > > Glenn Washburn  пишет:
> > > 
> > >> On Fri, 08 Nov 2013 19:54:43 +0100
> > >> Vladimir 'φ-coder/phcoder' Serbinenko  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?
> 
> The commit for these logs is 9612ebc00ef5f186e9084b60ceeb1606d34f1d23.
> 
> It looks like stack protector is disabled in gcc and I don't believe
> that -fno-stack-protector is being used.
> 

Check for -fstack-protector is broken (always fails). Could you test
with explicit

TARGET_CFLAGS="-Os -fno-stack-protector"

(-Os to emulate default behavior)?


signature.asc
Description: PGP signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Re: __stack_chk_fail in regexp is not defined

2013-11-09 Thread Glenn Washburn
On Sat, 09 Nov 2013 12:37:08 +0100
Vladimir 'φ-coder/phcoder' Serbinenko  wrote:

> On 09.11.2013 05:11, Andrey Borzenkov wrote:
> > В Fri, 8 Nov 2013 14:42:43 -0600
> > Glenn Washburn  пишет:
> > 
> >> On Fri, 08 Nov 2013 19:54:43 +0100
> >> Vladimir 'φ-coder/phcoder' Serbinenko  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.


signature.asc
Description: PGP signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Re: Install_c merge intention

2013-11-09 Thread Andrey Borzenkov
В Sat, 09 Nov 2013 13:51:09 +0100
Vladimir 'φ-coder/phcoder' Serbinenko  пишет:

> Hello, all. install_c is feature complete and I intent to make it
> upstream unless issues are raised until 16 Nov. It's available under
> http://git.savannah.gnu.org/cgit/grub.git/log/?h=phcoder/install_c
> 

Does not build here

util/grub-mkimage.c:48:29: fatal error: grub/emu/config.h: Нет такого файла или 
каталога
compilation terminated.

HEAD is 1622e97606772a1a1c841ba15c67b8d5b419a027.


signature.asc
Description: PGP signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Re: pvgrub2 is merged

2013-11-09 Thread Andrey Borzenkov
В Sat, 09 Nov 2013 21:52:20 +0100
Vladimir 'φ-coder/phcoder' Serbinenko  пишет:

> Hello, all. pvgrub2 has just became part of upstream grub as ports i386-xen 
> and x86_64-xen.
> http://git.savannah.gnu.org/cgit/grub.git
> 
> Documentation on its usage is missing for now but in short:
> ARCH=x86_64
> ./autogen.sh
> ./configure --target=$ARCH --with-platform=xen
> make
> mkdir -p boot/grub/
> cat > boot/grub/grub.cfg < search -s root -f /boot/grub/grub.cfg
> configfile /boot/grub/grub.cfg
> EOF
> ./grub-mkstandalone --grub-mkimage=./grub-mkimage -o grub.xen -O $ARCH-xen -d 
> grub-core/ boot/grub/grub.cfg
> 

Do I understand it correctly that to use grub.xen it is enough to add

kernel = "/path/to/grub.xen"

to guest configuration?



signature.asc
Description: PGP signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Re: [Xen-devel] pvgrub2 is merged

2013-11-09 Thread Samuel Thibault
Vladimir 'φ-coder/phcoder' Serbinenko, le Sat 09 Nov 2013 21:52:20 +0100, a 
écrit :
> pvgrub2 has just became part of upstream grub as ports i386-xen and 
> x86_64-xen.

\o/

Samuel

___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


pvgrub2 is merged

2013-11-09 Thread Vladimir 'φ-coder/phcoder' Serbinenko
Hello, all. pvgrub2 has just became part of upstream grub as ports i386-xen and 
x86_64-xen.
http://git.savannah.gnu.org/cgit/grub.git

Documentation on its usage is missing for now but in short:
ARCH=x86_64
./autogen.sh
./configure --target=$ARCH --with-platform=xen
make
mkdir -p boot/grub/
cat > boot/grub/grub.cfg <

signature.asc
Description: OpenPGP digital signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


PowerMac serial console confusion

2013-11-09 Thread Aaro Koskinen
Hi,

On Apple Xserve G5, the device tree looks like this with Linux v3.12:

/proc/device-tree/ht@0,f200/pci@3/mac-io@7/escc@13000/ch-b@13000
/proc/device-tree/ht@0,f200/pci@3/mac-io@7/escc@13000/ch-a@13020

Linux picks the ch-a as the first serial port:

[2.288585] 0.00013020:ch-a: ttyS0 at MMIO 0x80013020 [...]

Also in Open Firmware the primary serial port seems to be ch-a (there
is only one port in the box anyway). However, that won't work in GRUB
and I need to say "serial escc-ch-b --speed=57600" to get the serial
console working.

It would seem that GRUB 2.00 has ch-a and ch-b the other way round:

add_device (macio_addr[2] + escc_addr[0] + 32, 1);
add_device (macio_addr[2] + escc_addr[0], 0);

[...]

add_device (grub_addr_t addr, int channel)

[...]

port->name = grub_xasprintf ("escc-ch-%c", channel + 'a');

Is this a bug or maybe I have missed something?

A.

___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


2 quick questions

2013-11-09 Thread Gerard Butler
Is it possible to pass a command to a Linux based OS? So for instance I select 
Ubuntu or Fedora and I tell it to run some script as soon as it boots and I can 
put this comand in the menuentry.
My second question is that is it possible to control navigation within GRUB 
using a joystick? I know it's possible to treat a joystick as a keyboard in 
several OSes, but at the boot menu I don't if it's possible for that to happen. 
  ___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Re: grub2 boot root-on-zfs errors

2013-11-09 Thread Vladimir 'φ-coder/phcoder' Serbinenko
On 09.11.2013 16:31, Beeblebrox wrote:
> As of today, Nov/9/13, I have updated the git repo to latest version.
> The error persists:
> 
> /usr/bin/ld: unrecognised emulation mode: elf_i386
> Supported emulations: elf_x86_64_fbsd elf_i386_fbsd
> cc: error: linker command failed with exit code 1 (use -v to see invocation)
> gmake[3]: *** [disk.module] Error 1
> gmake[3]: Leaving directory `/asp/git/grub/grub-core'
> 
> 
What is the value of your target_os ?
Did you rerun ./autogen.sh?
> On 11/5/13, Beeblebrox  wrote:
 Unrelated. float and double poisoning is OS-independent.
>>
>> Thank you - I really appreciate that information.
>> Is there anything you would like me to do re
>> Supported emulations: elf_x86_64_fbsd elf_i386_fbsd
>> Or will you be pushing a code revision into trunk?
>> Regards.
>>
> 
> ___
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 




signature.asc
Description: OpenPGP digital signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Re: grub2 boot root-on-zfs errors

2013-11-09 Thread Beeblebrox
As of today, Nov/9/13, I have updated the git repo to latest version.
The error persists:

/usr/bin/ld: unrecognised emulation mode: elf_i386
Supported emulations: elf_x86_64_fbsd elf_i386_fbsd
cc: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[3]: *** [disk.module] Error 1
gmake[3]: Leaving directory `/asp/git/grub/grub-core'


On 11/5/13, Beeblebrox  wrote:
>>> Unrelated. float and double poisoning is OS-independent.
>
> Thank you - I really appreciate that information.
> Is there anything you would like me to do re
> Supported emulations: elf_x86_64_fbsd elf_i386_fbsd
> Or will you be pushing a code revision into trunk?
> Regards.
>

___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Install_c merge intention

2013-11-09 Thread Vladimir 'φ-coder/phcoder' Serbinenko
Hello, all. install_c is feature complete and I intent to make it
upstream unless issues are raised until 16 Nov. It's available under
http://git.savannah.gnu.org/cgit/grub.git/log/?h=phcoder/install_c



signature.asc
Description: OpenPGP digital signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


Re: __stack_chk_fail in regexp is not defined

2013-11-09 Thread Vladimir 'φ-coder/phcoder' Serbinenko
On 09.11.2013 05:11, Andrey Borzenkov wrote:
> В Fri, 8 Nov 2013 14:42:43 -0600
> Glenn Washburn  пишет:
> 
>> On Fri, 08 Nov 2013 19:54:43 +0100
>> Vladimir 'φ-coder/phcoder' Serbinenko  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?
> 
> 
> ___
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 




signature.asc
Description: OpenPGP digital signature
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel