[ECOS] RE: networking support for my eCos application

[C B <csb_80 at hotmail dot com>]

Ugh.  I had somehow specified arm-elf-ld rather than arm-elf-gcc as the linker.  Using arm-elf-gcc fixed the problem.  Thanks again for everyone's help.
 
Chris



> Date: Fri, 9 Nov 2007 09:21:54 +0000
> From: jld@ecoscentric.com
> To: csb_80@hotmail.com
> CC: ecos-discuss@ecos.sourceware.org
> Subject: Re: networking support for my eCos application
>
> Chris
>
> C B wrote:
>
>> But, when I try to compile and link my own code I still get these undefined references when I try to link with the eCos libs I've built:
>>
>>>>> undefined reference to 'init_all_network_interfaces'
>>>>> undefined reference to 'eth0_up'
>>>>> undefined reference to 'eth0_bootp_data'
>>>>> undefined reference to 'inet_ntoa'
>>
>> The command that gives those errors:
>> arm-elf-ld -L"C:\cygwin\opt\ecos\ecos-cvs\tmp\install\lib" -L"C:\cygwin\opt\ecos\ecos-cvs\tmp\net\common\current" -L"C:\cygwin\opt\ecos\gnutools\arm-elf\arm-elf\lib" -L"C:\cygwin\opt\ecos\gnutools\arm-elf\lib\gcc-lib\arm-elf\3.2.1" -Ttarget.ld -o"Simple.exe" ./simple.o
>>
>> The ping_test calls init_all_network_interfaces() so I'm not sure why it's not found.
>
> I suggest you look at the command line arguments which the eCos build
> system used to successfully link the ping test. Try linking your own
> code similarly at a command line prompt and, assuming the linker
> succeeds, work backwards to see which switches make the difference.
>
> For a start, you should be using "-nostdlib" in your link command and
> you should need to explicitly reference only the lib directory in your
> eCos install tree.
>
> John Dallaway
> eCosCentric Limited

_________________________________________________________________
Peek-a-boo FREE Tricks & Treats for You!
http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss