This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Using a different toolchain
- From: Andrew Lunn <andrew at lunn dot ch>
- To: "John R. Dunning" <jrd at jrd dot org>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Tue, 4 Apr 2006 15:16:47 +0200
- Subject: Re: [ECOS] Using a different toolchain
- References: <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