#91 Build on MacOS X El Capitan

[Yuri Pimenov]

It appears that vecLib is deprecated in El Capitan as stated here https://github.com/Homebrew/homebrew-science/issues/1016#issuecomment-61399887

Replacing in configure.in by "Accelerate" works.

Additional notes for homebrew users:

• gettext must be linked: "brew link --force gettext" before build, --disable-nls just doesn't work and requires "locale.h" which can't be found
• Gnuplot must be compilled with cairo support: "brew reinstall gnuplot --with-cairo"
• Must provide "--without-readline" otherwise "gretlcli.c:430:5: error: use of undeclared identifier 'rl_done'"

[Sven Schreiber]

Am 29.01.2016 um 15:54 schrieb Yuri Pimenov:

It appears that vecLib is deprecated in El Capitan as stated here
https://github.com/Homebrew/homebrew-science/issues/1016#issuecomment-61399887

I don't quite understand the point. Is the build currently failing? Then
that would be a bug instead of a feature request (but don't worry, we
could change that). Or are you saying this "Accelerate" thing would be
simply better?

thanks,
sven

[Yuri Pimenov]

Seems that "vecLib" could just be replaced by "Accelerate" but that's just trivial. The real problem that MacOS build is broken.

I've tried to compile gretl on the system with homebrew installed. Whether it compiles on a vanila Mac OS X I don't know. I was able to succeed with compilation by disabling some features. For example, configure didn't find suitable NLS files but #ifdef NLS_ENABLED was set to true that led to #include "locale.h" which could not be found. I don't know whether it's configure's bug or gretl's. If I do autoconf it complains on missing M4 templates.

[Allin Cottrell]

I will get access to an El Capitan system and do some testing. On one
small point there's now a fix in git: I think --disable-nls should work
properly. Thanks for the heads-up on all this.

[Yuri Pimenov]

--disable-nls doesn't help

[Sven Schreiber]

Allin, on Feb 23rd you wrote something on the devel list about El Capitan, but I'm not quite sure it is directly related to the failing build. Is this issue fixed now and can be closed? If not, it would better belong in the Bugs tracker anyway.
thanks,
sven

[Sven Schreiber]

Given that this is almost two months ago now I kind of assume that the build problems have been resolved, but have they really? So that this can be closed?
thanks for any updates and hints,
sven

[Sven Schreiber]

OK, in the changelog of version 2016b from April there is an entry about fixed crashes on OS X, so I'm guessing/hoping that these issues are resolved. So I'm closing this. Please tell me if any problems still exist and we can reopen.