🚀 go-pugleaf

In article <103@snll-arpagw.UUCP> paolucci@snll-arpagw.UUCP (Sam Paolucci) writes:
>... but it also prints a bunch of
>messages all similar to:
>Structure definition 'VSprite' never completed.
>...  Where does this come from?  Also, does anybody
>know what the linker messages mean?  Any clue is appreciated.
>				ARPA: paolucci@snll-arpagw.llnl.gov

I've not used Manx, but the Lattice compiler used to do similar things.
I suspect that you are including a file that does something
like

struct XXX {
    blah blah blah;
    struct VSprite * spritelist;
    blah blah blah;
    };

and then declaring something of type struct XXX.
Since you don't reference the VSprite, you don't
get compiler errors (because all pointers are the same
size (is this true in ANSI C?)). However, maybe the
linker is looking for how big (*spritelist) should
be for some reason. As you requested,
this is just a clue, because I really have no idea
what I'm talking about (or how you could automatically
find where such a thing is declared). -- Darren