www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/10/11/11:46:48

Date: Sun, 11 Oct 1998 16:44:48 +0100 (BST)
From: George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
To: djgpp AT delorie DOT com
Subject: Re: Please: Newbie and "Who's Afraid of C++" needs help w/djgpp
In-Reply-To: <3620A82D.62C8@erols.com>
Message-ID: <Pine.OSF.4.05.9810111638090.22222-100000@sable.ox.ac.uk>
MIME-Version: 1.0
Reply-To: djgpp AT delorie DOT com

On Sun, 11 Oct 1998 dannys AT erols DOT com wrote:

> > OK, that's an old djgpp -- version 2.00.  The latest is version
> > 2.01.  But still, as far as I can see the packages you have
> > should be compatible with each other.
> 
> Should I update to 2.01 or stick with what I already have? I don't want
> to introduce any more variables unecessarily at this point. Just want to
> get up and running with learning.

It's up to you.  DJGPP v1 is certainly not `supported' any more
(although people will still help if they can).  There are
problems when you mix v2.00 binaries with v2.01 binaries, so
using v2.00 means that you can't use any newer packages.  If you
want to upgrade anything, you'll have to upgrade everything.

I don't think upgrading will affect the functionality enough to
make what the book tells you wrong.  In other words, everything
in the book ought to still work after you upgrade.

> > > c:\whos\normal>redir -o output.txt -eo gcc -v mk itemtst1
> > 
> > It's wrong.  
> 
> Do you mean that I entered it under the wrong directory or what?

No, the problem is in the way `redir' works.  It's a command
that redirects input and output in a more sophisticated way than
comamnd.com can do itself.  The first few options (up to and
including `-eo') are instructions to tell it what to do, and the
rest of the command line is just a command for it to execute.
In the above example, you've told it to send output to
`output.txt', and send errors to wherever output is going (i.e.
`output.txt' also), and then execute "gcc -v mk itemtst1".  This
last command is nonsense; gcc is the compiler, it doesn't know
what to do with a batch file (hence all the `file not found'
errors).

> Thanks George. I did all of the above and the compilation seemed not to
> work. ie hello.exe was not created. Output.txt reads as follows:
> 
> gcc.exe: hello.c: No such file or directory (ENOENT)
> Reading specs from c:/djgpp/lib\specs
> gcc.exe: unrecognized option `-02'
> gcc version 2.7.2

Sorry, that should have been a capital O, not the number 0.  Try
again.

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk

xu do tavla fo la lojban  --  http://xiron.pc.helsinki.fi/lojban/lojban.html

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019