🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.next.sysadmin
2 messages
2 total messages Started by Uwe Mueller Wed, 29 Jul 1992 11:14
gcc-2.1 and libg++-2.2 problems with ld ...
#292
Author: Uwe Mueller
Date: Wed, 29 Jul 1992 11:14
25 lines
1383 bytes

When trying to compile libg++-2.2 using gcc Version 2.1 everything works  
fine, until the following linker error occurs:

------------------------------------------------------------------------

gcc -o gperf new.o options.o iterator.o main.o gen-perf.o key-list.o  
list-node.o hash-table.o bool-array.o read-line.o std-err.o version.o   
./../libg++.a
ld: options.o symbol 37 (___DTOR_LIST__) has unknown n_type field (0x16)
collect: /bin/ld returned 1 exit status
*** Exit 1
Stop.

-------------------------------------------------------------------------

has anyone any Idea what goes wrong? There is a new ld located in  
/usr/local/lib/gcc-lib/next/2.0/ which is part of the release of 2.1 of  
gcc. However, the makefile tries to use the old one in /bin/ld. Attempts  
to replace the old linker by the new one led to fatal system crashes ...

Thanks for any help

uwe@bio128.uni-bielefeld.de
Re: gcc-2.1 and libg++-2.2 problems with ld ...
#363
Author: Thomas Neumann
Date: Fri, 31 Jul 1992 17:45
28 lines
1612 bytes
In article <1992Jul29.111446.6189@unibi.uni-bielefeld.de> uwe@bio131.uni-bielefeld.de (Uwe Mueller) writes:
>
>
>When trying to compile libg++-2.2 using gcc Version 2.1 everything works  
>fine, until the following linker error occurs:
>
>------------------------------------------------------------------------
>
>gcc -o gperf new.o options.o iterator.o main.o gen-perf.o key-list.o  
>list-node.o hash-table.o bool-array.o read-line.o std-err.o version.o   
>./../libg++.a
>ld: options.o symbol 37 (___DTOR_LIST__) has unknown n_type field (0x16)
>collect: /bin/ld returned 1 exit status
>*** Exit 1
>Stop.
>
>-------------------------------------------------------------------------
>
>has anyone any Idea what goes wrong? There is a new ld located in  
>/usr/local/lib/gcc-lib/next/2.0/ which is part of the release of 2.1 of  
>gcc. However, the makefile tries to use the old one in /bin/ld. Attempts  
>to replace the old linker by the new one led to fatal system crashes ...

You need to use the `-fno-gnu-linker' option. `n_type' 0x16 is
GNU ld specific, thus NeXT ld doesn't like it.
For convenience you may want to add this to your `specs' file.

bye -- Thomas
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