I am experiencing something alike on my pmax; I am trying the brave
experiment of making KDE for the pmax (I believe it will look pretty
ugly on my monochrome screen if I can get it working but...)

The first evident problem comes when making the QT package from the
package system.

The first trouble I got was that the compile stopped several places, it
seemed like the patches from pkgsrc had failed horrobly (I am using
/etc/mk.conf to specify localbase and xbase and such).

After editing the makefiles so that they compile (including adding
-L/usr/lib and -ltermcap) the app fails. This app is moc of the
QT-system, which is just processing header files to produce moc_xxxx.cpp
files (no screen handling or magic).

I am not experienced in debugging on NetBSD, but when I tried, gdb tells
me it gets SIGSEGV immediately when I use the run command, no code - it
is charmingly suggesting that it is a bug in gdb...

I also just upgraded to 1.3.2, and built my own kernel (without
problems).

I am about to dig into it now, but if there is an  easy clever answer; I
would appreciate getting it before I use too much time on it.

Regards,

Harald.

> -----Original Message-----
> From:	mjbedy [SMTP:mjbedy@Oakland.edu]
> Sent:	12. august 1998 16:48
> To:	port-pmax@netbsd.org
> Subject:	C++ compiler wackyness.
> 
>   Hi,
> 
>   I've got 1.3.2 installed on my 5000/125, and I am tring to compile a
> C++
> program, but even hello world fails to compile cleanly. This is a
> problem
> that has existed since 1.3-beta (i.e., it didn't just appear in
> 1.3.2.)
> 
>   I was getting some undefined symbol errors while linking, "tgoto",
> "tput", and etc. After some sleuth work, I was able figure out that
> adding
> -ltermcap to the compile command allowed it to finish compiling. 
> Unfortunately, the executable it creates immediatly seg faults.
> 
>   When I upgraded to 1.3.2 this time, I completely wiped out
> everything,
> and started over fresh. I have since re-untared the comp.tgz and
> base.tgz
> archives to attempt to fix the problem, but that didn't help. (I
> wasn't
> really expecting it to.)
> 
>   SO, I have suped the current-gnu sources, and they are currently
> compiling (slowly, oh so slowly).
> 
>   Basically, before I go installing current over stable, is there
> something I've missed, or is there anything anbody suggests I check to
> see
> what the matter is? I would appreciate any help I could get.
> 
>   Thanks,
>     - Mike
> 
>