This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
egcs on LynxOS (x86)
- To: egcs-bugs at cygnus dot com
- Subject: egcs on LynxOS (x86)
- From: Hanan Rosemarin <h_rosemarin at hotmail dot com>
- Date: Mon, 26 Jan 1998 12:03:21 +0200
- Reply-To: h_rosemarin at hotmail dot com
hi,
I tried building egcs-1.0.1 on lynxos-2.5.0.
I was surprised to see that the 'configure' script recognized the os,
however I still had to do a little tweaking (virtualy nothing works the
first time on lynx). At first I had to comment out the extern
declarations of mktemp(), as it is declared by a "#define mktemp()
lynx-mktemp()". Next, I had to comment out the linker argument "P1000"
in "lynx-ng.h".
Currently I'm stuck with the following problem, the line:
'./xgcc -B./ -DIN_GCC -I./include -g enquire.o -o enquire'
fails due to unresolved 'Ltext0' in function 'eldprop', and in various
other functions.
I could not make that out, I found something remotely like 'Ltext0' in
the file 'dbxout.c'. The archive libgcc2.a was filled with unresolved
('U') refernces to 'Ltext0'. Apparently, the assembly generated contains
a forward refernce to 'Ltext0', and it declares it a few lines down the
road. However, when checking with 'nm' - the symbol is 'Unresolved'. I
saw something about symbols begining with 'L' being local, but I don't
see why they are not resolved.
Any hints?
thanks in advance,
hanan
p.s. I tried changing the DEBUGGING_INFORMATION definition to DWARF (it
used to be DBX), and it tried to compile dwarfout.c, instead. However,
it failed linking due to missing ASM_OUTPUT_DEF macro. this macro
resided in 'defaults.h'. anyway it seems that the definitions in the
lynx-ng.h / xm-lynx.h, are way off. I believe Lynx compiles best when
set to bsd-4 type machine (instead svr3 to which it is currently
defined).
does anyone have an idea as to proper settings for LynxOS (or better
yet, has anyone managed to compile it on LynxOS)
hanan