Thought I'd give xcircuit an update (3.8.31) so the General might spend more time here, got almost to the end but then :
This seems to be a linking error but I ain't no programmer ... what's the best way to figure this out ?
Second, several of these :
Shouldn't even gcc find things like this ? Defining the same thing several times cannot be good.
Then there's about two bazillion of these :
Almost wore out my character generator. That particular warning is common in tons of open source software ... if I were writing code you'd expect this shit but isn't a thousand eyes, five hundred keyboards supposed to fix this kind of thing ?
Code:
ld32: ERROR 33 : Unresolved text symbol "vfork" -- 1st referenced by svg.o.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: INFO 152: Output file removed because of error.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: INFO 152: Output file removed because of error.
This seems to be a linking error but I ain't no programmer ... what's the best way to figure this out ?
Second, several of these :
Code:
ld32: WARNING 15 : Multiply defined:(fontnumbers) in menucalls.o and xtfuncs.o (2nd definition ignored).
ld32: WARNING 15 : Multiply defined:(popups) in xcircuit.o and xtgui.o (2nd definition ignored).
ld32: WARNING 15 : Multiply defined:(popups) in xcircuit.o and xtgui.o (2nd definition ignored).
Shouldn't even gcc find things like this ? Defining the same thing several times cannot be good.
Then there's about two bazillion of these :
Code:
cc-3970 cc: WARNING File = xtgui.c, Line = 878
conversion from pointer to same-sized integral type (potential portability
problem)
XtnSetArg(XtNstring, request);
^
conversion from pointer to same-sized integral type (potential portability
problem)
XtnSetArg(XtNstring, request);
^
Almost wore out my character generator. That particular warning is common in tons of open source software ... if I were writing code you'd expect this shit but isn't a thousand eyes, five hundred keyboards supposed to fix this kind of thing ?