[bug #25026] compilation of gnustep-base fails on openbsd 4.4 sparc

[Sebastian Reitenbach]

Follow-up Comment #2, bug #25026 (project gnustep):

Hi,

I applied the changes you did in trunk to the -stable sources I have
installed, and it compiles now. Many thanks.
Will this also be backported to -stable?


However, I get the following warnings when compiling:
cc GSXML.m -c 
              -Wall -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_RUNTIME=1
-DGNUSTEP_BASE_LIBRARY=1 -D_REENTRANT -fPIC -g -Wall -DDEBUG
-fno-omit-frame-pointer -DGSWARN -DGSDIAGNOSE -Wno-import -O2 -pipe
-fno-strict-aliasing -fgnu-runtime -I../../Headers/Additions -I../. -I../
-I../../Headers -I. -I/usr/local/include -I/usr/local/include
-I/usr/local/include -I/usr/local/include/libxml2 -I/usr/local/include
-I/usr/local/include -I/usr/local/include -I/usr/local/include
-I/gnustep-base-1.16.5_writes_to_HOME/GNUstep/Library/Headers
-I/usr/local/include 
               -o obj/GSXML.o
GSXML.m: In function `loadEntityFunction':
GSXML.m:2420: warning: assignment from incompatible pointer type
GSXML.m: In function `-[GSXMLDocument(XSLT) xsltTransform:params:]':
GSXML.m:3995: warning: variable `newdoc' might be clobbered by `longjmp' or
`vfork'
GSXML.m: In function `-[GSXMLRPC
initWithURL:certificate:privateKey:password:]':
GSXML.m:5102: warning: argument `self' might be clobbered by `longjmp' or
`vfork'
GSXML.m: In function `-[GSXMLRPC parseMethod:params:]':
GSXML.m:5167: warning: variable `ctx' might be clobbered by `longjmp' or
`vfork'
GSXML.m:5168: warning: variable `ns' might be clobbered by `longjmp' or
`vfork'
GSXML.m:5169: warning: variable `parser' might be clobbered by `longjmp' or
`vfork'
GSXML.m: In function `-[GSXMLRPC parseResponse:params:]':
GSXML.m:5237: warning: variable `ctx' might be clobbered by `longjmp' or
`vfork'
GSXML.m:5238: warning: variable `ns' might be clobbered by `longjmp' or
`vfork'
GSXML.m:5239: warning: variable `parser' might be clobbered by `longjmp' or
`vfork'
GSXML.m:5240: warning: variable `fault' might be clobbered by `longjmp' or
`vfork'

don't know whether these will be problematic, however, the initial problem is
fixed. 

Sebastian

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?25026>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/