From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id iShUFULay2HpDwAAWB0awg (envelope-from ) for ; Tue, 28 Dec 2021 22:47:14 -0500 Received: by simark.ca (Postfix, from userid 112) id 478731F0D7; Tue, 28 Dec 2021 22:47:14 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id AD5241F0D4 for ; Tue, 28 Dec 2021 22:47:13 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id CB834385841C for ; Wed, 29 Dec 2021 03:47:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CB834385841C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1640749632; bh=Z/+usiVW0S6lmR8ZRKukQDWu09QrGBm5Coa41hVXjSo=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=QNKpDTjpG3N/YsZdsY1AafjgmRbNoYAdZLs0CYWBDrRlAKsBgwLimbw5vssSzx6W9 zMas3qydn7GBY+K1STEfMsj9agVt4iPX5DRgcVpZcZLooLpFR59NH2tAKkNyMfmevH or6RGyQqDCtCtrsxkhty/L9WmIVtDWXI2XqrgcUY= Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) by sourceware.org (Postfix) with ESMTPS id 1442F3858406 for ; Wed, 29 Dec 2021 03:46:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1442F3858406 Received: by mail-wr1-x430.google.com with SMTP id v7so41760766wrv.12 for ; Tue, 28 Dec 2021 19:46:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Z/+usiVW0S6lmR8ZRKukQDWu09QrGBm5Coa41hVXjSo=; b=kPh8reDNMranY2QfFsOxbRBk4sKDtIx/YVnURFoS87o/g+aYq6xhJ0ghDjIFo0YbI7 oyYaVepC6HkibKSo3ScUPBmb1Z8ATRa8+E9WiZ2bjBnoVFDJ+W+wz3+xUgpWgtPlqw/y r7r7SB76VVkI4GUM7zwofvlwTYvxZCo5Ve8nOUNZdFO1ib+QkpVSQWpHYVX0UQPhSdz7 RLr3LXBFqEw92MtyEcgXNDeA2aWRDzm5ltoa2fs5Al88Z1YsDq7vItmHC+JVCfeZPE3d bq+zmgVrDyoURhwqhvSlmw9SAYFvOS9TcIXz8FbAlXQVyg4ssWslY0rfbjfCME1f6RJj ri1A== X-Gm-Message-State: AOAM532YcD+ablCoIYjt6WIPfyegzaLEplXRgStvhafI36dQ5GNBSz6S SS/dVw/OVZRXLFpcYqbDjcP0 X-Google-Smtp-Source: ABdhPJwt/m0kViYc63WmaD60QIHxdzFX46aX5/dReQu/wuOa+KA19yz3Tfo40T+OJuTj+V8nkqM9ZQ== X-Received: by 2002:a5d:6cd0:: with SMTP id c16mr18809397wrc.625.1640749605097; Tue, 28 Dec 2021 19:46:45 -0800 (PST) Received: from takamaka.home ([2a01:cb22:1d5:1100:5cd6:fe3f:9e98:8792]) by smtp.gmail.com with ESMTPSA id y1sm19492967wrm.3.2021.12.28.19.46.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 28 Dec 2021 19:46:44 -0800 (PST) Received: by takamaka.home (Postfix, from userid 1000) id F2231A4A8F; Wed, 29 Dec 2021 07:46:40 +0400 (+04) Date: Wed, 29 Dec 2021 07:46:40 +0400 To: Simon Marchi via Gdb Subject: Re: -Werror enabled by default on GNU/Hurd Message-ID: References: <87pmpgml2v.fsf@autistici.org> <1fe352c0-a665-cd60-51cf-a47bce29ac61@polymtl.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1fe352c0-a665-cd60-51cf-a47bce29ac61@polymtl.ca> X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Joel Brobecker via Gdb Reply-To: Joel Brobecker Cc: Andrea Monaco , Joel Brobecker Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" > > When building gdb on GNU/Hurd, -Werror is enabled by default. I think > > that's a bug: that option is only useful in specific instances; enabling > > it by default means that the build fails after a plain ./configure, and > > you need to pass --disable-werror to make it succeed. > > > > I tried to locate the problem myself, but the build scripts are very > > complex. Could someone please give me some hints? > > What are the errors you see? We aim for warning-free builds, so the best > fix would be to get rid of these warnings. Indeed. If you use the development branch, then we want warnings to trigger an error -- otherwise, those warnings very rarely get looked at. The situation is different on release branches, where warnings are made non-fatal. -- Joel