From: Ben Dougall <bend@freenet.co.uk>
To: gcc-help@gcc.gnu.org
Subject: Re: embedding gcc?
Date: Wed, 11 Dec 2002 08:37:00 -0000 [thread overview]
Message-ID: <D16E69F0-0D26-11D7-8BB7-0030653F9ECE@freenet.co.uk> (raw)
In-Reply-To: <583E84A77A2FCB4F967E6CD9B0CA4AF71BD028@nt-server.kreuter>
On Tuesday, December 10, 2002, at 08:05 pm, Buddy Lott wrote:
> Why not build your installation script to installation software so that
> it will install your code and GCC?
Yeah, I think you're right.
I was envisaging maybe only needing and using particular parts of GCC,
so only including and using a stripped down version of it, but using
GCC as it is, will probably save untold amounts of work and time. So
your suggestion is probably the best way to do it. Thanks very much.
next parent reply other threads:[~2002-12-11 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <583E84A77A2FCB4F967E6CD9B0CA4AF71BD028@nt-server.kreuter>
2002-12-11 8:37 ` Ben Dougall [this message]
2002-12-11 9:54 ` Buddy Lott
[not found] <1039456162.9884.ezmlm@gcc.gnu.org>
2002-12-09 12:28 ` Ben Dougall
2002-12-09 18:13 ` Gokhan Kisacikoglu
2002-12-10 6:18 ` Ben Dougall
2002-12-07 4:19 Ben Dougall
2002-12-07 5:02 ` bjorn rohde jensen
2002-12-08 11:59 ` Andrea 'fwyzard' Bocci
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=D16E69F0-0D26-11D7-8BB7-0030653F9ECE@freenet.co.uk \
--to=bend@freenet.co.uk \
--cc=gcc-help@gcc.gnu.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).