NetBSD Problem Report #50006

From dholland@netbsd.org  Sat Jun 27 19:30:27 2015
Return-Path: <dholland@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 461F1A65BB
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 27 Jun 2015 19:30:27 +0000 (UTC)
Message-Id: <20150627193026.C7B8714A2DA@mail.netbsd.org>
Date: Sat, 27 Jun 2015 19:30:26 +0000 (UTC)
From: dholland@netbsd.org
Reply-To: dholland@netbsd.org
To: gnats-bugs@gnats.NetBSD.org
Subject: stupid diagnostic message from gcc's cpp(1)
X-Send-Pr-Version: 3.95

>Number:         50006
>Category:       bin
>Synopsis:       stupid diagnostic message from gcc's cpp(1)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 27 19:35:00 +0000 2015
>Last-Modified:  Fri Jan 18 20:25:01 +0000 2019
>Originator:     David A. Holland
>Release:        NetBSD 7.99.17 and 7.0_RC1 (as of today)
>Organization:
>Environment:
System: NetBSD macaran 7.99.17 NetBSD 7.99.17 (MACARAN) #26: Fri May 22 18:22:29 EDT 2015  dholland@macaran:/usr/src/sys/arch/amd64/compile/MACARAN amd64
Architecture: x86_64
Machine: amd64
>Description:

   % cpp < .
   cc1: fatal error: stdout: No such file or directory
   compilation terminated.

similarly,

   % cpp .
   cc1: fatal error: .: No such file or directory
   compilation terminated.

Not only is it printing the wrong (probably uninitialized) errno, but
it's got its input and output mixed up.

>How-To-Repeat:

Run calendar -a from /etc/daily on a system where someone has a
~/.calendar directory, and discover a strange message in the daily
output.

>Fix:

Easy once someone goes and tracks down where in gcc the print is
coming from.

>Release-Note:

>Audit-Trail:

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: bin/50006: stupid diagnostic message from cpp(1)
Date: Sat, 27 Jun 2015 19:44:29 +0000

 On Sat, Jun 27, 2015 at 07:35:00PM +0000, dholland@netbsd.org wrote:
  > >Synopsis:       stupid diagnostic message from cpp(1)

 that's gcc's cpp, for the record.

 -- 
 David A. Holland
 dholland@netbsd.org

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: bin/50006: stupid diagnostic message from cpp(1)
Date: Fri, 18 Jan 2019 10:09:43 +0000

 On Sat, Jun 27, 2015 at 07:45:00PM +0000, David Holland wrote:
  >  On Sat, Jun 27, 2015 at 07:35:00PM +0000, dholland@netbsd.org wrote:
  >   > >Synopsis:       stupid diagnostic message from cpp(1)
  >  
  >  that's gcc's cpp, for the record.

 FWIW, gcc 6.4 still does this.

 -- 
 David A. Holland
 dholland@netbsd.org

From: matthew green <mrg@eterna.com.au>
To: gnats-bugs@NetBSD.org
Cc: gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, dholland@netbsd.org
Subject: re: bin/50006: stupid diagnostic message from cpp(1)
Date: Sat, 19 Jan 2019 07:23:16 +1100

 >   >   > >Synopsis:       stupid diagnostic message from cpp(1)
 >   >  
 >   >  that's gcc's cpp, for the record.
 >  
 >  FWIW, gcc 6.4 still does this.

 file a bug upstream?  i'd rather not fix this in our tree.


 .mrg.

>Unformatted:

Home	PR Database Search