From: Mark Butcher <M_J_BUTCHER@compuserve.com>
To: Peter Barada <pbarada@mail.wm.sps.mot.com>
Cc: gcc <gcc@gcc.gnu.org>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Tutorial 4
Date: Wed, 26 Jun 2002 14:58:00 -0000 [thread overview]
Message-ID: <200206261758_MC3-1-400-70FA@compuserve.com> (raw)
Hi Peter
Thanks for your comments. In fact I have got into the habit of trashing
everything before trying a build - yesterday I completely deleted all build
file and the tool directories (like a fresh install) and the error was
identical - this on two differenct computers (using cygwin shell - under
Windows 98 and Window NT).
It looks as though we are more or less in agreement that the build method
is basically correct and like you, being a pure c-programmer (with just a
little c++ experience) it means studying the language some more to
understand the problem.
I would be very interested to know whether the scrips works in a Linux
environment ! It would certainly be interesting if there are some
environment dependencies.
In the meantime I'll get my head down in my "Now I'm going to learn C++
book"...... (just noticed I took it in to the office so it will have to
wait until tomorrow).
Cheers
Mark
PS. I read your posting where you seem to have had an identical problem -
did you not have any response which may aid understanding the root-cause ?
next reply other threads:[~2002-06-26 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 14:58 Mark Butcher [this message]
2002-06-26 15:50 ` Peter Barada
-- strict thread matches above, loose matches on Subject: below --
2002-06-25 15:49 Mark Butcher
2002-06-26 7:55 ` Peter Barada
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=200206261758_MC3-1-400-70FA@compuserve.com \
--to=m_j_butcher@compuserve.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=pbarada@mail.wm.sps.mot.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).