This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Linkerscript
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: "Meulendijks, J." <Meulendijks at WT dot TNO dot NL>
- Cc: "'ecos-discuss at ecos dot sourceware dot org'" <ecos-discuss at ecos dot sourceware dot org>
- Date: 30 Sep 2004 11:33:17 +0100
- Subject: Re: [ECOS] Linkerscript
- References: <6B80E71673E6D611AC1D0008C7F37BC203F8E5DE@wt15.wt.tno.nl>
"Meulendijks, J." <Meulendijks@WT.TNO.NL> writes:
> Hi all,
>
> I read the following on the internet:
>
> "You can specify a file name to include sections from a particular file. You
> would do this if one or more of your files contain special data that needs to be
> at a particular location in memory. For example, use the following input.
>
> data.o(.data)"
>
> But when I use this the linker says: "cannot find data.o". But the linkcommand
> is including the directory in which data.o is located. I do this with the -L
> option.
> I don't see what's is wrong with it but I only get this to work if I replace
> "data.o(.data)" with "c:/bla/bla/data.o(.data)". So I must give the absolute
> path and that's NOT what I want.
I believe this only works with files that are mentioned on the command
line, or are found in libraries. So add data.o to the command line.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss