🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

1 total messages Started by Heiko Weber Mon, 05 Oct 1992 19:34
undefined symbols with gcc2.2.2
#432
Author: Heiko Weber
Date: Mon, 05 Oct 1992 19:34
33 lines
1755 bytes
Hello !

I've tried to compile some C++ files with the gcc2.2.2 - but the
I am unable to link the stuff together:

g++ -IMx Hello.o HelloApp.o -L /usr/X/lib -LMx -lMx -lXm -lXt -lX11 -lsocket -lnsl -o HelloApp
Undefined			first referenced
 symbol  			    in file
.L_f22_e                            Mx/libMx.a(MxAppl.o)
.L_B5_e                             Mx/libMx.a(MxUIComp.o)
.L_B5                               Mx/libMx.a(MxUIComp.o)
.L_f19_e                            Mx/libMx.a(MxMainW.o)
.L_f13_e                            Mx/libMx.a(Main.o)
ld: HelloApp: fatal error: Symbol referencing errors. No output written to HelloApp
*** Error code 1 (bu21)

make: fatal error.

The library libMx.a is my own, simple collection of C++ classes. The
same files compiles and links (and run) without any problem under
HP Unix 8.05 with the HP C++ develop. environment. Viewing to the
undefined symbols of the listed object-files with 'nm -u' results
into the same undefined symbols, for example '.L_f19e' ...

Why does the gcc produce these symbols, is there a workaround ?

Thanks in advance

   Heiko
-- 
| Heiko Weber jun. | heiko@uwesa.hanse.de | carrier: 049-4169-448 |
| D-2151 Sauensiek | Loehe 5 |  Germany   | voice:  049-4169-1366 | 
+------------------+----------------------+-----------------------+
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads