[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Re: can't install packages because Octave is using clang instead of
Re: Re: can't install packages because Octave is using clang instead of homebrew gcc (MacOS)
Sun, 16 Jun 2019 11:48:20 -0700
So it turns out the root of the problem was some corrupted stuff in in
I recently got a new computer and transferred the old files using the standard
apple data migration tool, but it broke my homebrew.
I nuked /usr/local/include and reinstalled octave and now I can get octavos
epkg installs fine with apple’s builtin clang.
Thanks so much for your help!
> On Jun 16, 2019, at 9:00 AM, address@hidden wrote:
> On Sat, Jun 15, 2019 at 19:12:12 -0700, David Lowenfels wrote:
>> Thanks Mike. The variables set in ~/.bashrc don't seem to be
>> propagating into octave shell environment... any other suggestions?
> I guess that depends how you are starting Octave.
> If you are running Octave from a bash shell command line, try the
> following instead
> ## at the bash prompt
> export CC=gcc-9
> export CXX=g++-9
> ## now at the Octave prompt
> getenv CC
> getenv CXX
> mkoctfile -p CC
> mkoctfile -p CXX
> system ('touch dummy.cc');
> mkoctfile -v dummy.cc
> If that works, then it's just a matter of making sure the environment
> variables are set in the right startup files.