Created attachment 148774 [details] transcript of 'make all' 2.21.15_5 version make terminates with: /usr/local/include/xorg/fb.h:837: warning: redundant redeclaration of 'fbGetWinPrivateKey' /usr/local/include/xorg/fb.h:611: warning: previous declaration of 'fbGetWinPrivateKey' was here *** [intel_batchbuffer.lo] Error code 1 Stop in /usr/obj/usr/ports/x11-drivers/xf86-video-intel/work/xf86-video-intel-2.21.15/src/uxa. *** [all-recursive] Error code 1 Stop in /usr/obj/usr/ports/x11-drivers/xf86-video-intel/work/xf86-video-intel-2.21.15/src. *** [all-recursive] Error code 1 Stop in /usr/obj/usr/ports/x11-drivers/xf86-video-intel/work/xf86-video-intel-2.21.15. *** [all] Error code 1 Stop in /usr/obj/usr/ports/x11-drivers/xf86-video-intel/work/xf86-video-intel-2.21.15. *** [do-build] Error code 1 Stop in /usr/ports/x11-drivers/xf86-video-intel.
Auto-assigned to maintainer x11@FreeBSD.org
Hi! Two declaration in the same header is really strange. Could you please indicate the version of xorg-server you have? And could you please attach /usr/local/include/xorg/fb.h to this bug report?
xorg-server-1.7.7_14,1
Created attachment 148776 [details] /usr/local/include/xorg/fb.h
We don't support xorg-server 1.7 anymore and xf86-video-intel 2.21.15 isn't compatible with it. You need to update xorg-server and probably other related ports. The reasons for ending the support of xorg-server 1.7 and several other really old ports is explained in the following mail: https://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-October/000096.html If you need help to proceed with the update, please ask your questions here :)
Yes. However WITH_NEW_XORG has been removed from xf86-video-intel recently, but not from xorg-server. Therefore I (as a naïve user) would expect it to work still. Failing miserably during compilation with cryptic errors is not exactly self-explanatory. Is there any particular reason for keeping WITH_NEW_XORG in xorg-server but removing it from drivers?
I think the maintainers wanted to remove the flag with the next updates to each ports. For instance, there's an update to xorg-server 1.14 cooking. This future update will remove the old WITH_NEW_XORG bits.
(In reply to Helge Oldach from comment #6) > Yes. However WITH_NEW_XORG has been removed from xf86-video-intel recently, > but not from xorg-server. Therefore I (as a naïve user) would expect it to > work still. Failing miserably during compilation with cryptic errors is not > exactly self-explanatory. > > Is there any particular reason for keeping WITH_NEW_XORG in xorg-server but > removing it from drivers? Correct WITH_NEW_XORG was removed from xf86-video-intel but it has been turned on by default in https://svnweb.freebsd.org/changeset/ports/369875 unless WITHOUT_NEW_XORG was set. But the whole WITH_NEW_XORG switch is going away. Which version of FreeBSD is this and do you maybe have WITHOUT_NEW_XORG set in /etc/make.conf?
9-STABLE (built world about a week ago) - Yes, I know it does support KMS, and it should thus run the new xorg-server. Quite frankly I even tried that but was disappointed that it did build a huge amount of other ports (GCC and so on), and it resulted in garbage on my screen. So I dropped back again. Did not seem ready for prime time at that moment. (FWIW, this is an elder Q965-equipped machine.) Indeed, /etc/make.conf has WITHOUT_NEW_XORG=yes. The old xorg-server has been doing fine for me up to now, so why change it... I was just struck that NEW_XORG is still in xorg-server while it has been removed from drivers, rendering them uncompilable.
Fixed by removal of WTHOUT_NEW_XORG, forcing upgrading xorg-server to 1.12.