From: "John R. Dunning" <jrd@jrd.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "John R. Dunning" <jrd@jrd.org>, ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Using a different toolchain
Date: Tue, 04 Apr 2006 14:12:00 -0000 [thread overview]
Message-ID: <17458.32425.140166.137040@kong.jrd.org> (raw)
In-Reply-To: <20060404131647.GA4499@lunn.ch>
From: Andrew Lunn <andrew@lunn.ch>
Date: Tue, 4 Apr 2006 15:16:47 +0200
You want to change CYGBLD_GLOBAL_COMMAND_PREFIX
Ok, tnx.
What is wrong with the linker script eCos generates? Since you are
still using gcc and i assume you are still using binutils,
Yes.
i would of
thought target.ld would work.
Well, I dunno; I may just be not looking at the right thing. I'm
trying to use what amounts to a 64-bit mips toolchain (it's a mips
instruction set, with some extra hacks added to it for custom
hardware) so I started with the 32-bit stuff, got that to build ok,
then tried swapping in the 64-bit stuff. The 64-bit linker barfed on
the references to elf32-littlemips in target.ld, so I tried changing
them to what I thought were equivalent 64-bit things, but that didn't
work either. I tried using the linker script that I use for other
(non-ecos) binaries on this platform, and that said it built an
executable, but when I objdump it, there's nothing in .text.
Perhaps I need to go off and read up on linker scripts, because my
non-ecos one bears approximately zero resemblance to the ecos one, and
I can intuit only vaguely what either one of them are doing :-{
--
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 14:12 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
2006-04-04 14:12 ` John R. Dunning [this message]
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=17458.32425.140166.137040@kong.jrd.org \
--to=jrd@jrd.org \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@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).