public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Lars Poeschel <larsi@wh2.tu-dresden.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: Strange buildsystem behaviour
Date: Wed, 18 Jun 2008 10:58:00 -0000	[thread overview]
Message-ID: <136E7846-7252-43D7-A7A4-02ED213ADFF8@wh2.tu-dresden.de> (raw)
In-Reply-To: <20080618102248.GB10893@lunn.ch>

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]


Am 18.06.2008 um 12:22 schrieb Andrew Lunn:

>> I read about this and added a KEEP() around the regarding input
>> sections, but it should not matter in this case, because for the
>> variant.S file it works.
>
> Im not sure this is true. I guess the KEEP() will only help if the
> object file is loaded. If no symbols in the file are referenced, it
> never loads the file and so never knows it needs to keep anything.

YES!
Thanks Andrew this was the solution!
variant.S had some other symbol that was referenced but platform.S did  
not have this symbol. If I make a "dummy" reference to the new code in  
platform.S from somewhere else gets included.

Thanks again!

Lars


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  reply	other threads:[~2008-06-18 10:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18  9:36 Lars Poeschel
2008-06-18  9:53 ` Andrew Lunn
2008-06-18 10:07   ` Lars Poeschel
2008-06-18 10:23     ` Andrew Lunn
2008-06-18 10:58       ` Lars Poeschel [this message]
2008-06-18 16:26         ` Partition support for FAT file system Frank Pagliughi
2008-06-18 16:44           ` Nick Garnett
2008-06-18 17:01             ` Frank Pagliughi
2008-06-18 19:26               ` Nick Garnett
2008-06-20 13:56                 ` Frank Pagliughi
2008-06-18 19:28               ` Frank Pagliughi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=136E7846-7252-43D7-A7A4-02ED213ADFF8@wh2.tu-dresden.de \
    --to=larsi@wh2.tu-dresden.de \
    --cc=andrew@lunn.ch \
    --cc=ecos-devel@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).