Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

rhide and Windows95

0 views
Skip to first unread message

Selfgovern

unread,
Jun 11, 1997, 3:00:00 AM6/11/97
to

I can't get rhide to compile anything in a Windows 95 DOS box. When I
open a .cpp file, and choose compile, it just dies. The only way to get
it back is to do a ctrl-alt-del and end the task.
If I use the -c option I can't see the files until I change the file
patern. Then when I can see the files and load one and try to compile, I
get a message that says Don't know how to build FILENAME.o from
c:/PATH/FILENAME.CPP.
(FILENAME and PATH are shown as an example...the case is the significance)
What now?

Dave D.

Dave Dawson

Democracy is two wolves and a lamb voting on lunch. Liberty is a well-armed lamb denying enforcement of the vote.

Robert Hoehne

unread,
Jun 12, 1997, 3:00:00 AM6/12/97
to Selfgovern

Selfgovern wrote:
>
> I can't get rhide to compile anything in a Windows 95 DOS box. When I
> open a .cpp file, and choose compile, it just dies. The only way to get
> it back is to do a ctrl-alt-del and end the task.
What version of RHIDE you are using? Or better, post the bug-report
generated by RHIDE (look in the leftmost menu).

> c:/PATH/FILENAME.CPP


> (FILENAME and PATH are shown as an example...the case is the significance)
> What now?

Rename it to lower cases. RHIDE (and gcc) choose the right compiler
depending on the suffix, and .CPP is not a known suffix to be a source
file (this is in the RHIDE doc already for a long time).

Robert
--
*****************************************************************
* Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau *
* Post: Am Berg 3, D-09573 Dittmannsdorf *
* e-Mail: Robert...@Mathematik.TU-Chemnitz.DE *
* WWW: http://www.tu-chemnitz.de/~rho *
*****************************************************************

Salvador Eduardo Tropea (SET)

unread,
Jun 12, 1997, 3:00:00 AM6/12/97
to Selfgovern

selfg...@aol.com (Selfgovern) wrote:

> I can't get rhide to compile anything in a Windows 95 DOS box. When I
> open a .cpp file, and choose compile, it just dies. The only way to get
> it back is to do a ctrl-alt-del and end the task.

> If I use the -c option I can't see the files until I change the file
> patern. Then when I can see the files and load one and try to compile, I
> get a message that says Don't know how to build FILENAME.o from
> c:/PATH/FILENAME.CPP.

> (FILENAME and PATH are shown as an example...the case is the significance)
> What now?

Go to the menu (seems that you can do that) with ALT-SPACE and choose the Bug
Report option. Send the results to Robert.
Your situation is very strange. Are you using a new version of RHIDE?

SET
------------------------------------ 0 --------------------------------
Visit my home page: http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013

Selfg...@aol.com

unread,
Jun 12, 1997, 3:00:00 AM6/12/97
to salv...@inti.edu.ar

In a message dated 97-06-12 15:43:19 EDT, salv...@inti.edu.ar (Salvador
Eduardo Tropea (SET)) writes:

<< Send the results to Robert.
Your situation is very strange. Are you using a new version of RHIDE? >>

Version 1.3.

If this isn't going to the right person, could you please forward?

This is a bug report for RHIDE Version 1.3 (Jun 10 1997 09:23:28)
I am running MS-DOS 7.10 (Windows 95)

Important environment variables:
PATH=C:\BITWARE\;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\FP25;C:\DJGPP\BIN
DJGPP=c:/djgpp/djgpp.env
LFN=n
INFOPATH=c:/djgpp/info;c:/djgpp/gnu/emacs/info
LOCALEDIR=
LANGUAGE=
SHELL=
COMSPEC=C:\WINDOWS\COMMAND.COM
DJSYSFLAGS=

Here is the output from a sample compilation and link for C
Reading specs from c:/djgpp/lib\specs
gcc version 2.7.2.1
c:/djgpp/bin\cpp.exe -lang-c -v -undef -D__GNUC__=2 -D__GNUC_MINOR__=7
-Dunix -Di386 -DGO32 -DMSDOS -DDJGPP=2 -DDJGPP_MINOR=1 -D__unix__ -D__i386__
-D__GO32__ -D__MSDOS__ -D__DJGPP__=2 -D__DJGPP_MINOR__=1 -D__unix -D__i386
-D__GO32 -D__MSDOS -D__DJGPP=2 -D__DJGPP_MINOR=1 -
c:/djgpp/tmp/RHiaaaaa\ccbaaaaa
GNU CPP version 2.7.2.1 (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:
c:/djgpp/include
c:/djgpp/contrib/grx20/include
/usr/local/include
/usr/local/go32/include
/usr/local/lib/gcc-lib/go32/2.7.2.1/include
/usr/include
End of search list.
c:/djgpp/bin\cc1.exe c:/djgpp/tmp/RHiaaaaa\ccbaaaaa -quiet -dumpbase -.c
-version -o c:/djgpp/tmp/RHiaaaaa\cccaaaaa
GNU C version 2.7.2.1 (80386, BSD syntax) compiled by GNU C version 2.7.2.1.
c:/djgpp/bin\as.exe -v -o c:/djgpp/tmp/RHiaaaaa\ccdaaaaa
c:/djgpp/tmp/RHiaaaaa\cccaaaaa
GNU assembler version 2.7 (i386-go32-msdos)
c:/djgpp/bin\ld.exe -o /dev/null c:/djgpp/lib\crt0.o -Lc:/djgpp/lib -v
c:/djgpp/tmp/RHiaaaaa\ccdaaaaa -Tdjgpp.djl -lgcc -lc -lgcc
ld version 2.7 (with BFD 2.7)
c:/djgpp/bin\stubify.exe -v /dev/null
Warning: input file is not COFF or stubbed COFF
exe: No such file or directory (ENOENT)
stubify for djgpp V2.X executables, Copyright (C) 1995 DJ Delorie

End of the sample

Here is the output from a sample compilation and link for C++
Reading specs from c:/djgpp/lib\specs
gcc version 2.7.2.1
c:/djgpp/bin\cpp.exe -lang-c++ -v -undef -D__GNUC__=2 -D__GNUG__=2
-D__cplusplus -D__GNUC_MINOR__=7 -Dunix -Di386 -DGO32 -DMSDOS -DDJGPP=2
-DDJGPP_MINOR=1 -D__unix__ -D__i386__ -D__GO32__ -D__MSDOS__ -D__DJGPP__=2
-D__DJGPP_MINOR__=1 -D__unix -D__i386 -D__GO32 -D__MSDOS -D__DJGPP=2
-D__DJGPP_MINOR=1 - c:/djgpp/tmp/RHiaaaaa\ccbaaaaa
GNU CPP version 2.7.2.1 (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:
c:/djgpp/lang/cxx
c:/djgpp/include
c:/djgpp/contrib/grx20/include
/usr/local/lib/g++-include
/usr/local/include
/usr/local/go32/include
/usr/local/lib/gcc-lib/go32/2.7.2.1/include
/usr/include
End of search list.
c:/djgpp/bin\cc1plus.exe c:/djgpp/tmp/RHiaaaaa\ccbaaaaa -quiet -dumpbase
-.cc -version -o c:/djgpp/tmp/RHiaaaaa\cccaaaaa
GNU C++ version 2.7.2.1 (80386, BSD syntax) compiled by GNU C version
2.7.2.1.
c:/djgpp/bin\as.exe -v -o c:/djgpp/tmp/RHiaaaaa\ccdaaaaa
c:/djgpp/tmp/RHiaaaaa\cccaaaaa
GNU assembler version 2.7 (i386-go32-msdos)
c:/djgpp/bin\ld.exe -o /dev/null c:/djgpp/lib\crt0.o -Lc:/djgpp/lib -v
c:/djgpp/tmp/RHiaaaaa\ccdaaaaa -Tdjgpp.djl -lgcc -lc -lgcc
ld version 2.7 (with BFD 2.7)
c:/djgpp/bin\stubify.exe -v /dev/null
Warning: input file is not COFF or stubbed COFF
exe: No such file or directory (ENOENT)
stubify for djgpp V2.X executables, Copyright (C) 1995 DJ Delorie

End of the sample

My problem is the following:
============================

I can't get RHIDE to compile anything in a Windows95 DOS Box.
When I open a .cpp file and choose compile, it just dies. The
only to get it back is the do a ctrl-alt-del and end the task.
If I use the -c option, I can't see the files until I change
the file pattern to [CP]. I can then see the files (in all upper case)


and can load one and choose compile. I then get an error that says:
Don't know how to build FILENAME.o from c:/PATH/FILENAME.CPP.

(The FILENAME and PATH are shown as an example...the case is the
significance.)

Dave Dawson

The liberty of the individual is no gift of civilization. It was greatest
before there was any civilization.
Sigmund Freud (1856-1939)

Smith A. Cat

unread,
Jun 12, 1997, 3:00:00 AM6/12/97
to

Selfg...@aol.com wrote:

> I can't get RHIDE to compile anything in a Windows95 DOS Box.


windoze95 flatters itself, calling that thing a DOS box.

anyway, have you tried "manually" compiling anything, from the "DOS
(aaaarrrggghhh, there it is again...)" prompt that is?? at least then
you'll know whether it's RHIDE or your paths, system, whatever.

have you tried CygWin32?? (i think that's the name anyway, it's the GCC
for Win95/NT).

DOS 7.10? hahahahahahahahahahahahahahahahahahahahahaha...

phil


Mr. Th

unread,
Jun 13, 1997, 3:00:00 AM6/13/97
to

> Selfgovern wrote:
> >
> > I can't get rhide to compile anything in a Windows 95 DOS box. When I
> > open a .cpp file, and choose compile, it just dies. The only way to get
> > it back is to do a ctrl-alt-del and end the task.

It does the same to me. Usually I just do alt-enter and turn it
into the full screen before I do stuff. I only switch back to a dos
window when the mouse cursor does its disappearing act and I need to
select a window for some reason. You always have to switch back to full
screen, though, or it'll screw up.

Philip Hindman

unread,
Jun 13, 1997, 3:00:00 AM6/13/97
to
This seems to be a problem with Rhide 1.3
I am having the same problem using DOS 6.22, and am receiving the same
behavior. Try using .cc extensions instead of .cpp extensions and
everything should work fine for now(it does with me). I have talked
to Robert Hoehne about it and he it working on it. See the thread
"RHIDE v1.3 Possible Bug"

Paul Derbyshire

unread,
Jun 14, 1997, 3:00:00 AM6/14/97
to


Microsoft uses void main? Now why am I not surprised? :)

--
.*. Where feelings are concerned, answers are rarely simple [GeneDeWeese]
-() < When I go to the theater, I always go straight to the "bag and mix"
`*' bulk candy section...because variety is the spice of life... [me]
Paul Derbyshire ao...@freenet.carleton.ca, http://chat.carleton.ca/~pderbysh

0 new messages