GNU bug report logs - #37650
Fw: Possible bug.

Previous Next

Package: coreutils;

Reported by: George R Goffe <grgoffe <at> yahoo.com>

Date: Mon, 7 Oct 2019 21:34:02 UTC

Severity: normal

To reply to this bug, email your comments to 37650 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-coreutils <at> gnu.org:
bug#37650; Package coreutils. (Mon, 07 Oct 2019 21:34:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to George R Goffe <grgoffe <at> yahoo.com>:
New bug report received and forwarded. Copy sent to bug-coreutils <at> gnu.org. (Mon, 07 Oct 2019 21:34:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: George R Goffe <grgoffe <at> yahoo.com>
To: "bug-coreutils <at> gnu.org" <bug-coreutils <at> gnu.org>
Subject: Fw: Possible bug.
Date: Mon, 7 Oct 2019 21:31:25 +0000 (UTC)
[Message part 1 (text/plain, inline)]
Hi,
I'm building the "latest" coreutils on my Fedora Core 32 x86_64 system with two different versions of the gcc compilers. Both builds are failing with this indication:
In file included from lib/nproc.c:50:
/usr/include/sys/sysctl.h:21:2: error: #warning "The <sys/sysctl.h> header is deprecated and will be removed." [-Werror=cpp]
21 | #warning "The <sys/sysctl.h> header is deprecated and will be removed."
|  ^~~~~~~
cc1: all warnings being treated as errors


I guess the builds would succeed if it weren't for the "-Werror=cpp" flag. I can try removing this flag if you'd like. I thought you might like to see this error though.
I can provide build logs for both versions if you need/want them.
Best Regards,
George...
  
[Message part 2 (text/html, inline)]

Information forwarded to bug-coreutils <at> gnu.org:
bug#37650; Package coreutils. (Tue, 08 Oct 2019 01:13:02 GMT) Full text and rfc822 format available.

Message #8 received at 37650 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: George R Goffe <grgoffe <at> yahoo.com>, 37650 <at> debbugs.gnu.org
Subject: Re: bug#37650: Fw: Possible bug.
Date: Mon, 7 Oct 2019 18:12:32 -0700
On 10/7/19 2:31 PM, George R Goffe via GNU coreutils Bug Reports wrote:
> I guess the builds would succeed if it weren't for the "-Werror=cpp" flag. I can try removing this flag if you'd like.

Yes, please do that. It's generally not a good idea to build with 
different flags than you configured with.




Information forwarded to bug-coreutils <at> gnu.org:
bug#37650; Package coreutils. (Tue, 08 Oct 2019 06:54:01 GMT) Full text and rfc822 format available.

Message #11 received at 37650 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: George R Goffe <grgoffe <at> yahoo.com>
Cc: 37650 <at> debbugs.gnu.org
Subject: Re: bug#37650: Fw: Possible bug.
Date: Mon, 7 Oct 2019 23:53:39 -0700
On 10/7/19 9:12 PM, George R Goffe wrote:

> The intent of the configure directive "--enable-gcc-warnings" that states, "turn on many GCC warnings (for developers; best with GNU make)" is, I guess, to warn developers of situations they need to be aware of.

Sorry, it looks like I misunderstood your bug report.

--enable-gcc-warnings is intended for developers, that is, people who are 
maintaining or modifying coreutils. It tends to generate so many false alarms 
that it is not intended for builders (people who are compiling and installing 
coreutils). This particular diagnostic appears to be a false alarm, as coreutils 
should configure and build just find if sys/sysctl.h is missing. So I suggest 
either ignoring the warning, or omitting --enable-gcc-warnings, or (and this is 
hardest suggestion, and meant only if you want to become a developer) developing 
a patch that pacifies your compiler.




This bug report was last modified 5 years and 312 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.