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:07:00 -0000	[thread overview]
Message-ID: <38B53518-83B4-47A6-A64D-FC8266DB0602@wh2.tu-dresden.de> (raw)
In-Reply-To: <20080618095232.GA10893@lunn.ch>

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

>> Does anybody have a hint for me ? How can I get the code linked  
>> when it
>> is in platform.S ?
>
> The dependancy rules don't always work for some special files, eg
> vectors.S. However, if the object file is getting into libtarget.a, it
> should all work. The only exception would be if nothing actually uses
> symbols you added, then the linker is expected not to link your
> code....

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.

> Is this really reproducible? If you rm -fr your work tree and build
> everything from clean, can you reproduce the problem?

Yes, I can reproduce it. Just now it did 2 tests:

rm -rf *
ecosconfig new skmb91302 redboot
ecosconfig tree
make

Code is in when it is in variant.S, after that the same procedure with  
the code in platform.S and the code is not there.

Lars

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

  reply	other threads:[~2008-06-18 10:07 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 [this message]
2008-06-18 10:23     ` Andrew Lunn
2008-06-18 10:58       ` Lars Poeschel
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=38B53518-83B4-47A6-A64D-FC8266DB0602@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).