🚀 go-pugleaf

In article <13100003@tisdec.tis.tandy.com> kevinl@tisdec.tis.tandy.com writes:
>
>When using GNU C/C++ for OS/2, I am unable to run the programs it
>produces.
>
>Everything compiles and links OK when just compiling a C program,
>but when I try to run it, OS/2 stops the program and says it
>created a problem and cannot continue.
>
>When I try to link a C++ program I get unresolved externals that
>look something like __?????__, where ? represents some character--
>some undefined constant I think.
>

  It's been a while since I used GCC/2, but this sounds like you're
not running "collect" on your C++ code.  Look at the example programs'
makefile for more information.

>Also, when link386 finishes, it says that the program type is not
>specified "assuming WINDOWCOMPAT."  How do I specify the program type?
>I tried the /PMTYPE option, but it did not help.  This is really
>secondary.  I don't mind the message as long as I can get the programs
>to actually _run_.

  Chances are, WINDOWCOMPAT is what you want.  As I understand it, it
means that the program is able to be run in a window, as opposed to
full-screen.  PMTYPE would be those that actually use PM features
(i.e., buttons, windows).  I think the third example program is a PM
C++ example.

>Has anyone else experienced similar problems?  Any and all help would
>be appreciated.
>--
>Kevin K. Lewis             | My opinions may be unreasonable
>kevinl@tisdec.tis.tandy.com| but such is the voice of inspiration

  I have to say that I gave up on GCC/2 in favor of EMX/GCC when EMX
added a C++ compiler.  It has support for gdb, and has a built-in
linker (you don't have to use LINK386).  It also seems to be better
supported and more widely used than GCC/2.
-- 
Andrew Bros                             bros@convex.com
System Integration Group                Convex Computer Corporation
It does not do to leave a live dragon out of your calculations,
if you live near him.  - JRR Tolkien, The Hobbit.