headers
Neuwirth Erich | 4 Aug 2012 09:10
Picon
Picon
Favicon

Re: make test on Mac

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 again.
Any further suggestions?

On Aug 3, 2012, at 10:32 PM, ASSI <Stromeko <at> nexgo.de> wrote:

> [It looks you sent this mail to me rather than the list, so my reply is 
> private as well.  I'd prefer to keep the discussion on-list.]
> 
> On Thursday 02 August 2012, 09:05:52, Neuwirth Erich wrote:
>> i686-apple-darwin11-gfortran-4.2.1: error trying to exec 'cc1': execvp: No
>> such file or directory /bin/bash:
>> /var/folders/cl/zktxb0v51ng7jfv0mspj2w940000gn/T/babel-9230sRi/fortran-bi
>> n-9230CSz: Permission denied
>> 
>> So I see this is a problem with gcc.
> 
> Maybe, but it rather seems that actually it is expecting to find /bin/bash, 
> but comes up empty.
> 
>> But gfortran is running on my machine.
> 
> "Running" meaning what exactly?  From the above it doesn't appear it might 
> actually work when you tried to start it from the command line.
>
(Continue reading)

Permalink | Reply |
headers
Achim Gratz | 4 Aug 2012 10:05
Picon

Re: make test on Mac

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 or directory

This is the gfortran frontend telling you that it doesn't find its own
compiler backend…

>>> /bin/bash:
>>> /var/folders/cl/zktxb0v51ng7jfv0mspj2w940000gn/T/babel-9230sRi/fortran-bi
>>> n-9230CSz: Permission denied

…and this is bash telling you that no executable was produced, which is
explained by the first error message.

> It seems that the test suite does not find cc1 on Mountain Lion.

The test suite does not even look for that file, it is part of the
compiler.  This seems to be a problem with the installation of your
compiler(s), but Org can't do anything about it.  Just do

$ make TMPDIR=`pwd` TEST_NO_AUTOCLEAN=1 test
$ cd tmp-orgtest

and try to compile any of the (non-empty) *.F90 files you'll find there.
(Continue reading)

Permalink | Reply |

Gmane