Xref: utzoo comp.lang.c++:5452 comp.sys.hp:3412
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!snorkelwacker!mit-eddie!mit-amt!peter
From: peter@mit-amt.MEDIA.MIT.EDU (Peter Schroeder)
Newsgroups: comp.lang.c++,comp.sys.hp
Subject: problems building cfront 2.0
Keywords: C++,cfront2.0,HP9000/800,iostreams,static
Message-ID: <995@mit-amt.MEDIA.MIT.EDU>
Date: 10 Nov 89 00:48:43 GMT
Organization: MIT Media Lab, Cambridge, MA
Lines: 53

I just got 2.0 and started to put it on my HP9000/835. I was very happy
to see that this platform is supported now and the build went fine
(aside from a few little things).

Now however I find a rather puzzling problem.
Consider:

#include <iostream.h>

main()
{
   cout << "hello world\n";
}

and

#include <iostream.h>
#include <stdlib.h>

main()
{
   cout << "hello world\n";
   exit( 0 );    // <- this line makes all the difference
}

The first program does not print anything, the second program runs just
fine! I discovered this when trying to figure out why some of the demos
failed.

What is going on here? I used the debugger as best I could and found
that the initializer for the streams are called and the lshift function
does get the correct argument, calls the put function, but nothing gets
out... With the regular C debugger (xdb) I can't go any further than
that since it does not understand C++.

Also, there are a few changes that I would suggest for building this
beast on HP9000/800. Who at AT&T and HP is interested in hearing about this?
(specifically generic.h needs a change for the token pasting)

If you are an HP compiler wizard, would you get in touch with me?
There are a bunch of files which the compiler croaks on with -O2 but not
-O1. The C++ documentation from AT&T mentions this. Can something short
of handcompiling these files be done? Why does the compiler die? Do the
files need to be broken up? How about creative use of the +e[01] flags
when building cfront itself? I had a similar problem once on my own code
and `fixed' it by using the +e[01] flags.

Has anybody experienced similar problems? and found a fix????

Thanks for your help!

Peter
peter@media-lab.media.mit.edu