[Scons-dev] FORTRAN tests failing in SCons latest
William Blevins
wblevins001 at gmail.com
Thu Oct 1 11:28:52 EDT 2015
At least according to the GNU docs, gfortran has legacy support for F77.
On Thu, Oct 1, 2015 at 4:16 PM, Bill Deegan <bill at baddogconsulting.com>
wrote:
> Sounds like when u run gfortran as f77 it realizes it should respect
> Fortran 77 syntax and behaves differently and thus the error.
> So it's likely a real error which none of our build slaves are picking up
> on, but not sure until I can install f77 on one of my systems to verify.
>
> -Bill
> p.s. I wouldn't remove a symlink on your system, unless you manually put
> it there in the first place... But then I'm also not sure where the symlink
> came from..
>
>
> On Thu, Oct 1, 2015 at 11:13 AM, William Blevins <wblevins001 at gmail.com>
> wrote:
>
>> removing the etc-alternatives configuration for f77 seemed to resolve the
>> issue. Might be an issue with the gfortran packaging.
>>
>> On Thu, Oct 1, 2015 at 3:57 PM, William Blevins <wblevins001 at gmail.com>
>> wrote:
>>
>>> I can disable f77, but it must have happened by default on the package
>>> installtion. I didn't do it explicitly.
>>>
>>> On Thu, Oct 1, 2015 at 3:53 PM, William Blevins <wblevins001 at gmail.com>
>>> wrote:
>>>
>>>> I get "dpkg-query: no path found matching pattern /usr/bin/f77".
>>>>
>>>> That was the first thing I looked at after doing: "which f77".
>>>>
>>>> /usr/bin/f95 gives me the same result; since those links point to
>>>> /etc/alternatives, this is expected I think?
>>>>
>>>> On Thu, Oct 1, 2015 at 3:42 PM, Bill Deegan <bill at baddogconsulting.com>
>>>> wrote:
>>>>
>>>>> Can you run:
>>>>> dpkg -S /usr/bin/f77
>>>>> ?
>>>>> Want to figure out what package this comes from?
>>>>> I'm running
>>>>> bdbaddog at hpmicrodog:~/scons/scons$ lsb_release -a
>>>>> No LSB modules are available.
>>>>> Distributor ID: Ubuntu
>>>>> Description: Ubuntu 14.04.3 LTS
>>>>> Release: 14.04
>>>>> Codename: trusty
>>>>> bdbaddog at hpmicrodog:~/scons/scons$ cat /etc/debian_version
>>>>> jessie/sid
>>>>>
>>>>> And I don't get a f77 symlink.. only f95
>>>>>
>>>>> -Bill
>>>>>
>>>>> On Thu, Oct 1, 2015 at 10:37 AM, William Blevins <
>>>>> wblevins001 at gmail.com> wrote:
>>>>>
>>>>>> Debian 8
>>>>>>
>>>>>> GNU Fortran 4.9.2
>>>>>>
>>>>>> On Thu, Oct 1, 2015 at 3:37 PM, William Blevins <
>>>>>> wblevins001 at gmail.com> wrote:
>>>>>>
>>>>>>> It looks like "/usr/bin/f[77|95]" -> "/etc/alternatives/f[77|95]" ->
>>>>>>> "/usr/bin/gfortran".
>>>>>>>
>>>>>>> On Thu, Oct 1, 2015 at 3:24 PM, Bill Deegan <
>>>>>>> bill at baddogconsulting.com> wrote:
>>>>>>>
>>>>>>>> Looks like it's running f77 as the command line?
>>>>>>>> Can you run "which f77" on your system?
>>>>>>>> What distro/version are you running? (Linux right?)
>>>>>>>>
>>>>>>>> -Bill
>>>>>>>>
>>>>>>>> On Thu, Oct 1, 2015 at 9:21 AM, William Blevins <
>>>>>>>> wblevins001 at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Looks like SHFORTRANFLAGS = '-x' is somehow getting converted to
>>>>>>>>> "-Ix".
>>>>>>>>>
>>>>>>>>> Not a Fortran expert. I just happened to notice when I was
>>>>>>>>> running my test suites. Tried to have as many tools working as possible
>>>>>>>>> when I was regression testing the CL support.
>>>>>>>>>
>>>>>>>>> V/R,
>>>>>>>>> William
>>>>>>>>>
>>>>>>>>> On Thu, Oct 1, 2015 at 2:18 PM, William Blevins <
>>>>>>>>> wblevins001 at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> wblevins at debian:~/SCons/scons_20150323$ ./runtest.py
>>>>>>>>>> test/Fortran/SHFORTRANFLAGS.py
>>>>>>>>>> 1/1 (100.00%) /usr/bin/python -tt test/Fortran/SHFORTRANFLAGS.py
>>>>>>>>>> STDOUT
>>>>>>>>>> =========================================================================
>>>>>>>>>> scons: Reading SConscript files ...
>>>>>>>>>> scons: done reading SConscript files.
>>>>>>>>>> scons: Building targets ...
>>>>>>>>>> /usr/bin/python wrapper.py f77 -o bar.os -c -fPIC -Ix bar.f
>>>>>>>>>> gfortran -o bar/libbar.so -shared bar.os
>>>>>>>>>> scons: done building targets.
>>>>>>>>>>
>>>>>>>>>> STDERR
>>>>>>>>>> =========================================================================
>>>>>>>>>> 0a1
>>>>>>>>>> > Warning: Nonexistent include directory "x"
>>>>>>>>>> FAILED test of
>>>>>>>>>> /home/wblevins/SCons/scons_20150323/src/script/scons.py
>>>>>>>>>> at line 611 of
>>>>>>>>>> /home/wblevins/SCons/scons_20150323/QMTest/TestCommon.py (_complete)
>>>>>>>>>> from line 701 of
>>>>>>>>>> /home/wblevins/SCons/scons_20150323/QMTest/TestCommon.py (run)
>>>>>>>>>> from line 390 of
>>>>>>>>>> /home/wblevins/SCons/scons_20150323/QMTest/TestSCons.py (run)
>>>>>>>>>> from line 133 of test/Fortran/SHFORTRANFLAGS.py
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, Oct 1, 2015 at 2:15 PM, William Blevins <
>>>>>>>>>> wblevins001 at gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> It is with default latest.
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Oct 1, 2015 at 2:08 PM, William Blevins <
>>>>>>>>>>> wblevins001 at gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I think I only have gfortran installed.
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Oct 1, 2015 at 1:46 PM, Bill Deegan <
>>>>>>>>>>>> bill at baddogconsulting.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> William,
>>>>>>>>>>>>>
>>>>>>>>>>>>> This is with the default branch?
>>>>>>>>>>>>> Installing g77 should be sufficient right?
>>>>>>>>>>>>>
>>>>>>>>>>>>> -Bill
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Oct 1, 2015 at 7:39 AM, William Blevins <
>>>>>>>>>>>>> wblevins001 at gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Just as a heads up, the FORTRAN tests are failing on my linux
>>>>>>>>>>>>>> box with the gfortran toolchain in case the CI servers don't have all the
>>>>>>>>>>>>>> toolchains.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> test/FORTRAN/F77FLAGS.py
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> test/FORTRAN/FORTRANFLAGS.py
>>>>>>>>>>>>>>> test/FORTRAN/SHF77FLAGS.py
>>>>>>>>>>>>>>> test/FORTRAN/SHFORTRANFLAGS.py
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> V/R,
>>>>>>>>>>>>>> William
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> Scons-dev mailing list
>>>>>>>>>>>>>> Scons-dev at scons.org
>>>>>>>>>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> Scons-dev mailing list
>>>>>>>>>>>>> Scons-dev at scons.org
>>>>>>>>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Scons-dev mailing list
>>>>>>>>> Scons-dev at scons.org
>>>>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Scons-dev mailing list
>>>>>>>> Scons-dev at scons.org
>>>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Scons-dev mailing list
>>>>>> Scons-dev at scons.org
>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Scons-dev mailing list
>>>>> Scons-dev at scons.org
>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>>>
>>>>>
>>>>
>>>
>>
>> _______________________________________________
>> Scons-dev mailing list
>> Scons-dev at scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>>
>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20151001/e4227be4/attachment.html>
More information about the Scons-dev
mailing list