From: Mark Butcher <M_J_BUTCHER@compuserve.com>
To: Phil Edwards <phil@jaj.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Tutorial 3
Date: Tue, 18 Jun 2002 14:41:00 -0000 [thread overview]
Message-ID: <200206181740_MC3-1-2E1-A117@compuserve.com> (raw)
Hi Phil
Thanks for your notes.
I am also sure that the problem is due to not finding some headers and
library files. In the mean time I believe that I have managed to
successfully build NEWLIB and am quite sure that the (previously really)
missing items are present (mcore-elf-gcc.exe is now there, crt0.o is now
there and libraries like libc.a).
Although the full gcc build still failed for the same reason, it must be
something silly and so probably even I can fix it - given a little more
time.
I'm looking forward to posting details of my successful build for the mcore
soon, with a list of exactly what to type in to get it working - for any
other Windows Cygwin Dummies out there.
Cheers
Mark
next reply other threads:[~2002-06-18 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 14:41 Mark Butcher [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-18 14:41 Mark Butcher
2002-06-18 16:56 ` Hans-Peter Nilsson
2002-06-19 14:01 ` Peter Barada
2002-06-16 15:42 Mark Butcher
2002-06-17 1:57 ` Andrew Haley
2002-06-17 9:31 ` Peter Barada
2002-06-17 13:25 ` Phil Edwards
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=200206181740_MC3-1-2E1-A117@compuserve.com \
--to=m_j_butcher@compuserve.com \
--cc=gcc-help@gcc.gnu.org \
--cc=phil@jaj.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).