Problem updating xorg-clients

Joshua Tinnin krinklyfig at spymac.com
Fri Jul 30 21:18:17 PDT 2004


(message has been reformatted from top-posting ...)

On Friday 30 July 2004 04:44 am, "Michael L. Squires" <mikes at siralan.org> 
wrote:
> On Thu, 29 Jul 2004, Joshua Tinnin wrote:
> > I'm getting an error message (below) when trying to upgrade the
> > xorg-clients port, and I'm not at all sure how to fix it. Am running
> > 5.2.1-RELEASE-p9 with xorg-6.7.0_1.
> >
> > - jt
> >
> > making all in programs/xhost...
> > cc -O -pipe -march=athlon-xp -ansi -pedantic -Wno-system-headers
> > -Dasm=__asm -Wall -Wpointer-arith -Wundef    
> > -I/usr/ports/x11/xorg-clients/work/xc
> > -I/usr/ports/x11/xorg-clients/work/xc/exports/include 
> > -I/usr/X11R6/include -DCSRG_BASED  -DFUNCPROTO=15 -DNARROWPROTO  
> > -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT -DHAS_FCHOWN -DIPv6            
> >    -DBSD44SOCKETS -DXVENDORNAME='"The X.Org Foundation"'
> > -DXVENDORNAMESHORT='"X.Org"' -c xhost.c
> > xhost.c: In function `change_host':
> > xhost.c:423: error: syntax error before "siaddr"
> > xhost.c:434: error: `siaddr' undeclared (first use in this function)
> > xhost.c:434: error: (Each undeclared identifier is reported only once
> > xhost.c:434: error: for each function it appears in.)
> > xhost.c: In function `get_hostname':
> > xhost.c:883: error: `XServerInterpretedAddress' undeclared (first use in
> > this function)
> > xhost.c:883: error: `sip' undeclared (first use in this function)
> > xhost.c:884: warning: ISO C89 forbids mixed declarations and code
> > xhost.c:888: error: syntax error before ')' token
> > *** Error code 1
> >
> > Stop in /usr/ports/x11/xorg-clients/work/xc/programs/xhost.
> > *** Error code 1
> >
> > Stop in /usr/ports/x11/xorg-clients/work/xc/programs.
> > *** Error code 1
> >
> > Stop in /usr/ports/x11/xorg-clients.
> > ** Command failed [exit code 1]: /usr/bin/script -qa
> > /tmp/portupgrade99236.6 make
> > ** Fix the problem and try again.
>
> I just built xorg from scratch under 5.2-CURRENT (of the past few days)
> and didn't have this problem.

I'm not sure what it is. I tried upgrading again today after a daily cvsup, 
and still getting this error. I know enough about programming to know what 
file and line has the problematic code, but I'm not sure what to do to fix 
it. I think it's on my end, as I haven't heard anyone else comment on this 
issue, but not sure why or where ...

- jt


More information about the freebsd-questions mailing list