The following appears with the compiler versions:
gcc-2.8.1
egcs-2.90.17p
pgcc-2.90.21
pgcc-2.91.08
pgcc-2.91.09
I ave mentioned the "start of problems" while trying to
compile ext.so for FileRunner. Linking this extension
library reports undefined symbols for such "boring" things
like "printf", "statfs" etc.
After adding "-lc" to the gcc options, the problem disappear.
But: This was needed ever before 2.1.90 with the SAME FileRunner-version.
Next was compiling sysklogd-1.3.25. This works fine. I checked the resulting
programs witj ldd and it said me "statically linked ELF". I checked my
already installed conterparts, result: "dybamically linked ELF". Hmmmm....
I tried to compile sysklogd-1.3.25 with "-fpic" option set. Result:
klogd.c: In function `CloseLogSrc':
klogd.c:302: fixed or forbidden register was spilled.
This may be due to a compiler bug or to impossible asm
statements or clauses.
?????? Confusion arises...
Next I wrote a simple "Hello Linux"-C-programm (only with one "printf" inside
main and a return statement.
gcc -c HelloLinux.c -o HelloLinux
works -- but again it was statically linked. But
gcc -fpic -c HelloLinux.c HelloLinux.
produces a program that segfaults.
WHAT HAPPENS HERE? AM I SUDDENLY TOO STUPID TO COMPILE A SIMPLE PROGRAM? OR
AM I BLIND???
PLease help me to see again! ;-)
My system is updated according to the Changes-file of the kernel sources. I am
using kernel 2.1.90 on a Intel-based system.
KEEP HACKING!
meino
----------------------------------
E-Mail: Meino Christian Cramer <root@solfire.ludwigsburg.netsurf.de>
Date: 22-Mar-98
Time: 09:27:24
This message was sent by XFMail
----------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu