[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44346] configure summary shows OpenMP enabled

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #44346] configure summary shows OpenMP enabled even if not detected
Date: Mon, 23 Feb 2015 14:05:43 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.111 Safari/537.36

Follow-up Comment #7, bug #44346 (project octave):

Should we move this discussion somewhere else?

I think John's point was that appending to the user's flags in configure is
not a problem, but the user can then run "make CFLAGS='whatever' and the flags
that were appended could get lost. The plain CFLAGS and CXXFLAGS are
theoretically _supposed_ to be untouched so the user can set them to whatever
they want, and the project puts necessary flags in the AM versions.

I think it would be interesting to see if we could move all flags to
AM_*FLAGS, including the pthreads flag, the warning flags, OpenMP, etc. John
mentioned XTRA_* were used for legacy reasons, could we consolidate those uses
also and eliminate those xtra variables?

Would the fact that the pthreads flag is needed early not still be valid if it
were in AM_CFLAGS? I think the "early" just means the line number in

And as for Fortran, I think it would be useful, for users to potentially build
OpenMP extensions to Octave in Fortran if they like. I already tried that,
though, and the test fails with gfortran for F77, so presumably it only works
in Fortran 90 or newer standards. So that's not possible unless we use FC
instead of F77 (there was a discussion about that some time ago).


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]