GNU bug report logs - #55010
Compiling from git clone

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 55010 in the body.
You can then email your comments to 55010 AT debbugs.gnu.org in the normal way.

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

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

From: Ken Ingram <ken.ingram <at> gmail.com>
To: bug-coreutils <at> gnu.org
Subject: Compiling from git clone
Date: Mon, 18 Apr 2022 14:47:39 -0700

[Message part 1 (text/plain, inline)]

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

[Message part 2 (text/html, inline)]

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

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Ken Ingram <ken.ingram <at> gmail.com>
Cc: 55010 <at> debbugs.gnu.org
Subject: Re: bug#55010: Compiling from git clone
Date: Tue, 19 Apr 2022 16:42:08 -0700

On 4/18/22 14:47, Ken Ingram wrote:
> 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)
>   ^~~~~~~~~~

I'm not seeing that on Fedora 35 x86-64, with GCC 11.2.1 20220127 (Red 
Hat 11.2.1-9). If you're using an older compiler, I suggest configuring 
with --disable-gcc-warnings, or building with "make WERROR_CFLAGS=", so 
that the unnecessary warnings don't break the build. If you're not, 
please specify the platform and GCC you're using, and how you ran 
'configure' and 'make'. Thanks.

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

From: Ken Ingram <ken.ingram <at> gmail.com>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 55010 <at> debbugs.gnu.org
Subject: Re: bug#55010: Compiling from git clone
Date: Tue, 19 Apr 2022 22:54:51 -0700

[Message part 1 (text/plain, inline)]

Debian 4.19.160-2 (2020-11-28) x86_64 GNU/Linux
gcc (Debian 8.3.0-6) 8.3.0

So I guess I'm on an "old" compiler compared to 11.2.1

On Tue, Apr 19, 2022 at 4:42 PM Paul Eggert <eggert <at> cs.ucla.edu> wrote:

> On 4/18/22 14:47, Ken Ingram wrote:
> > 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)
> >   ^~~~~~~~~~
>
> I'm not seeing that on Fedora 35 x86-64, with GCC 11.2.1 20220127 (Red
> Hat 11.2.1-9). If you're using an older compiler, I suggest configuring
> with --disable-gcc-warnings, or building with "make WERROR_CFLAGS=", so
> that the unnecessary warnings don't break the build. If you're not,
> please specify the platform and GCC you're using, and how you ran
> 'configure' and 'make'. Thanks.
>

[Message part 2 (text/html, inline)]

Message #18 received at 55010-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Ken Ingram <ken.ingram <at> gmail.com>
Cc: 55010-done <at> debbugs.gnu.org
Subject: Re: bug#55010: Compiling from git clone
Date: Wed, 20 Apr 2022 09:47:59 -0700

On 4/19/22 22:54, Ken Ingram wrote:
> So I guess I'm on an "old" compiler compared to 11.2.1

Yes, 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.

Message #21 received at 55010-done <at> debbugs.gnu.org (full text, mbox):

From: Ken Ingram <ken.ingram <at> gmail.com>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 55010-done <at> debbugs.gnu.org
Subject: Re: bug#55010: Compiling from git clone
Date: Wed, 20 Apr 2022 17:37:40 -0700

[Message part 1 (text/plain, inline)]

Thanks for the tip.

Everything compiled and I was able to get a current version of stat, so I
can use BirthTime.

I believe it's long past time to upgrade the system.

But like all old-timers comfortable in their ways, I've been resisting....

On Wed, Apr 20, 2022 at 9:48 AM Paul Eggert <eggert <at> cs.ucla.edu> wrote:

> On 4/19/22 22:54, Ken Ingram wrote:
> > So I guess I'm on an "old" compiler compared to 11.2.1
>
> Yes, 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.
>

[Message part 2 (text/html, inline)]

Previous Next

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