Re: [chrony-dev] [GIT] chrony/chrony.git branch master updated. 4.3-32-gbadaa83 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] [GIT] chrony/chrony.git branch master updated. 4.3-32-gbadaa83
- From: David Bohman <debohman@xxxxxxxxx>
- Date: Thu, 19 Jan 2023 06:37:57 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=TdMaXI45//QKAtBcwH7DCrI3jKhqi8f18tfU6kebdJk=; b=c0rayWskx1iPRR9bs605sZRRGa0YG+xTkWFjy4+BNDD8ZiBMot/U/uDaS8W1PqdEfN Z+86DFwzPl1A6bSMqKodiaOAQkgqmGr2JuCOqxJN3S17B/LnNQZkylT95z8pqtGZeawL bdeZ+mxPQMDbG9qOIiLJzCZv929GnjzAWl25pkj86jrQss3GmDj3eGxP9aJMPDrqNO38 WBWkbrJ5ZdaALA74LNYnAe6LRYQnyDNB+rkXbnoItXfoXf9ALc5De2WuIWoPxk6UWQHp EsNPwUsiC/Wb4+wpKN9iEYUp0+kVAwyT+FwaXUWI/xbUcUpq2D9wM613P0y2pXApH4ni 2OLA==
The current TOT builds fine now. Thanks.
On Thu, Jan 19, 2023 at 2:53 AM Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
>
> On Thu, Jan 19, 2023 at 09:45:28AM +0100, Miroslav Lichvar wrote:
> > On Thu, Jan 19, 2023 at 06:23:32AM +1300, Bryan Christianson wrote:
> > > -#if defined(__GLIBC_PREREQ) && __GLIBC_PREREQ(2, 34) && __TIMESIZE == 32
> > > +#ifdef __GLIBC_PREREQ
> > > +#if __GLIBC_PREREQ(2, 34) && __TIMESIZE == 32
> > > #define CONVERT_TIMEVAL 1
> > > #if defined(_TIME_BITS) && _TIME_BITS == 64
> >
> > The same issue is on this line ^.
>
> It turns out this works with both gcc and clang, even with -Wundef, so
> I'll leave it there.
>
> --
> Miroslav Lichvar
>
>
> --
> To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
> For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
> Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.
>
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.