From: "jerryc@innerpeace.org" <jerryc@innerpeace.org>
To: linux-8086@vger.kernel.org
Subject: Re: compiler for ELKS programs
Date: Sun, 19 Jan 2003 22:21:53 -0500 [thread overview]
Message-ID: <3E2B6B51.2030403@innerpeace.org> (raw)
In-Reply-To: MJEMLGHNOJPHGGILAOEBMELMCGAA.neil.holmes@zoom.co.uk
Dear Neil,
I've read that page over several times, and there was some info about
compiling ELKS itself. However, if it does say what to use to compile
software to run on ELKS, I couldn't find it. Would you be so kind as to
humor a newbie to C and ELKS and copy and paste in the paragraph or two
that has it, and I'll forward it to my local LUG friends to explain it
for me if I can't understand it?
Thanks for your help.
Yours in peace,
Jerry
Neil Holmes wrote:
> The compiler required for ELKS is documented on the ELKS web site. See the
> FAQ section at :-
>
> http://elks.sourceforge.net
>
> Neil
>
> -----Original Message-----
> From: linux-8086-owner@vger.kernel.org
> [mailto:linux-8086-owner@vger.kernel.org]On Behalf Of
> jerryc@innerpeace.org
> Sent: 19 January 2003 06:49
> To: linux-8086@vger.kernel.org
> Subject: compiler for ELKS programs
>
>
> Greetings,
>
> Inspired by the feedback I have gotten from this list and my local LUG,
> I am learning to program C and use the curses / ncurses libraries. This
> seems like the best approach for putting Inner Peace on 8086's.
>
> I read somewhere that ELKS itself does not have a compiler. If that's
> true, the code would have to be compiled on another computer, which
> should not be a problem. Some of what I'm reading refers to different
> coding styles for different compilers.
>
> So, here are the relevant questions:
>
> Does ELKS have a compiler?
> If not, is there a compiler that will compile programs properly to run
> on ELKS?
> If so, what kind of coding styles are needed?
>
> Any other help and suggestions would be appreciated.
>
> Thanks again for all your support for an ELKS and C newbie.
>
> Yours in peace,
>
> Jerry
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2003-01-20 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 6:48 compiler for ELKS programs jerryc
2003-01-19 8:20 ` Neil Holmes
2003-01-20 3:21 ` jerryc [this message]
2003-01-20 6:43 ` Neil Holmes
2003-01-20 8:51 ` Paul Nasrat
2003-01-20 12:41 ` jb1
-- strict thread matches above, loose matches on Subject: below --
2003-01-20 11:48 jerryc
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=3E2B6B51.2030403@innerpeace.org \
--to=jerryc@innerpeace.org \
--cc=linux-8086@vger.kernel.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