2011-08-08 15:26:24     Eclipse/bfin-elf-gcc Linker problem

Document created by Aaronwu Employee on Oct 16, 2013
Version 1Show Document
  • View in full screen mode

2011-08-08 15:26:24     Eclipse/bfin-elf-gcc Linker problem

Daniel Price (UNITED STATES)

Message: 102857   

 

I'm building a large (300 source files) bare-metal Blackfin project in Eclipse. Everything compiles fine, but there's a strange bug in the linker phase.

 

I'm using the automatically-generated makefiles. When it tries to link everything together, it fails quickly with this error message:

 

bfin-elf-gcc: ./Fusion/common/clib/strng/fclstrchr.o: No such file or directory

 

This is listed in the expanded link command correctly (./Fusion/common/clib/string/fclstrchr.o).

 

On Friday, it had dropped a different character in the error message (./Fusion/common/clib/string/fclsrchr.o). I change a linker flag since then.

 

Has anyone seen this before? Any ideas?

QuoteReplyEditDelete

 

 

2011-08-09 03:44:49     Re: Eclipse/bfin-elf-gcc Linker problem

David Gibson (UNITED KINGDOM)

Message: 102859   

 

I think the first step here is to determine whether the error is being caused by the Eclipse IDE/Makefile or the Linker.

 

Can you enable the verbose build output in Eclipse and view the link command in the console window?

 

Does the command line look correct there?

 

If it does, could you copy the link command line and execute it yourself from a shell to see if the error occurs on the command line.

 

 

 

D

QuoteReplyEditDelete

 

 

2011-08-09 11:51:18     Re: Eclipse/bfin-elf-gcc Linker problem

Daniel Price (UNITED STATES)

Message: 102869   

 

Yeah, as stated above, the link command in the Eclipse console looks correct. I can't copy-paste it into a shell, as there are too many characters in the command, but I dumped it to a file and invoked the linker with @file and the error didn't occur.

 

If I change a link option so that there are more characters at the beginning of the link command, the missing character in the error output shifts by the same number of characters.

 

No files go into libraries before linking, so all 330 of them show up in the link command. I'm working on getting them grouped into libs, but I haven't used Eclipse for C development before so that's going slowly.

QuoteReplyEditDelete

 

 

2011-08-12 10:30:08     Re: Eclipse/bfin-elf-gcc Linker problem

Glen Anderson (UNITED STATES)

Message: 102917   

 

Interesting... I couldn't find anything in Eclipse's bug database that would describe that so perhaps it's a problem with the Blackfin specific plugins for Eclipse. Would it be possible for you to post the output of the link with the -v switch enabled? That might help narrow things down a bit.

Attachments

    Outcomes