From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 3E90A3858D37 for ; Fri, 3 Mar 2023 14:14:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 3E90A3858D37 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1677852868; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=mF631fz7NvCxJVmXcBkN7rOG2oSjYUgpvCnOHLEGRuc=; b=LvLwOWipNktTCJ+xZzJQGk1wHGInzT4GHnf4L9ofBUZXHSDHdJlSNSgOruLgvDD07vT+/a 8wFWzvJq1TGMP3CWcgvCt3/AhhWTNUuKYo1309ak3xzW83js20ZvyDFaP+Em6CFEExZ5dO Kj6TpSJYZfpF7o87lyDcixOC8VNRLhc= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-401-DkA-b3laMiarz2aXBlfJNA-1; Fri, 03 Mar 2023 09:14:25 -0500 X-MC-Unique: DkA-b3laMiarz2aXBlfJNA-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 0738E38123B2; Fri, 3 Mar 2023 14:14:25 +0000 (UTC) Received: from redhat.com (unknown [10.33.36.53]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9EE5140B40DF; Fri, 3 Mar 2023 14:14:21 +0000 (UTC) Date: Fri, 3 Mar 2023 14:14:18 +0000 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Wookey Cc: Paul Eggert , Bruno Haible , "Richard W.M. Jones" , Demi Marie Obenour , Eric Blake , Sam James , Carlos O'Donell via Libc-alpha , autoconf@gnu.org, c-std-porting@lists.linux.dev, Zack Weinberg , David Seifert , Gentoo Toolchain , Arsen =?utf-8?Q?Arsenovi=C4=87?= , dueno@redhat.com Subject: Re: On time64 and Large File Support Message-ID: Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= References: <7253e4c5-0f36-e725-f180-624f8887bf08@cs.ucla.edu> <20230302110244.GK7636@redhat.com> <4158136.ciBtUerH68@nimes> <20230303033045.GO12440@mail.wookware.org> <20230303140135.GX12440@mail.wookware.org> MIME-Version: 1.0 In-Reply-To: <20230303140135.GX12440@mail.wookware.org> User-Agent: Mutt/2.2.9 (2022-11-12) X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Fri, Mar 03, 2023 at 02:01:35PM +0000, Wookey wrote: > On 2023-03-02 21:50 -0800, Paul Eggert wrote: > > On 3/2/23 19:30, Wookey wrote: > > > > Gnulib automatically changing the ABI for packages that use it > > > (and have LFS already enabled) is deeply unhelpful... > > > This change to Gnulib was reverted in December[1] and that propagated into > > bleeding-edge GnuTLS last month[2]. So if I understand things correctly the > > next GnuTLS release will go back to the old way of doing things, > > OK. gnulib doesn't seem to have releases as such (last release v0.1 9 > years ago), and is normally used embedded in the upstream source like > autotools (right?). What is a good test for whether a package/upstream > is affected by this 'gnulib might have turned 64-bit time' issue? Is > there an embedded gnulib version one can check, or does one have to look > at dates of the m4/year2038.m4 and m4/largefile.m4 files in the source? Looks like you can probably detect it from the configure --help output. Based on this commit: > > [1]: https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=7c7c8a519f3892f6f5b30a1c6b22796ab314a45c The original problematic impl has this: - AC_ARG_ENABLE([year2038], - [ --disable-year2038 omit support for timestamps past the year 2038]) the new code which does not enable 2038 by default has +[AC_ARG_ENABLE([year2038], + m4_provide_if([AC_SYS_YEAR2038], + [AS_HELP_STRING([--disable-year2038], + [do not support timestamps after 2038])], + [AS_HELP_STRING([--enable-year2038], + [support timestamps after 2038])]))]) So if configure --help | grep disable-year2038 says 'omit support for timestamps past the year 2038', the app is suspect and might face ABI compat issues. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|