From: Andrew Lunn <andrew@lunn.ch>
To: "John R. Dunning" <jrd@jrd.org>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Using a different toolchain
Date: Tue, 04 Apr 2006 13:17:00 -0000 [thread overview]
Message-ID: <20060404131647.GA4499@lunn.ch> (raw)
In-Reply-To: <17458.28456.147803.714504@kong.jrd.org>
On Tue, Apr 04, 2006 at 09:05:44AM -0400, John R. Dunning wrote:
> Hi all. I'm trying to find hints on how to get ecos to build using a
> non-stock toolchain. It's gcc, but not one of the canned ones that
> comes with ecos.
>
> First, is there a way to convince ecosconfig and friends to generate a
> different tool prefix in the makefiles? It seemed like it was
> designed for that, but I couldn't find it. If not, it's no big deal,
> I can tweak the makefiles after generation.
You want to change CYGBLD_GLOBAL_COMMAND_PREFIX
> Second, is there documentation on what sections and other
> constructions are required in the linker script? I tried using a
> linker script from another (non-ecos) project, but that failed
> miserably. I have the impression that the script I'm using just
> doesn't have enough in it, but I don't speak ld well enough to know
> what I'm missing. Do I just need to go read up on that stuff in order
> to get my linker script right?
What is wrong with the linker script eCos generates? Since you are
still using gcc and i assume you are still using binutils, i would of
thought target.ld would work.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-04-04 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 13:05 John R. Dunning
2006-04-04 13:17 ` Andrew Lunn [this message]
2006-04-04 14:12 ` John R. Dunning
2006-04-06 3:11 ` John R. Dunning
2006-04-06 3:38 ` [ECOS] " Grant Edwards
2006-04-06 6:39 ` [ECOS] " Andrew Lunn
2006-04-04 14:23 ` [ECOS] " Grant Edwards
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=20060404131647.GA4499@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jrd@jrd.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).