When I try to generate a plot, I receive the following message:
Fontconfig error: Cannot load default config file
warning: could not match any font: *-normal-normal-10
warning: called from
axes at line 66 column 10
gca at line 58 column 9
newplot at line 148 column 8
surf at line 70 column 9
sombrero at line 65 column 5
Then I received a series of the following messages:
warning: ft_render: unable to load appropriate font
warning: could not match any font: *-normal-normal-10
Usually the plot will appear once, but if I type again Phone, Octave will exit the following message.
panic: Segmentation fault: 11 - stopping myself...
attempting to save variables to'octave-workspace'...
warning: unable to open'octave-workspace' for writing...
warning: called from
__gnuplot_drawnow__>gnuplot_trim_term at line 368 column 10
__gnuplot_drawnow__>gnuplot_set_term at line 119 column 20
__gnuplot_drawnow__ at line 84 column 16
Segmentation fault: 11
When discussing similar errors, I often see references to /etc/fonts/fonts.conf. My /etc directory does not contain the fonts subdirectory. This may be the source of the problem, but I don’t know how to solve it. When I run and brew install fontconfig, I get a warning: fontconfig-2.11.1_1 is already installed. When I run sudo find / -name fonts.conf, I get /opt/X11/lib/X11/fontconfig/fonts.conf.
The brewing doctor produced the following warning, which may be related, which I don’t know how to solve (missing to uninstall Anaconda):
Warning: Anaconda is known to frequently break Homebrew builds, including Vim
and MacVim, due to bundling many duplicates of system and Homebrew-available
tools.
If you encounter a build failure please temporarily remove Anaconda
from your $PATH and attempt the build again prior to reporting the
failure to us. Thanks!
Warning: "config" scripts exist outside your system or Homebrew directories.< br />`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.
Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:
/Users/greg/anaconda/bin/curl-config
/Users/greg/anaconda/b in/freetype-config
/Users/greg/anaconda/bin/libdynd-config
/Users/greg/anaconda/bin/libpng-config
/Users/greg/anaconda/bin/ libpng16-config
/Users/greg/anaconda/bin/python-config
/Users/greg/anaconda/bin/python2-config
/Users/greg/anaconda/bin/python2. 7-config
/Users/greg/anaconda/bin/xml2-config
/Users/greg/anaconda/bin/xslt-config
I am running OS X 10.11.3 (El Capitan).
In order to work properly, you need to set a manual path for fontconfig, so it will not look for fonts in inappropriate directories (/etc/fonts is for Linux installations, but OS X XQuartz can turn To a different location).
You should run the command export FONTCONFIG_PATH = / opt / X11 / lib / X11 / fontconfig to set fontconfig the correct way. In addition, you can also add the line export FONTCONFIG_PATH=/opt/X11/lib/X11/fontconfig to ~/.bash_profile, and then restart the terminal so that you don’t need to run this command again.
I installed Octave through Homebrew and used the instructions here.
When I try to generate a plot, I receive the following message:
Fontconfig error: Cannot load default config file
warning: could not match any font: *-normal-normal-10
warning: called from
axes at line 66 column 10
gca at line 58 column 9
newplot at line 148 column 8
surf at line 70 column 9
sombrero at line 65 column 5
Then I received a series of the following messages:
warning: ft_render: unable to load appropriate font
warning: could not match any font: *-normal-normal-10
Usually the plot will appear once, but if I type again Phone, Octave will exit the following message.
panic: Segmentation fault: 11 - stopping myself...
attempting to save variables to'octave-workspace'...
warning: unable to open'octave-workspace' for writing...
warning: called from
__gnuplot_drawnow__>gnuplot_trim_term at line 368 column 10
__gnuplot_drawnow__>gnuplot_set_term at line 119 column 20
__gnuplot_drawnow__ at line 84 column 16
Segmentation fault: 11
When discussing similar errors, I often see references to /etc/fonts/fonts.conf. My /etc directory does not contain the fonts subdirectory. This may be the source of the problem, but I don’t know how to solve it. When I run and brew install fontconfig, I get a warning: fontconfig-2.11.1_1 is already installed. When I run sudo find / -name fonts.conf, I get /opt/X11/lib/X11/fontconfig/fonts.conf.
The brewing doctor produced the following warning, which may be related, which I don’t know how to solve (missing to uninstall Anaconda):
Warning: Anaconda is known to frequently break Homebrew builds, including Vim
and MacVim, due to bundling many duplicates of system and Homebrew-available
tools.
If you encounter a build failure please temporarily remove Anaconda
from your $PATH and attempt the build again prior to reporting the
failure to us. Thanks!
Warning: "config" scripts exist outside your system or Homebrew directories.< br />`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.
Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:
/Users/greg/anaconda/bin/curl-config
/Users/greg/anaconda/bin/ freetype-config
/Users/greg/anaconda/bin/libdynd-config
/Users/greg/anaconda/bin/libpng-config
/Users/greg/anaconda/bin/libpng16- config
/Users/greg/anaconda/bin/python-config
/Users/greg/anaconda/bin/python2-config
/Users/greg/anaconda/bin/python2.7- config
/Users/greg/anaconda/bin/xml2-config
/Users/greg/anaconda/bin/xslt-config
I am running OS X 10.11.3(El Capitan).
Actually, this is not Octave’s problem, but its complicated settings and misconfiguration of other utilities (especially fontconfig).
In order to work properly, you need to set a manual path for fontconfig, so it will not look for fonts in inappropriate directories (/etc/fonts is for Linux installations, but OS X XQuartz can turn To a different location).
You should run the command export FONTCONFIG_PATH = / opt / X11 / lib / X11 / fontconfig to set fontconfig the correct way. In addition, you can also add the line export FONTCONFIG_PATH=/opt/X11/lib/X11/fontconfig to ~/.bash_profile, and then restart the terminal so that you don’t need to run this command again.