Your message dated Sat, 03 Jan 2009 23:02:03 +0000 with message-id <e1ljfvl-0006vo...@ries.debian.org> and subject line Bug#508565: fixed in libf2c2 20061008-4.1 has caused the Debian Bug report #508565, regarding f2c: does not translate properly in EMT64 machines 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 ow...@bugs.debian.org immediately.) -- 508565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Subject: f2c: does not translate properly in EMT64 machines Package: f2c Version: 20050501-1 Severity: grave Justification: renders package unusable *** Please type your report below this line *** I use a combination of f2c and gcc compilations to compile and then execute a C program which uses a fotran 77 subroutine. The sequence is simple: 1) I execute the script containing: f2c -f coeff_rot_nadl_juan.f gcc -c -O5 coeff_rot_nadl_juan.c 2) Then I compile and main program and executes it using: gcc -o filou_exe -O5 oscillations.c coeff_rot_nadl_juan.o -lm -lf2c\ && filou_exe where the fortran routine is "coeff_rot_nadl_juan.f", and the main program (written in C) is "oscillations.c" This works properly in my i386 machine (with ETCH), but it doesn't in my amd64 machine. In amd64 case: (1) and (2) compiles with no errors (and no warnings neither), but it crashes when I execute the program (i.e. when I execute filou_exe) The errors produced are: " structure input model type: CESAM5.* fmt: read unexpected character apparent state: unit 37 named gr1r_s3.osc last format: (4i10) lately reading sequential formatted external IO Aborted " The errors are all referred to readout an ASCII file ("gr1r_s3.osc") containing both numbers and strings (with scientific formats) So it seems that there is a problem when translating to C or when compling with gcc this translated into C code. Thanks! JC -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-amd64 Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages f2c depends on: ii libc6 2.3.6.ds1-13etch7 GNU C Library: Shared libraries pn libf2c2-dev <none> (no description available) Versions of packages f2c recommends: ii gcc 4:4.1.1-15 The GNU C compiler -- no debconf information
--- End Message ---
--- Begin Message ---Source: libf2c2 Source-Version: 20061008-4.1 We believe that the bug you reported is fixed in the latest version of libf2c2, which is due to be installed in the Debian FTP archive: libf2c2-dev_20061008-4.1_amd64.deb to pool/main/libf/libf2c2/libf2c2-dev_20061008-4.1_amd64.deb libf2c2_20061008-4.1.diff.gz to pool/main/libf/libf2c2/libf2c2_20061008-4.1.diff.gz libf2c2_20061008-4.1.dsc to pool/main/libf/libf2c2/libf2c2_20061008-4.1.dsc libf2c2_20061008-4.1_amd64.deb to pool/main/libf/libf2c2/libf2c2_20061008-4.1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 508...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Evgeni Golov <sarge...@die-welt.net> (supplier of updated libf2c2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sat, 03 Jan 2009 03:41:30 +0100 Source: libf2c2 Binary: libf2c2 libf2c2-dev Architecture: source amd64 Version: 20061008-4.1 Distribution: unstable Urgency: low Maintainer: Alan Bain <af...@debian.org> Changed-By: Evgeni Golov <sarge...@die-welt.net> Description: libf2c2 - Shared libraries for use with FORTRAN applications libf2c2-dev - Development libraries for use with f2c Closes: 442018 508565 Changes: libf2c2 (20061008-4.1) unstable; urgency=low . * Non-maintainer upload. * Don't sed away long on alpha and ia64, that was an ugly hack. * Instead add some ifdefs to f2c.h so we catch all archs where a long is 8 bytes and use only int there (make sure not to break other architectures by keeping long int there). Update README.debian accordingly. Also update f2c.h0 and f2c_master.h, so the files match, even if they are unused. Closes: #442018, #508565. * Clean debian/*.debhelper.log. Checksums-Sha1: c7bdd168e6f582bdc34ff92ca88dcb2aa2751680 980 libf2c2_20061008-4.1.dsc 6ae8a4a9f1341be89f93b74492f530ba13be227e 60471 libf2c2_20061008-4.1.diff.gz 7e5b1d8ce7671eda4ee29fe1ade0c724b8beb271 476998 libf2c2-dev_20061008-4.1_amd64.deb febd228daf93f76823145cbfcbc3d5a2820c65ce 158832 libf2c2_20061008-4.1_amd64.deb Checksums-Sha256: 55f805311754ff8f8eb7a0f1053775efee1c58bf297658b2d849d2aa56ca9817 980 libf2c2_20061008-4.1.dsc 3878fe559c046d2b7d8795e33281b81ed7b75e13a4c63e6e40927876f2bf0869 60471 libf2c2_20061008-4.1.diff.gz 7a412f15e782ae0fcabaecfa289edef67caaa7e38f7d7129d873d2611c132fdd 476998 libf2c2-dev_20061008-4.1_amd64.deb cbd63faa7a48e88056f3b6fb43113a49290b5ad1a63411b47e56b0fa90118fa3 158832 libf2c2_20061008-4.1_amd64.deb Files: fb3ff8dc35e105c9ed7da1304b5c0a51 980 devel optional libf2c2_20061008-4.1.dsc 6ba584e7a3748e4f8d0c93582d8b2b94 60471 devel optional libf2c2_20061008-4.1.diff.gz 6bf952736e441f3707d412c5cbcc2b91 476998 libdevel optional libf2c2-dev_20061008-4.1_amd64.deb dab3900424b71e066f400dcfe658c32a 158832 libs optional libf2c2_20061008-4.1_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAklf7FIACgkQeGfVPHR5Nd1ERwCeIPtzFeYiBdhGifYqUnH3souc Ri8AoLyNYjYcRJ9rLe7Gfk0Ds7gxyQSf =300Q -----END PGP SIGNATURE-----
--- End Message ---
