gpsd-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] featuretest macros


From: Gary E. Miller
Subject: Re: [gpsd-dev] featuretest macros
Date: Fri, 21 Jun 2019 16:56:03 -0700

Yo Greg!

On Fri, 21 Jun 2019 19:50:36 -0400
Greg Troxel <address@hidden> wrote:

> "Gary E. Miller" <address@hidden> writes:
> 
> > What is a "correct warning?  
> 
> The ones I sent a few days ago were on netbsd-8.  By correct, I meant
> that reading the source, I concur with the compiler that a warning is
> in order.

Which differs from the gpsd preference of "no warnings", if possible.

These are the one you sent earlier this week?

> >> Certainly, if one defines _XOPEN_SOURCE to 700 and does not define
> >> _NETBSD_SOURCE, then there are lots of undeclared functions.
> >> Which is correct, as _XOPEN_SOURCE is a request to make visible
> >> the symbols specified by that standard, and no more.  
> >
> > Uh, which is it now?  You need _NETBSD_SOURCE, or not?  
> 
> I do not need it, unless I also have XOPEN_SOURCE, in which case I do.
> Because the default behavior is to implicitly define _NETBSD_SOURCE
> unless some other visibility defines are present.

And they are, from Python.h

> > And we can't remove _XOPEN_SOURCE, and others, from gpsd as Python.h
> > defines it.  Not much t gpsd without Python.h  
> 
> That is arguably a bug in python.

Yes, exactly my thoughts.  Please file a bug upstream.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin

Attachment: pgpCCmduxGCJ1.pgp
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]