After reinstalling fortran following the instructions for th R Tools
implementation
on http://www.webmo.net/support/fortran_osx.html
The fortran test examples now woe.
But I am getting another set or errors (after updating from git)
6 expected failures
10 unexpected results:
FAILED test-org/
Neuwirth Erich writes:
> I do (of course) have /bin/bash and the error is produced by bash.
OK, so the linebreaks have been corrupted in your original post. You
actually got two error messages it seems:
>>> i686-apple-darwin11-gfortran-4.2.1: error trying to exec 'cc1':
>>> execvp: No such file
The private reply was not intended.
I checked.
I do (of course) have /bin/bash
and the error is produced by bash.
It seems that the test suite does not find cc1 on Mountain Lion.
cc1 in installed byXCode, but PATH does not include the directory with cc1.
So I will try to add it there and report aga
Hi Eric,
Eric Schulte writes:
> The `org-test-load' function, which loads of all of the test files,
> catches these missing-test-dependency signals and for each one it
> creates a dummy test that fails but is expected to fail. These tests
> serve to indicate to the user that there are tests whi
Neuwirth Erich univie.ac.at> writes:
> Are the tests supposed to work only from within Emacs?
No, but you might be in a better position to tell us what went wrong, as you
still haven't shown what error you are getting from the tests in question.
So could you please go into the org directory and
I do have gfortran
Mahler:org-mode neuwirth$ whereis gfortran
/usr/bin/gfortran
Version information
Mahler:org-mode neuwirth$ gfortran
i686-apple-darwin11-gfortran-4.2.1: no input files
And it is in emacs' exec-path
exec-path
("/usr/bin" "/bin" "/usr/sbin" "/sbin"
"/Applications/Emacs.app/Conten
Bastien writes:
> Eric Schulte writes:
>
>> `org-test-for-executable' signals it's own error, but if we
>> changed `org-test-for-executable' to return a boolean and then used your
>> example above it would be more readable.
>
> Perhaps -- what I mean is that if (org-test-for-executable "python")
Eric Schulte writes:
> `org-test-for-executable' signals it's own error, but if we
> changed `org-test-for-executable' to return a boolean and then used your
> example above it would be more readable.
Perhaps -- what I mean is that if (org-test-for-executable "python")
signal a missing dependanc
Bastien writes:
> Eric Schulte writes:
>
>> Bastien writes:
>>
>>> Eric Schulte writes:
>>>
Hmm, these tests should only be run if the "gfortran" executable is in
your path.
>>>
>>> So let's take them out of the test suite when gfortran is not present?
>>
>> That is what we do curr
Eric Schulte writes:
> Bastien writes:
>
>> Eric Schulte writes:
>>
>>> Hmm, these tests should only be run if the "gfortran" executable is in
>>> your path.
>>
>> So let's take them out of the test suite when gfortran is not present?
>
> That is what we do currently, or at least that is what
Bastien writes:
> Eric Schulte writes:
>
>> Hmm, these tests should only be run if the "gfortran" executable is in
>> your path.
>
> So let's take them out of the test suite when gfortran is not present?
That is what we do currently, or at least that is what we're supposed to
be doing current
Eric Schulte writes:
> Hmm, these tests should only be run if the "gfortran" executable is in
> your path.
So let's take them out of the test suite when gfortran is not present?
--
Bastien
>
> I can't reproduce this on my Emacs.
>
> GNU Emacs 24.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.10)
> of 2012-07-26 on myhost
>
>> 7 unexpected results:
>>FAILED ob-fortran/command-arguments
>>FAILED ob-fortran/fortran-var-program
>>FAILED ob-fortran/input-var
>>FAILED ob
Neuwirth Erich univie.ac.at> writes:
> 7 unexpected results:
>FAILED ob-fortran/command-arguments
>FAILED ob-fortran/fortran-var-program
>FAILED ob-fortran/input-var
>FAILED ob-fortran/list-var
>FAILED ob-fortran/list-var-from-table
>FAILED ob-fortran/preprosessor-var
Hi Erich,
yes, it does make sense to report such errors as they may be related to
your architecture/installation -- and developers cannot test all possible
architectures/installations.
Neuwirth Erich writes:
> I am regularly building org mode on my Mac.
> I do not pretend to bean experienced Em
I am regularly building org mode on my Mac.
I do not pretend to bean experienced Emacs programmer, but I am will it to help
if I can contribute.
This is what I get when I run
make test
on the current source.
Ran 314 tests, 307 results as expected, 7 unexpected (2012-08-01 16:06:02+0200)
5 expect
16 matches
Mail list logo
