|
From: | GNU bug Tracking System |
Subject: | bug#55010: closed (Compiling from git clone) |
Date: | Wed, 20 Apr 2022 16:49:01 +0000 |
Your message dated Wed, 20 Apr 2022 09:47:59 -0700 with message-id <6c72d4ea-b9f9-20f8-fa02-ac2b48809bc8@cs.ucla.edu> and subject line Re: bug#55010: Compiling from git clone has caused the debbugs.gnu.org bug report #55010, regarding Compiling from git clone to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 55010: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=55010 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: Compiling from git clone Date: Mon, 18 Apr 2022 14:47:39 -0700 Making all in .
make[2]: Entering directory '/home/kingram/src/coreutils'
CC lib/libcoreutils_a-randperm.o
lib/randperm.c: In function 'sparse_new':
lib/randperm.c:111:1: error: function might be candidate for attribute 'malloc' if it is known to return normally [-Werror=suggest-attribute=malloc]
sparse_new (size_t size_hint)
^~~~~~~~~~
cc1: all warnings being treated as errors
make[2]: *** [Makefile:15588: lib/libcoreutils_a-randperm.o] Error 1
make[2]: Leaving directory '/home/kingram/src/coreutils'
make[1]: *** [Makefile:21009: all-recursive] Error 1
make[1]: Leaving directory '/home/kingram/src/coreutils'
make: *** [Makefile:8267: all] Error 2
--- End Message ---
--- Begin Message ---Subject: Re: bug#55010: Compiling from git clone Date: Wed, 20 Apr 2022 09:47:59 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 On 4/19/22 22:54, Ken Ingram wrote:So I guess I'm on an "old" compiler compared to 11.2.1Yes, so let's not worry about the warning, as it suggests adding clutter unnecessary in modern compilers, it's easy to ignore the warnings in older compilers, and this is an issue only when using --enable-gcc-warnings or when building from git and not using --disable-gcc-warnings.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |