ports/130986: [PATCH] x11/xmore build failure

[Randy Pratt]

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

From: Randy Pratt <bsd-unix at embarqmail.com>
To: John Nielsen <john at jnielsen.net>
Cc: Robert Noland <rnoland at freebsd.org>, bug-followup at freebsd.org
Subject: Re: ports/130986: [PATCH] x11/xmore build failure
Date: Thu, 26 Mar 2009 19:26:11 -0400

 On Tue, 24 Mar 2009 11:46:40 -0400
 John Nielsen <john at jnielsen.net> wrote:
 
 > I just ran in to the same build failure as the original submitter but on a 
 > machine running -CURRENT. Since you (rnoland) couldn't reproduce the 
 > issue and I've only seen it on one machine out of several I've been 
 > updating lately I suspect the problem is likely a missing dependency. I 
 > did recently do a pkg_cutleaves run on the machine now having the 
 > problem, but not quite recently enough that I remember everything I 
 > removed.
 > 
 > Randy, do you recall uninstalling any ports prior to encountering this 
 > issue or is your Xorg configuration otherwise customized?
 
 Its been awhile, but my ports mix does change occasionally and its
 entirely possible that I could have removed something.  Up
 to that point I had been updating ports daily for about 3 years.  I use
 portmaster and regularly run the "--check-depends" option.  This
 should restore any missing dependencies required by the ports
 Makefile.  If there is a missing dependency in the Makefile, it appeared
 with the new xorg since xmore compiled fine with the older xorg.
 
 At the time, I gave up on updating to the latest xorg due to
 keyboard/mouse problems and just reverted my tree back to just before
 the xorg update (2009-01-23 09:58:10 UTC) and left it there.
 
 > I played around with a Makefile solution and while I was able to 
 > get --disable-xprint passed to the configure step it doesn't fix the 
 > problem. However, if I do a "make configure" (with or without my patched 
 > Makefile) then cd $WRKSRC then manually 
 > run "./configure --disable-xprint", a subsequent "make install" from the 
 > ports directory builds and installs just fine. So either my ports fu 
 > isn't up to snuff or something odd is going on or both.
 
 I may get some time when the weather gets hot to attempt the xorg update
 again but its a lot of compiling and a lot more if I have to revert the
 tree again.  This time will probably be a wipe-all-ports and reinstall
 since the ports tree has moved so much in the past couple of months
 that its not worth doing an upgrade path.
 
 Thanks for confirming that I'm not the only one who has seen this.
 
 Randy