Bug 21898 - f77 compiler problem
Summary: f77 compiler problem
Status: CLOSED DUPLICATE of bug 21426
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gcc
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-07 17:30 UTC by matthew jull
Modified: 2008-05-01 15:37 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2000-12-07 17:30:11 UTC


Attachments (Terms of Use)

Description matthew jull 2000-12-07 17:30:08 UTC
i've got a g77 compiler problem that also occurs with a demo
version of a commercial f77 compiler (Absoft). Even using a very simple 
program such as test.f :

      x=1.0
      write(*,*)x
      stop
      end

and compiling with f77  i get:

{menudo}/home/jull/toko/2por~> /usr/bin/f77 test.f
/usr/lib/gcc-lib/i386-redhat-linux/2.96/libg2c.a(open.o): In function
`f_open': open.o(.text+0x4e6): the use of `tempnam' is dangerous, better
use
`mkstemp'

       using f77 from a commercial Absoft demo compiler i get:

{menudo}/home/jull/toko/2por~> /usr/absoft/bin/f77 test.f
FORTRAN 77 Compiler 5.0, Copyright (c) 1987-2000, Absoft Corp.
This demonstration copy of Absoft Fortran 77 expires in 16 days.
/usr/absoft/lib/libfio.a(lowlevel.o): In function `_temp_file':
lowlevel.o(.text+0x10): the use of `tempnam' is dangerous, better use
`mkstemp'

the compiled program runs fine with either compiler, but i am
baffled why i should have this "warning" when compiling, other 
than to say that it looks like the compiler is using an older command 
(tempnam) to make a temporary file, while some
configuration files (or something) want it to use the more
up-to-date mkstemp command. 
    
Do you know how I could fix this problem? I use the fortran compiler
enough that it will be bothersome always having this message popping up and
I also wonder if it will have any impact on the numerical calculations
I am doing. My guess is that since it occurs with both compilers, it is not
a
compiler problem, but perhaps a library problem.

thanks,
		matthew-

p.s. i have all recent updates/patches to redhat 7 as of dec.7/2000.

Comment 1 matthew jull 2000-12-08 21:18:33 UTC

*** This bug has been marked as a duplicate of 21426 ***


Note You need to log in before you can comment on or make changes to this bug.