From: Charles Terry <cterry AT plinet DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE Weirdness
Date: Thu, 09 Apr 1998 05:53:27 -0700
Organization: All USENET -- http://www.Supernews.com
Lines: 53
Message-ID: <352CC4C7.653C@plinet.com>
References: <DIBAFJALMNGEAAAA AT mailexcite DOT com>
NNTP-Posting-Host: 23442 AT 207 DOT 174 DOT 3 DOT 221
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Sed Johnson wrote:
> 
> (sorry if this is a duplicate of a previous message,
>   I'm not sure if it sent before)
> 
> I was able to resolve some of the linking errors
> I was getting from RHIDE before, but now something
> really weird is happening.
> 
> My project is all together all nice... all directories
> (including object directories) specified and
> everything.  I go to compile my project... everything
> compiles fine... RHIDE goes to link my project and
> gives me a whacky error, such as:
> 
> Creating: program.exe
> Error: gcc.exe: myfunc: No such file or directory (ENOENT)
> There were some errors
> 
> This MIGHT be understandable, except that I don't
> have any "myfunc" file in my project.  Nor
> do I have a "myfunc.cc".  I DO have a "myfuncs.cc"
> though.  What is odd is that when RHIDE goes
> to link my project, this file often changes to
> some other (seemingly RANDOM) file in my project,
> truncated of course, and the linker bombs out.
> 
> Now want to hear something really weird?  I go to
> write a makefile for my project, exit out of RHIDE,
> run MAKE on the makefile RHIDE created, and it compiles
> AND links perfectly!   What is up with that?
> 
> I have 13 ".cc" files in my project.
> 

What did you do to correct the previous errors you were getting.
In responce to the Email lstdcx is the C++ library that rhide
automatically links in with files with a .cc extention.  
I don't know if I mentioned this in the previous reply but
you can go to options-compiler-command and prepend a -v to the
flags that rhide sends to gcc.  Then your output window will list 
everything that the compiler and linker are trying to do. I would
suggest you use the "build all" option in rhide and check what
files are being created, from and to where.  
Also in responce to the Email, the flags rhide uses are all warning
flags, none of them will result in a linker error.
If you post your replys to the newsgroup instead of my mail
the experts :-) here will be able to follow the thread and
add more than I can.

Good Luck
Charles