🚀 go-pugleaf

N.Davis@lut.ac.uk writes:

>In article <garp.726271124@isy.liu.se> garp@isy.liu.se (Johan Garpendahl) writes:
>>Here are a few patches to make InterViews 3.1 compile better with gcc-2.3.3.
>>
>>
>>Don't try to compile with -O2.
>>Don't try to make shared libraries.
>>I tried it.
>>

>Hmm, why should I not compile InterViews 3.1 shared libraries using gcc-2.3.3?
>I have done just this, and judging by the comments made about which binaries
>work and which do not, I seem to be in exactly the same situation as those
>of you who favour non-shared libraries.

OK, maybe I should have put a smiley somewhere.
Try it if you like, but don't complain if everything doesn't work.

>I will however admit that all the Unidraw based progs fail; I'm no C++ guru
>but I appear to have an empty string being passed to the constructor
>of ControlInfo which ultimately core dumps in newstr. (see the GDB output
>below). This used to work in gcc-2.3.2 (At least, I seem to recall running
>idraw, or am I mistaken).

I've done some experimenting with that and I can make a workaround
for the strings by initializing them from the Unidraw constructor.
Idraw will then start up nicely, but you won't be able to do anything
useful because the mouse-events won't get through. 

If anyone knows why, or has a workaround for that one, I'd be happy.

After all, I want to use shared libraries, but I'm not ready to give
up Idraw or Unidraw to get it. I'd even like to be able to use libg++
as a shared library, but that doesn't seen to work yet either.

Happy hacking, 

	Johan


-- 
Johan Garpendahl                   | Email: garp@isy.liu.se
Linkoping University               | Phone: +46 - 13 - 28 13 24
Dept. of Electrical Engineering    | Fax  : +46 - 13 - 13 92 82
S-581 83  LINKOPING // SWEDEN      | May the Source be with you.