Date: Sat, 10 Oct 1998 16:39:02 +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: <361F6273.3E80@erols.com>
Message-ID: <Pine.OSF.4.05.9810101632590.20988-100000@sable.ox.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com

On Sat, 10 Oct 1998 dannys AT erols DOT com wrote:

> Sorry if this request is too specific...

No request can be too specific -- it's vague requests that are
hard to answer.

> I ran the check under instruction # 2.4 (go32-v2) and got the following:
> 
> go32/v2 version 2.0 built Jan 23 1996 22:03:02
> Usage: go32 coff-image [args]
> Rename this to go32.exe only if you need a go32 that can run v2 binaries
> as well as v1 binaries (old makefiles). Put ahead of the old go32 in
> your path.
> DPMI memory available: 40272 Kb
> DPMI swap space available: 22332 Kb
> 
> Am I correct in assuming that this means that the compiler is installed
> okay? 

It implies that some things are OK.  If you didn't need to go to
djgpp's `bin' directory to do this then your path is correct.
If you did need to, then your path is not correct.

> I copied the sample files to c:\whos.
> 
> Then I tried to compile itemtst1 and got a slew of Bad command or file
> name messages scrolling down and then a bunch of lines referring to
> itemtst1.cc: follwed by a number, 0, 7, 10, etc and then "undefined
> reference to 'StockItem: :Display and other similar messages to numerous
> to list here. and then finally I end up with the prompt C:\whos\normal>.
> 
> Obviously something is wrong. Can you help please? 

Please post the output of the `set' command at a DOS prompt,
i.e. do this:

    set > set.txt

and post the text file.  Also post your autoexec.bat, and say
the exact path to where djgpp is installed (the path to
`djgpp.env').  In addition, go to your djgpp `manifest'
directory and type this:

    dir /b *.mft > manifest.txt

Post that file too.

Finally, tell us exactly what you typed to compile that program.
If you ran a batch file, tell us exactly what the batch file
says.  Also post all the error messages produced.  The simplest
way to do this is instead of calling:

    gcc .....

call this:

    redir -o output.txt -eo gcc -v .....

`-v' means to give more information about what gcc is doing.
When you perform this command you won't see the output on the
screen, but you can read it in `output.txt'.  Please include
that file in your next posting too.

-- 
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