misc/65924: XFree86-4-libraries won't include in xc/lib/X11

[Kris Kennaway]

The following reply was made to PR ports/65924; it has been noted by GNATS.

From: Kris Kennaway <kris at obsecurity.org>
To: Coleman Kane <cokane at cokane.org>
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: misc/65924: XFree86-4-libraries won't include in xc/lib/X11
Date: Fri, 23 Apr 2004 21:24:22 -0700

 On Fri, Apr 23, 2004 at 08:07:20PM -0700, Coleman Kane wrote:
 > 
 > >Number:         65924
 > >Category:       misc
 > >Synopsis:       XFree86-4-libraries won't include in xc/lib/X11
 > >Confidential:   no
 > >Severity:       non-critical
 > >Priority:       low
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Fri Apr 23 20:10:24 PDT 2004
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Coleman Kane
 > >Release:        FreeBSD 5-current
 > >Organization:
 > >Environment:
 > FreeBSD blah 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Fri Apr 23 03:59:18 GMT 2004     root at blah:/usr/obj/usr/src/sys/BLAH  i386
 > 
 > >Description:
 >      x11/XFree86-4-libraries won't configure. Dies at making includes in xc/lib/X11 on building makekeys.
 > >How-To-Repeat:
 >       Build x11/XFree86-4-libraries from ports
 > >Fix:
 >       Modify the xc/config/cf/FreeBSD.cf file, and remove the NULL-quote from the SystemMTDefines #define. GCC interprets this as an argument, an input file named <NULL>, which it cannot find and it dies.
 > 
 > --- FreeBSD.cf  Sat Apr 24 02:43:59 2004
 > +++ FreeBSD.cf.old      Sat Apr 24 02:46:00 2004
 > @@ -89,7 +89,7 @@
 >  # endif
 >  # define HasPosixThreads       YES
 >  # define ThreadedX             YES
 > -# define SystemMTDefines       
 > +# define SystemMTDefines       ""
 >  /*
 >   * FreeBSD has tread-safe api but no getpwnam_r yet.
 >   */
 
 This patch won't apply; what you describe is a side-effect of
 files/patch-FreeBSD.cf.  However there has to be more to the story,
 because the port has been building successfully on 5.x for the past 2
 months that the patch has been in place.
 
 Kris