[gnu.g++] Interviews with G++

gleicher@CS.CMU.EDU (Michael Gleicher) (11/19/89)

I'm sorry if these questions have been asked/answered 1000s of times, but I
really can't seem to figure them out. Some of them may have more to do with
the fact that after several times through the documentation, I still have no
idea how to get imake to do what I want it to.

What is the correct way to tell the "imake" system that I want to use g++
instead of CC? The only way I was able to figure it out was to link CC in the
InterViews bin directory to g++.

Are there fixes to make it so that interviews will compile under g++? Right
now I get errors and warning messages.

Is there a better version to get than the 2.5.tar.Z on
interviews.stanford.edu? 

Why does the make system (while doing dependency generation) have problems
finding rstat.h? It's right there in the InterViews source directories.
(is rstat also a SunOs thing? I'm actually running Mach so rstat.h does not
exist in /usr/include)

Can I somehow tell the make files that the X11 includes and libraries are not
in the normal place?

I appreciate any and all help. I really would like to check out interviews,
but the agnony of setting it up is starting to appear prohibitive.

Thanks,

Mike

Michael Lee Gleicher					gleicher@cs.cmu.edu
	    ski bum, graphics hacker, and SCS PhD student
Carnegie Mellon University, Pittsburgh, PA 15213-3890	(412) CMU-STYX (school)



--
Michael Lee Gleicher					gleicher@cs.cmu.edu
	    ski bum, graphics hacker, and SCS PhD student
Carnegie Mellon University, Pittsburgh, PA 15213-3890	(412) CMU-STYX (school)

interran@lurch.Stanford.EDU (John Interrante) (11/19/89)

 > What is the correct way to tell the "imake" system that I want to use g++
 > instead of CC? The only way I was able to figure it out was to link CC in
 > the InterViews bin directory to g++.

What's wrong with that solution?  It works just as well as overriding
the appropriate configuration parameter.  Note that you can configure
CC to drive cc1plus (the GNU C++ compiler) instead of cfront; in fact,
pre-IV2.6 configures CC that way by default.  You don't have to use
g++ (the GNU C++ compiler driver) unless you want something from g++
that CC won't give you (like automatically linking with libgnulib.a).

 > Are there fixes to make it so that interviews will compile under g++? Right
 > now I get errors and warning messages.

Get pre-IV2.6, g++ 1.36.1, and gcc 1.36.  You'll be much better off
with pre-IV2.6 than IV2.5 since pre-IV2.6 includes some fixes we
didn't bother distributing.  You'll find pre-IV2.6 in
iv-snapshot.tar.Z on interviews.stanford.edu.  You'll have to get g++
1.36.1 separately.  Labrea.stanford.edu and prep.ai.mit.edu have
copies.  Don't forget to get gcc 1.36 too if you don't have it.  Or
wait a couple of weeks for Mark Linton to finish documenting the
changes and officially release IV2.6.  The official release will
package all three programs together so that you can simply say "make"
in the top directory to make everything.

 > Why does the make system (while doing dependency generation) have problems
 > finding rstat.h? It's right there in the InterViews source directories.
 > (is rstat also a SunOs thing? I'm actually running Mach so rstat.h does not
 > exist in /usr/include)

You need both our rstat.h and the system rstat.h because our rstat.h
simply includes the system rstat.h within an extern "C" wrapper.
Forget about making whatever program that uses rstat.h compile - you
wouldn't have been able to link it anyway since we don't have source
for the functions declared in rstat.h.

 > Can I somehow tell the make files that the X11 includes and libraries are
 > not in the normal place?

Yes you can, but why don't you make life easier for everybody by
installing the X11 includes and libraries in the standard places?
Remember that a symbolic link is as good as an actual directory if
you're short of disk space in /usr.  Read iv/src/config/README; it'll
mention the configuration parameters that tell the make files where to
find the X11 includes and libraries.

Please send any further problems to interviews-bugs@interviews.stanford.edu.

		John