Linkerscript

Linkerscript

[Meulendijks, J.]

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.

Thanks in advance.

Re: Linkerscript

[Ian Lance Taylor]

"Meulendijks, J." <Meulendijks@WT.TNO.NL> writes:

> I read the following on the internet:

Well, there you go.  You can't trust 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.

This is not a gcc question.  ld is part of the binutils.  For binutils
help, see http://sourceware.org/binutils/

In a linker script, using data.o within a SECTIONS command tells the
linker what to do with data.o, but it doesn't tell the linker to
actually use data.o.  Putting INPUT(data.o) in your linker script will
probably do what you want.  See the linker manual for more
information.

Ian