Deprecated usage in linux.cf

[Alan Coopersmith]

I've cc'ed the xorg-devel mailing list to reach the other X.Org developers,
as I primarily work on Solaris, not Linux, myself.

I have no objection to such a change, and would accept a merge request [1] to
do it from someone who can test it, but I don't know if there needs to be
any sort of version check to use the older defines on older releases, and
the newer defines on newer ones, or even if we could check that in Imake,
since I believe it depends on the GNU libc version, not the Linux version.

Really though, TightVNC needs to move to a modern build system if it wants
to build on modern platforms, because we're not really maintaining Imake
and haven't done so in many years now.

	-alan-

[1] https://gitlab.freedesktop.org/xorg/util/cf/-/merge_requests

On 7/18/22 12:58, Ken Zalewski wrote:
> Hi Alan,
> 
> I saw that you released xorg-cf-files 1.0.7 back in 2021, via this archived email:
> https://lists.x.org/archives/xorg-announce/2021-August/003105.html 
> <https://lists.x.org/archives/xorg-announce/2021-August/003105.html>
> 
> I realize that the Imake system is antiquated, but it is still necessary to 
> build TightVNC on Linux.  I wanted to point out that GCC now issues a 
> deprecation warning when using -D_BSD_SOURCE and -D_SVID_SOURCE.  I believe the 
> correct define is now -D_DEFAULT_SOURCE.
> 
> I tracked this down to the file:
> /usr/lib64/X11/config/linux.cf <http://linux.cf>
> 
> When I modify lines 241 and 260 to replace "-D_BSD_SOURCE -D_SVID_SOURCE" with 
> "-D_DEFAULT_SOURCE", I no longer receive the deprecation notices.
> 
> Would it be possible to issue a new minor release of xorg-cf-files with this fix?
> 
> Thank you,
> 
> Ken Zalewski
> Troy, NY
> 
> 
> 
> 


-- 
         -Alan Coopersmith-                 alan.coopersmith at oracle.com
          Oracle Solaris Engineering - https://blogs.oracle.com/solaris