public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Charles Nelson <araes@pangeatech.com>
To: Harald Lüning <harald.luning@erv.ericsson.se>
Cc: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Re: Building gcc-2.95.2 for NT (win32)
Date: Thu, 02 Dec 1999 17:56:00 -0000	[thread overview]
Message-ID: <3847255A.B603D3B3@pangeatech.com> (raw)
In-Reply-To: <2DADC88F8F19D31193340090277A36617FF3A7@esegsnt003.erv.ericsson.se>

Hi Harald,
I have had this same problem and if you look at the 1st line in the
'configure' file you will notice that it reads '# !/bin/sh',  this line
and other lines like it are the cause of many wasted hours for those of
us forced to a standard computer system (namely a Wintel machine).  The
easiest solution is to create a sub-directory call 'bin' and copy
'sh.exe' into it.  It really seems that if you want to take advantage of
the power and benefits that GNU provides, then we "NT" users must
ultimately do all the work of porting and configuration ourselves. If you
want to make your life easy in the GNU world, then get and learn to use a
Unix type system.  Good Luck!

--
-------------------------------------------------------------
Charles L. Nelson
Embedded Systems Architect
ARAES(tm)
Applications Research And Engineering Services
-------------------------------------------------------------
> Where Technical Ideas Become Practical Products <


WARNING: multiple messages have this Message-ID

From: Charles Nelson <araes@pangeatech.com>
To: Harald Lüning <harald.luning@erv.ericsson.se>
Cc: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Re: Building gcc-2.95.2 for NT (win32)
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <3847255A.B603D3B3@pangeatech.com> (raw)
Message-ID: <19991231222400.PH33kdDvMzOLy_ozuMbEKss-SNczc-KeU8IXplk8JhU@z> (raw)
In-Reply-To: <2DADC88F8F19D31193340090277A36617FF3A7@esegsnt003.erv.ericsson.se>

Hi Harald,
I have had this same problem and if you look at the 1st line in the
'configure' file you will notice that it reads '# !/bin/sh',  this line
and other lines like it are the cause of many wasted hours for those of
us forced to a standard computer system (namely a Wintel machine).  The
easiest solution is to create a sub-directory call 'bin' and copy
'sh.exe' into it.  It really seems that if you want to take advantage of
the power and benefits that GNU provides, then we "NT" users must
ultimately do all the work of porting and configuration ourselves. If you
want to make your life easy in the GNU world, then get and learn to use a
Unix type system.  Good Luck!

--
-------------------------------------------------------------
Charles L. Nelson
Embedded Systems Architect
ARAES(tm)
Applications Research And Engineering Services
-------------------------------------------------------------
> Where Technical Ideas Become Practical Products <


  reply	other threads:[~1999-12-02 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-02  8:36 Harald Lüning
1999-12-02 17:56 ` Charles Nelson [this message]
1999-12-31 22:24   ` Charles Nelson
1999-12-31 22:24 ` Harald Lüning

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=3847255A.B603D3B3@pangeatech.com \
    --to=araes@pangeatech.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=harald.luning@erv.ericsson.se \
    /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).