Hello,
First, I would like to thank Ronald, Michael, Adam and everyone else for helping me to get started.
I have another problem. This time it's linking issue. I was compiling with gcc 3.3.
Please advise:
--- -e ... Making gdb_copy.o -e ... Making gdb_pc_com_intr.o -e ==> Archiving into libkern.a -e ==> Linking kernel.image thread-log.o: In function `sys_ipc_log_wrapper': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:179: undefined reference to `__stack_chk_fail' /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:65: undefined reference to `__stack_chk_fail' /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:179: undefined reference to `__stack_chk_fail' main-ia32-amd64.o: In function `main_arch()': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/main-ia32-amd64.cpp:112: undefined reference to `__stack_chk_fail' cpu-common.o: In function `Cpu::show_cache_tlb_info(char const*)': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/cpu-common.cpp:(.initcall.text+0x381): undefined reference to `__stack_chk_fail' cpu-common.o:/home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/cpu-common.cpp:892: more undefined references to `__stack_chk_fail' follow make[4]: *** [kernel.image] Error 1 make[4]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel/fiasco/build' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel/fiasco/build' make[2]: *** [build] Error 2 make[2]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel/fiasco' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel' make: *** [kernel] Error 2 ubuntu@ubuntu:~/l4-devel/l4$ ---
Hi,
On Thu Mar 08, 2007 at 00:26:55 +0300, Igor Shmukler wrote:
I have another problem. This time it's linking issue. I was compiling with gcc 3.3.
Please advise:
I just tried to reproduce this, with no luck. Linking always worked, with g++ (4.1) and g++-3.3.
This is an Ubuntu Feisty, right? Anything special in your setup?
-e ... Making gdb_copy.o -e ... Making gdb_pc_com_intr.o -e ==> Archiving into libkern.a -e ==> Linking kernel.image thread-log.o: In function `sys_ipc_log_wrapper': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:179: undefined reference to `__stack_chk_fail' /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:65: undefined reference to `__stack_chk_fail' /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:179: undefined reference to `__stack_chk_fail' main-ia32-amd64.o: In function `main_arch()': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/main-ia32-amd64.cpp:112: undefined reference to `__stack_chk_fail' cpu-common.o: In function `Cpu::show_cache_tlb_info(char const*)': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/cpu-common.cpp:(.initcall.text+0x381): undefined reference to `__stack_chk_fail' cpu-common.o:/home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/cpu-common.cpp:892: more undefined references to `__stack_chk_fail' follow make[4]: *** [kernel.image] Error 1 make[4]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel/fiasco/build'
Adam
Am Mittwoch März 7 2007 schrieb Adam Lackorzynski:
Hi,
Hi!
On Thu Mar 08, 2007 at 00:26:55 +0300, Igor Shmukler wrote:
I have another problem. This time it's linking issue. I was compiling with gcc 3.3.
Please advise:
I just tried to reproduce this, with no luck. Linking always worked, with g++ (4.1) and g++-3.3.
This is an Ubuntu Feisty, right? Anything special in your setup?
In Edgy, the Ubuntu default compiler (but not the older 3.3 version) has the stack guard feature enabled by default. We have a fix for Fiasco in SVN, but Igor said he is still using a CVS checkout, which could be the problem here.
Igor: Are you sure you compiled Fiasco with GCC 3.3? Call 'make config' in l4/kernel/fiasco/build/ and check the compiler settings in the 'Compiling and Building' menu. If it says 'gcc' and 'g++', you are still using the Ubuntu default compiler for Fiasco. Just doing a 'make config' in l4/ is not enough, as it does not affect Fiasco build options.
Regards, Carsten
[...]
On Wed Mar 07, 2007 at 22:26:06 +0000, Carsten Weinhold wrote:
On Thu Mar 08, 2007 at 00:26:55 +0300, Igor Shmukler wrote:
I have another problem. This time it's linking issue. I was compiling with gcc 3.3.
Please advise:
I just tried to reproduce this, with no luck. Linking always worked, with g++ (4.1) and g++-3.3.
This is an Ubuntu Feisty, right? Anything special in your setup?
In Edgy, the Ubuntu default compiler (but not the older 3.3 version) has the stack guard feature enabled by default. We have a fix for Fiasco in SVN, but Igor said he is still using a CVS checkout, which could be the problem here.
The CVS version has this particular fix (it's a one-liner). So my question remains, Igor. What are software are you using? Are you using the latest CVS version?
Adam
I have another problem. This time it's linking issue. I was compiling with gcc 3.3.
Please advise:
I just tried to reproduce this, with no luck. Linking always worked, with g++ (4.1) and g++-3.3.
This is an Ubuntu Feisty, right? Anything special in your setup?
In Edgy, the Ubuntu default compiler (but not the older 3.3 version) has the stack guard feature enabled by default. We have a fix for Fiasco in SVN, but Igor said he is still using a CVS checkout, which could be the problem here.
I think because I changed gcc version manually, I probably got have something within the set that's incompatible. Things like that happen, and that's most likely why I bothered the list members. Sorry!
I'll try to check everything more carefully, before disturbing others next time. Hopefully, this will do it. I just hate building a sandbox.
The CVS version has this particular fix (it's a one-liner). So my question remains, Igor. What are software are you using? Are you using the latest CVS version?
Makes sense to me. :)
Thanks to everyone again.
l4-hackers@os.inf.tu-dresden.de