From: Andrew Lunn <andrew@lunn.ch>
To: John Newlin <jnewlin@rawbw.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Contributing changes back to ECOS
Date: Wed, 29 Oct 2003 17:23:00 -0000 [thread overview]
Message-ID: <20031029172040.GA7717@lunn.ch> (raw)
In-Reply-To: <3F9FE49E.8040301@rawbw.com>
On Wed, Oct 29, 2003 at 08:02:38AM -0800, John Newlin wrote:
> I'm not using GCC as the compiler for my architecture. I made a small
> change to ecosconfig to read in a new global option that sets CC in all
> the makefiles. I doubt this is useful to many people, but I'd be happy
> to make patch files and send them in, just not sure the correct place.
I think people would be more interesting in knowning your experiance
of using something other than gcc. This is not easy to do.
What compiler are you using. How are you doing constructor
prioritization etc.
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-10-29 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 15:04 [ECOS] hal_virt_to_phys_address() Oscar
2003-10-29 16:02 ` [ECOS] Contributing changes back to ECOS John Newlin
2003-10-29 17:23 ` Andrew Lunn [this message]
2003-10-29 18:17 ` John Newlin
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=20031029172040.GA7717@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=jnewlin@rawbw.com \
/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).