[MOAB-dev] Disable fortran in moab-5.0.0

[Vijay S. Mahadevan]

> That makes sense.  I have just tested it quickly without the mangling option to configure and it worked fine.

Sounds good Paul. I saw your commits and PR for the CMake addition.
Will take a look at them today. We can just expose the variable for
FC_MANGLING just to be consistent in the option set.

And thanks for verifying the branch Lorenzo. I'll make sure to test
this combination with the --download-* options.

Vijay

On Thu, Nov 16, 2017 at 3:57 AM, Lorenzo Botti <bottilorenzo at gmail.com> wrote:
> Thank you very much Vijay. It worked.
> To me this setup is really helpful.
>
> Just a note. The disable fortran option should be taken into account also on
> the hdf5 build when configuring moab with download-hdf5. Otherwise that will
> fail.
>
> Hope that the new option will be included in future releases.
>
> Bests
> Lorenzo
>
>
> On Nov 15, 2017 2:58 AM, "Vijay S. Mahadevan" <vijay.m at gmail.com> wrote:
>>
>> Hi Lorenzo,
>>
>> Can you give the branch "vijaysm/osx-blas-lapack" a try on your
>> machines ? I've added several additional configure options to control
>> the mangling (when fortran is disabled), and an option to disable
>> BLAS/LAPACK (only if Eigen is present). A combination of:
>> --disable-blaslapack --with-eigen3 --with-fc-mangling-suffix="_"
>> should give you the right result. Let me know if this gives you the
>> result of not requiring a Fortran compiler.
>>
>> I will merge this branch to develop and run our buildbot tests on
>> various configuration combinations. Paul, I'll also make some
>> modifications to CMake if this approach is acceptable. Let me know.
>>
>> Iulian, any comments ?
>>
>> Vijay
>>
>> On Fri, Nov 10, 2017 at 5:14 PM, Vijay S. Mahadevan <vijay.m at gmail.com>
>> wrote:
>> > Paul, as Lorenzo mentioned, we need to modify configuration to enable
>> > this cross option. I can look into that as well.
>> >
>> > The more combinations/options we add, the more complicated the
>> > configuration becomes. While things do become seemingly flexible, I
>> > just want to make sure it doesn't become a maintenance nightmare later
>> > on. Hence the decision originally to just make BLAS/LAPACK mandatory
>> > and not allow Eigen (with/without external BLAS). The implication on
>> > FC here was a side effect unfortunately of that decision.
>> >
>> > Vijay
>> >
>> > On Fri, Nov 10, 2017 at 3:29 PM, Lorenzo Botti <bottilorenzo at gmail.com>
>> > wrote:
>> >> Dear Paul,
>> >> I don’t think it’s actually possible. The build system should be
>> >> modified to
>> >> account for such a configure option.
>> >> Anyway this is also what I need, a fix to run MOAB on OSX without
>> >> fortran.
>> >> On my laptop I’m not interested on performance but I do most of the
>> >> development.
>> >> Installing a fortran compiler on OSX is a pain, as far as I know this
>> >> forces
>> >> me to use gcc instead of clang.
>> >> Accordingly I would need to use a package manager like macports or
>> >> homebrew,
>> >> or to compile gcc myself.
>> >> A fallback on Eigen would be really welcome.
>> >>
>> >> Bests
>> >> Lorenzo
>> >>
>> >> On 10 Nov 2017, at 21:19, Paul Wilson <paul.wilson at wisc.edu> wrote:
>> >>
>> >> I'm not sure if I follow how to actually do what you are suggesting.
>> >> If I
>> >> wanted to rely on Eigen instead of both BLAS/LAPACK, is there a set of
>> >> options I can pass to either autoconf or CMAKE to do that?
>> >>
>> >>