Angus> Incidentally, (temporarily) commenting it out in this file
Angus> (specs) did not remove my multiply defined problem. Any ideas
Angus> who I should contact?
JMarc> Try first to compile a simple C or C++ program. It is better to ask
JMarc> for help with a small example when possible.
Granted. Unfortunately, I can compile kbiff without problems. No kde code is
truly small (all those libraries!) but this is as small as they get.
Note again the multiple definition of libgcc (ie, no problem there). The only
real difference that I can see between this and LyX's linking is the -rpath
directive here.
/usr/local/GNU/lib/gcc-lib/alphaev5-dec-osf4.0e/2.95.2/collect2 -G 8 -O3 -call_shared
-o kbiff -s /usr/lib/cmplrs/cc/crt0.o -L/usr/local/kde/lib -L/usr/local/qt/lib
-L/usr/lib -L/usr/shlib -L/usr/shlib/X11 -L/usr/local/lib -L/usr/local/GNU/lib
-L/usr/local/qt/lib -L/usr/local/kde/lib
-L/usr/local/GNU/lib/gcc-lib/alphaev5-dec-osf4.0e/2.95.2 -L/usr/lib/cmplrs/cc
-L/usr/local/GNU/lib setupdlg.o kbiff.o main.o kbiffmonitor.o notify.o kbiff.moc.o
kbiffmonitor.moc.o notify.moc.o setupdlg.moc.o status.moc.o Trace.o kbiffurl.o
status.o -lmediatool -lkfile -lkfm -lkdecore -lXext -lqt -lX11 -ldnet_stub -lkdeui
-lkdecore -lXext -lqt -lX11 -ldnet_stub -rpath
/usr/local/kde/lib:/usr/local/qt/lib:/usr/lib -lstdc++ -lm -lgcc -lc -lgcc
LyX appears to be invoking code in libgcc.a (code not invoked in kbiff) that is
multiply defined. I guess that I'll have to track down the bit of LyX that
makes those calls to "multiply defined" code:
/usr/local/GNU/lib/gcc-lib/alphaev5-dec-osf4.0e/2.95.2/libgcc.a(_eh.o):
_GLOBAL_$F$__default_terminate: multiply defined
/usr/local/GNU/lib/gcc-lib/alphaev5-dec-osf4.0e/2.95.2/libgcc.a(frame.o):
__register_frame_info_table: multiply defined
/usr/local/GNU/lib/gcc-lib/alphaev5-dec-osf4.0e/2.95.2/libgcc.a(frame.o):
__deregister_frame_info: multiply defined
Ugggghhhhhh!
Any ideas?
Is there anyone else out there who uses gcc-2.95.2 to compile LyX on an Alpha?
Angus
