[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Linking to Gt.m object files

From: nick clifton
Subject: Re: Linking to Gt.m object files
Date: Thu, 23 Feb 2012 16:41:28 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1

Hi Mike,

 but the linker fails.

Please could you open a bug report about this at:


Including the testcase will be really helpful. Itwill also be helpful to know that command line that g++ used to invoke the linker, as well as the target architecture for which this particular linker was configured. (I am currently assuming i386-pc-go32).

/usr/bin/ld.bfd.real: BFD (GNU Binutils for Ubuntu)

Note: 2.21... is an old binutils release. We are now on version 2.22, and the development sources are in advance of that. Not that it matters in this particular case as the problem appears to be reproducible with a linker built from today's sources. But I just thought that I should mention it, as the first thing anyone else looking at this bug is likely to try is using the latest linker.

internal error, aborting at ../../bfd/reloc.c line 6281 in

The problem in general is that the generic part of the linker is receiving an out-of-range error from that target specific backend when it is not expecting one. It is relatively easy to add some code to produce a warning message when this happens (rather than aborting), but I am a little bit concerned as to why the outofrange error is happening in the first place. If you fix the references to the undefined symbols (_Serenji and _Serenji.SHELL) does the abort go away ?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]