Your message dated Wed, 30 Dec 2009 00:13:26 +0100 with message-id <4B3A8D16.5080102@debian.org> and subject line Re: Bug#561245: Missing include files give error message but return code 0. has caused the Debian Bug report #561245, regarding Missing include files give error message but return code 0. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 561245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561245 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Missing include files give error message but return code 0.
- From: Thomas Jahns <jahns@dkrz.de>
- Date: Tue, 15 Dec 2009 14:21:02 +0100
- Message-id: <4B278D3E.6000602@dkrz.de>
Package: gfortran-4.4 Version: 4.4.2-5 When compiling a test program containing only an include, the compiler does not fail when not finding the include as it should: $ cat testinclude.f90 program testinc include 'notthere.inc' print *, 'I''m running although I shouldn''t even compile.' end program $ gfortran-4.4 -o testinclude testinclude.f90 testinclude.f90:2: Error: Can't open included file 'notthere.inc' $ echo $? 0 $ ./testinclude I'm running although I shouldn't even compile. The expected result of echo $? in the above case is of course 1 and no binary should have been produced. I tested this on amd64 with gfortran-4.4 version 4.4.2-3 and 4.4.2-5. I'm currently back to gfortran-4.3 which shows the expected behaviour: $ gfortran-4.3 -o testinclude testinclude.f90 Error: Can't open included file 'notthere.inc' $ echo $? 1 The bug is particularly annoying because it breaks many autoconf-style tests. Greetings, Thomas -- Thomas Jahns DKRZ GmbH, Department: Application software Deutsches Klimarechenzentrum Bundesstraße 55 D-20146 Hamburg Phone: +49-40-460094-151 Fax: +49-40-460094-270 Email: Thomas Jahns <jahns@dkrz.de>Attachment: smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---
--- Begin Message ---
- To: Thomas Jahns <jahns@dkrz.de>, 561245-done@bugs.debian.org
- Subject: Re: Bug#561245: Missing include files give error message but return code 0.
- From: Matthias Klose <doko@debian.org>
- Date: Wed, 30 Dec 2009 00:13:26 +0100
- Message-id: <4B3A8D16.5080102@debian.org>
- In-reply-to: <4B278D3E.6000602@dkrz.de>
- References: <4B278D3E.6000602@dkrz.de>
Version: 4.4.2-8 fixed. On 15.12.2009 14:21, Thomas Jahns wrote:Package: gfortran-4.4 Version: 4.4.2-5 When compiling a test program containing only an include, the compiler does not fail when not finding the include as it should: $ cat testinclude.f90 program testinc include 'notthere.inc' print *, 'I''m running although I shouldn''t even compile.' end program $ gfortran-4.4 -o testinclude testinclude.f90 testinclude.f90:2: Error: Can't open included file 'notthere.inc' $ echo $? 0 $ ./testinclude I'm running although I shouldn't even compile. The expected result of echo $? in the above case is of course 1 and no binary should have been produced. I tested this on amd64 with gfortran-4.4 version 4.4.2-3 and 4.4.2-5. I'm currently back to gfortran-4.3 which shows the expected behaviour: $ gfortran-4.3 -o testinclude testinclude.f90 Error: Can't open included file 'notthere.inc' $ echo $? 1 The bug is particularly annoying because it breaks many autoconf-style tests. Greetings, Thomas
--- End Message ---