Bug 891029

Summary: [abrt] numpy-f2py-1.6.2-6.fc18: crackfortran.py:347:readfortrancode:Exception: readfortrancode: Found non-(space,digit) char in the first column.
Product: [Fedora] Fedora Reporter: Chuck Forsberg <caf>
Component: numpyAssignee: Gwyn Ciesla <gwync>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: gwync, jspaleta, orion, rdieter, sochotni, tomspur
Target Milestone: ---Flags: orion: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:be816ce20a1829acf25d5ebb568b75e5237ea0bd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:56:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: dso_list
none
File: environ none

Description Chuck Forsberg 2013-01-01 04:22:43 UTC
Description of problem:
Error occurred while compiling WSPR for Linux

Version-Release number of selected component:
numpy-f2py-1.6.2-6.fc18

Additional info:
cmdline:        python /usr/bin/f2py -c --quiet --noopt --debug -m w '--f77flags=-g -O2 -fno-range-check -ffixed-line-length-none             -Wall -Wno-character-truncation -Wno-conversion -Wtabs -fPIC -fbounds-check' '--f90flags=-g -O2 -fno-range-check -ffixed-line-length-none             -Wall -Wno-character-truncation -Wno-conversion -Wtabs -fPIC -fbounds-check' --fcompiler=gnu95 --f77exec=gfortran --f90exec=gfortran '--opt=-fbounds-check -g -O2 -fno-range-check -ffixed-line-length-none             -Wall -Wno-character-truncation -Wno-conversion -Wtabs -fPIC -fbounds-check' -I/usr/include -I/usr/local/include '-DPACKAGE_NAME=\"wspr\"' '-DPACKAGE_TARNAME=\"wspr\"' '-DPACKAGE_VERSION=\"1.11\"' '-DPACKAGE_STRING=\"wspr 1.11\"' '-DPACKAGE_BUGREPORT=\"\"' '-DFC_LIB_PATH=\"/usr/lib/gcc/x86_64-redhat-linux/4.7.2/\"' '-DFC=\"gfortran\"' -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_ERRNO_H=1 -DHAVE_SYS_SYSLOG_H=1 -DHAVE_STDDEF_H=1 -DHAVE_LIBGEN_H=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_WAIT_H=1 -DHAVE_STDIO_H=1 -DHAVE_TERMIOS_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_LINUX_PPDEV_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_FCNTL_H=1 -DHAVE_SYS_IOCTL_H=1 -DTIME_WITH_SYS_TIME=1 -DSTRING_WITH_STRINGS=1 -DNDEBUG=1 '-DFC_LIB_PATH=\"/usr/lib/gcc/x86_64-redhat-linux/4.7.2/\"' '-DFC=\"gfortran\"' -I. -L/usr/lib64 -L/usr/local/lib -L/usr/lib/gcc/x86_64-redhat-linux/4.7.2/ -lpthread -lportaudio -lfftw3f only: wspr1 getfile paterminate audiodev : wspr1.f90 wspr2.f90 decode.f90 getutc.f90 gran.f90 rx.f90 startdec.f90 startrx.f90 starttx.f90 tx.f90 getfile.f90 paterminate.f90 wqencode.f90 chklevel.f90 genwspr.f90 wqdecode.f90 hash.f90 packname.f90 packtext2.f90 unpackname.f90 unpacktext2.f90 audiodev.f90 fil1.f90 packpfx.f90 packprop.f90 unpackpfx.f90 unpackprop.f90 msgtrim.f90 thnix.f90 iqdemod.f90 phasetx.f90 speciq.f90 xcor162.f90 rxtxcoord.f90 mept162.f getrms.f wfile5.f mix162.f sync162.f decode162.f spec162.f set.f xfft.f ps162.f pctile.f peakup.f db.f inter_mept.f fano232.f unpack50.f unpackcall.f unpackgrid.f four2a.f flat3.f sort.f deg2grid.f ssort.f gencwid.f morse.f packcall.f packgrid.f pack50.f encode232.f nchar.f grid2deg.f fchisq.f ccf2.f twkfreq.f azdist.f geodist.f padevsub.c start_threads.c sound.c gmtime2.c ptt_unix.c nhash.c fthread.c
executable:     /usr/bin/f2py
kernel:         3.6.10-4.fc18.x86_64
uid:            2010

Comment 1 Chuck Forsberg 2013-01-01 04:22:49 UTC
Created attachment 670915 [details]
File: backtrace

Comment 2 Chuck Forsberg 2013-01-01 04:22:50 UTC
Created attachment 670916 [details]
File: core_backtrace

Comment 3 Chuck Forsberg 2013-01-01 04:22:52 UTC
Created attachment 670917 [details]
File: dso_list

Comment 4 Chuck Forsberg 2013-01-01 04:22:53 UTC
Created attachment 670918 [details]
File: environ

Comment 5 Orion Poplawski 2013-02-25 23:41:53 UTC
Can you try to reproduce with 1.7.0?

Comment 6 Fedora End Of Life 2013-12-21 15:16:19 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2014-02-05 22:56:36 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.