From: John Newlin <jnewlin@rawbw.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Contributing changes back to ECOS
Date: Wed, 29 Oct 2003 16:02:00 -0000 [thread overview]
Message-ID: <3F9FE49E.8040301@rawbw.com> (raw)
In-Reply-To: <000301c39e2d$f2c29060$81940050@portatile1>
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.
Thanks,
-John Newlin
--
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 16:02 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 ` John Newlin [this message]
2003-10-29 17:23 ` [ECOS] Contributing changes back to ECOS Andrew Lunn
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=3F9FE49E.8040301@rawbw.com \
--to=jnewlin@rawbw.com \
--cc=ecos-discuss@sources.redhat.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).