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.133.124]) by sourceware.org (Postfix) with ESMTPS id ACD0D3858D1E for ; Mon, 19 Dec 2022 12:27:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org ACD0D3858D1E 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=1671452879; h=from:from: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=kg+Q2qNCSy6HtlKiYuBO/Us7+ulezXH9QcKdqVNvIrI=; b=LaUixVdZgzIRCOZAmEF5wY6sJE/rKUGeXqFOBAOHB2vlWVwYxai1dmVOWWG13uBdJj8Dgd 8QiNx2Bt6G8Q9kNHkGnjL0FqmXRlH28FhVYT1XtNsy3N/oKvHFPzxZQ57nQELUMwDxm3zE SXL//Q3zOZSuoDCDn3R6dqk0DC6g/oQ= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-632-MFtsionDMgq_Nu5V_wZq5g-1; Mon, 19 Dec 2022 07:27:58 -0500 X-MC-Unique: MFtsionDMgq_Nu5V_wZq5g-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D67F1811E9C; Mon, 19 Dec 2022 12:27:57 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3DCC12166B26; Mon, 19 Dec 2022 12:27:57 +0000 (UTC) From: Florian Weimer To: Adhemerval Zanella Netto Cc: libc-alpha@sourceware.org, Carlos O'Donell Subject: Re: [PATCH 0/2] Fix incorrect stub warnings after generic refactor References: Date: Mon, 19 Dec 2022 13:27:55 +0100 In-Reply-To: (Adhemerval Zanella Netto's message of "Mon, 19 Dec 2022 09:16:58 -0300") Message-ID: <87y1r3fuic.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.6 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: * Adhemerval Zanella Netto: > On 19/12/22 09:03, Florian Weimer wrote: >> They cause link failures with -Wl,--fatal-warnings on aarch64. >> > > Would be possible to use this option as default to catch such errors? We'd have to make it conditional because tests for mktemp and the like do result in warnings. We also do not have an inotify test, but in this particular case, maybe the nscd build would have caught it. Thanks, Florian