From: Michael Witten <mfwitten@MIT.EDU>
To: Brian Dessent <brian@dessent.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: [Progress] Tiny GCC: Pure, Unadulterated, Object Code
Date: Sat, 26 Jan 2008 16:17:00 -0000 [thread overview]
Message-ID: <C28A2552-FFB1-4674-9A1F-787ADD54BDD0@mit.edu> (raw)
In-Reply-To: <83DE5DDC-09DE-4C4A-92E5-8ED60D9375A1@MIT.EDU>
On 25 Jan 2008, at 8:16 AM, Michael Witten wrote:
> On 24 Jan 2008, at 7:20 AM, Brian Dessent wrote:
>
>> Michael Witten wrote:
>>
>>> Can I build gcc in this way?
>>>
>>> I've been trying for quite some time now to achieve such a
>>> stripped down gcc, but it would seem that the gcc build
>>> process insists on building these libraries, which I think
>>> is wholly unnecessary.
>>
>> You might be able to approximate this by "make all-gcc" and then
>> "make
>> install-gcc" (or just manually copying the xgcc to the destination.)
>
> I'm a little uncomfortable just taking the xgcc that's left over when
> the build fails.
I apologize.
For some reason, when I tried
make all-gcc
the build failed.
After getting a good night's rest and starting afresh,
I was able to build a 'naked' gcc using --without-headers,
a non-linux target, and your above suggestion.
That being said, part of the problem is that the build process
is neither well-documented nor intuitive--at least to me.
While I would love to contribute by improving this factor of gcc,
I would rather encourage somebody, who has an intimate familiarity
with the project, to take the time over a couple of weekends to
clarify the nuances and produce step-by-step (shell) instructions
for not only common tasks, but also the uncommon tasks; there's no
reason that this information should be hosted by other websites:
http://www.osdev.org/wiki/GCC_Cross-Compiler
That kind of documentation could go a long way in encouraging new
developers to get involved, because it would allow them to avoid
a first impression wrought with frustration.
Sincerely,
Michael Witten
next prev parent reply other threads:[~2008-01-25 23:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 12:21 Michael Witten
2008-01-24 14:29 ` Ian Lance Taylor
2008-01-25 4:23 ` Brian Dessent
2008-01-26 2:47 ` Michael Witten
2008-01-26 16:17 ` Michael Witten [this message]
2008-01-26 22:16 ` [Progress] " Michael Witten
2008-01-28 0:46 ` Andrew Haley
2008-01-27 13:07 ` Michael Witten
2008-01-27 8:45 ` Brian Dessent
2008-01-29 1:36 ` Scott Moore
2008-01-29 15:55 ` Michael Witten
2008-01-29 16:56 ` Brian Dessent
2008-01-29 18:16 ` Michael Witten
2008-01-29 18:36 ` Brian Dessent
2008-01-29 20:31 ` Michael Witten
2008-01-30 1:14 ` NightStrike
2008-01-30 7:09 ` Michael Witten
2008-01-30 10:20 ` Ian Lance Taylor
2008-01-30 10:54 ` Michael Witten
2008-01-30 12:09 ` Ian Lance Taylor
2008-01-29 14:22 ` John Carter
2008-01-29 15:40 ` Michael Witten
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=C28A2552-FFB1-4674-9A1F-787ADD54BDD0@mit.edu \
--to=mfwitten@mit.edu \
--cc=brian@dessent.net \
--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).