El día Tuesday, October 29, 2013 a las 07:52:14AM -0700, Cy Schubert escribió:

> In message <[email protected]>, Matthias Apitz writes:
> > 
> > Hello,
> > 
> > The vnc client only build in /head (anyway if with clang or gcc46) if
> > one adds an 
> > 
> > #include <stdlib.h> to the following three files:
> > 
> > ./work/vnc-4_1_3-unixsrc/common/network/TcpSocket.cxx
> > ./work/vnc-4_1_3-unixsrc/unix/tx/TXImage.cxx
> > ./work/vnc-4_1_3-unixsrc/unix/x0vncserver/Image.cxx
> > 
> > The server part stops building in:
> > 
> > ...
> > cc -c  -O -I../../include -I../../imports/x11/include/X11 `./ccimake` 
> > imake.c
> > cc -o imake  -O -I../../include -I../../imports/x11/include/X11 imake.o
> > rm -f ./config/makedepend/Makefile.proto
> > ./config/imake/imake -I./config/cf  -s ./config/makedepend/Makefile.proto 
> > -f 
> > ./config/makedepend/Imakefile -DTOPDIR=../.. -DCURDIR=./config/makedepend
> > objformat: not found
> > In file included from Imakefile.c:16:
> > In file included from ./config/cf/Imake.tmpl:104:
> > ./config/cf/FreeBSD.cf:477:35: error: '#' is not followed by a macro 
> > paramete
> > r
> 
> I haven't looked at it completely but it appears vnc needs a few patches to 
> add includes for stdlib.h. It's on my plate of things to do.

The missing includes for stdlib.h is an easy one, but the imake problem is
more complex; see also our exchange in June:

  Date: Fri, 7 Jun 2013 10:57:30 +0200
  To: Niclas Zeising <[email protected]>, [email protected], 
[email protected]
  Subject: Re: ports && 10-CURRENT
  Message-ID: <[email protected]>
  References: <[email protected]> 
<[email protected]> <[email protected]>

HIH

        matthias

-- 
Sent from my FreeBSD netbook

Matthias Apitz, <[email protected]>, http://www.unixarea.de/ f: +49-170-4527211
UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"

Reply via email to