GNU bug report logs - #9064
coreutils-8.12 compiler warning

Previous Next

Package: coreutils;

Reported by: "Joachim Schmitz" <jojo <at> schmitz-digital.de>

Date: Wed, 13 Jul 2011 07:57:01 UTC

Severity: normal

Done: Pádraig Brady <P <at> draigBrady.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: "Joachim Schmitz" <jojo <at> schmitz-digital.de>
Subject: bug#9064: closed (Re: bug#9064: coreutils-8.12 compiler warning)
Date: Wed, 13 Jul 2011 09:35:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#9064: coreutils-8.12 compiler warning

which was filed against the coreutils package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 9064 <at> debbugs.gnu.org.

-- 
9064: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9064
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Pádraig Brady <P <at> draigBrady.com>
To: Joachim Schmitz <jojo <at> schmitz-digital.de>
Cc: 9064-done <at> debbugs.gnu.org
Subject: Re: bug#9064: coreutils-8.12 compiler warning
Date: Wed, 13 Jul 2011 10:32:44 +0100
On 13/07/11 10:13, Joachim Schmitz wrote:
> Double backet does not fix this warning. It is the HP NonStop c89 and c99
> compiler without having disabled warnings (all warnings are on by default)
> If it isn't a bug, forget about it, or maybe add a comment next to that line
> about this.
> 
> -----Original Message-----
> From: Pádraig Brady [mailto:P <at> draigBrady.com] 
> Sent: Wednesday, July 13, 2011 11:05 AM
> To: Joachim Schmitz
> Cc: 9064 <at> debbugs.gnu.org
> Subject: Re: bug#9064: coreutils-8.12 compiler warning
> 
> On 13/07/11 08:55, Joachim Schmitz wrote:
>> I found this in mktemp.c, line344 (well, my compiler found it for me 
>> and warned about 'possible use of "=" where "==" was intended'):
>>
>>       if (!dry_run && (stdout_closed = true) && close_stream (stdout) 
>> != 0)
>>
>> Not sure whether this is bug or feature ;-)
> 
> Well it's a feature.
> We could reorganize but it would add a few more lines.
> What compiler (option) is this?
> Is the warning avoided by using double brackets like ((stdout_closed =
> true))

I also notice SGI's compiler has similar issues
http://archive.apache.org/gnats/2528

closing this.

cheers,
Pádraig.

[Message part 3 (message/rfc822, inline)]
From: "Joachim Schmitz" <jojo <at> schmitz-digital.de>
To: <bug-coreutils <at> gnu.org>
Subject: RE: coreutils-8.12 compiler warning
Date: Wed, 13 Jul 2011 09:55:51 +0200
I found this in mktemp.c, line344 (well, my compiler found it for me and
warned about 'possible use of "=" where "==" was intended'):

      if (!dry_run && (stdout_closed = true) && close_stream (stdout) != 0)

Not sure whether this is bug or feature ;-)

Bye, Jojo





This bug report was last modified 14 years and 44 days ago.

Previous Next


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