Page 1 of 1

Boomstick and "no .eh_frame_hdr table will be created"

Posted: Sun Jun 24, 2012 8:10 am
by lukasz1235
Hi!
I'm using "Boomstick" script to build toolchain. All is OK, but when I try to compile "Hello world" I get:

Code: Select all

/home/lukasz/Pulpit/os/lukos-0.0.4/tools/boomstick/local/lib/gcc/x86_64-pc-lukos/4.5.0/../../../../x86_64-pc-lukos/bin/ld: error in /home/lukasz/Pulpit/os/lukos-0.0.4/tools/boomstick/local/lib/gcc/x86_64-pc-lukos/4.5.0/crtend.o(.eh_frame); no .eh_frame_hdr table will be created.
Thanks for reply,
lukasz1235

Re: Boomstick and "no .eh_frame_hdr table will be created"

Posted: Sun Jun 24, 2012 8:16 am
by lukasz1235
Ekhm... "How I can repair this?"

Re: Boomstick and "no .eh_frame_hdr table will be created"

Posted: Sun Jun 24, 2012 11:04 am
by JamesM
You'll need to give a little more detail than that.

For example, are you using C++? The linker is complaining that the sections that are going to be produced are incompatible with C++ w/exception handling.

A command line would be useful, for example.

Re: Boomstick and "no .eh_frame_hdr table will be created"

Posted: Sun Jun 24, 2012 1:04 pm
by lukasz1235

Code: Select all

x86_64-pc-lukos-gcc -o"../../img/bin/app1" app1.c

Re: Boomstick and "no .eh_frame_hdr table will be created"

Posted: Sun Jun 24, 2012 3:05 pm
by gerryg400
I had the same problem. Read this http://forum.osdev.org/viewtopic.php?f= ... _frame_hdr
You can get this error if your GCC is not built correctly. I'm not sure about the cross-compiler in the tutorial but for a long time I had this issue. Eventually modifying this line in my config.gcc solved it. My recollection is that it applies mainly to 64 bit cross-compilers. I'm not suggesting that it's your problem but offer it here in case others are looking for a solution.

Code: Select all

+   tmake_file="${tmake_file} i386/t-i386elf t-svr4 386/t-crtstuff"
Adding the i386/t-crtstuff was the solution.

Re: Boomstick and "no .eh_frame_hdr table will be created"

Posted: Mon Jun 25, 2012 7:49 am
by lukasz1235
Problem solved. Thanks.