Help with getting started on Mac OS X

Doug McClure <[email protected]>
Newsgroups gmane.comp.bug-tracking.gnats.general
Message-ID <[email protected]>
Hi,

I'm trying to setup gnats 3.999.2 on a Mac OS X Server but I'm having a 
few problems, and I'm wondering if anyone else has managed to get gnats 
up and running on X Server 10.2.5.

When I build gnats, I get a LOT of errors like these

...
regex.h:434:3: style of line directive is a GCC extension
regex.h:518:3: style of line directive is a GCC extension
regex.h:558:3: style of line directive is a GCC extension
In file included from edit.c:21:
gnats.h:407:3: style of line directive is a GCC extension
edit.c:22:3: style of line directive is a GCC extension
In file included from edit.c:22:
gnatsd.h:2:3: style of line directive is a GCC extension
gnatsd.h:23:3: style of line directive is a GCC extension
...

and some errors like this:

In file included from /usr/include/machine/types.h:30,
                  from /usr/include/stddef.h:63,
                  from ./../include/libiberty.h:129,
                  from gnats.h:37,
                  from edit.c:21:
/usr/include/ppc/types.h:75: warning: ISO C89 does not support `long 
long'
/usr/include/ppc/types.h:76: warning: ISO C89 does not support `long 
long'

In the end, gnatsd did compile, but when inetd tries to start it, I it 
crashes and I get a backtrace like this:

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00091fff

Thread 0 Crashed:
  #0   0x9007472c in memmove
  #1   0x0000fdf8 in xstrndup (misc.c:398)
  #2   0x0001a92c in getOneAddress (mail.c:236)
  #3   0x0001a998 in get_responsible_addr (mail.c:251)
  #4   0x00003c64 in gnatsdChdb (cmds.c:662)
  #5   0x00002d20 in main (gnatsd.c:1044)
  #6   0x0000186c in _start (crt.c:267)
  #7   0x000016ec in start

If anybody has gotten it running on X Server, I'd appreciate any help 
you can give me

-d
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.