i try to add the libary jpggraph to my Debian Linux System with PHP 5.6.40 installed. I followed the installation manual from jpgrpah.net but get still the following error-message in the browser when starting a test program:
Catchable fatal error: Argument 1 passed to JpGraphException::defaultHandler() must be an instance of Throwable, instance of JpGraphExceptionL given in /usr/share/php/jpgraph/jpgraph_errhandler.inc.php on line 158
Does anyone have an idea what to do?
If you need further information like the php.ini or other coniguration files please tell me.
Best regards
Lars
I copied the extracted archive in /usr/share/jpgraph/
I followed the manual an made the changes in php.ini
I made changes recommended in the manual in the jpgraph-config.ini.php
I started an example program from jpgraph.net
I got the error message.
I checked all changes, if they match with the recommended changes in the manual.
I expected to see a graph in the browser window.
Related
Please forgive my naivete, this is my first attempt to compile any piece of software from source. I'm a long time user of the Handlersocket Plugin for Percona (MySQL) but they stopped including it after 5.6. I'm moving up to MySQL 8 and I'm trying to compile the Handlersocket plugin from source but I'm stumbling.
First off, I've downloaded the source for handlersocket (https://github.com/DeNA/HandlerSocket-Plugin-for-MySQL), and the source for MySQL Server 8.0.17 (https://github.com/mysql/mysql-server). I've unpacked handlersocket into the /source-downloads/ folder within the MySQL source, run the included ./autoconf.sh and then ./configure, but the latter is spouting errors...
checking mysql source... configure: error: --with-mysql-source=PATH is required for standalone build
I was able to adjust the call to ./configure --with-mysql-source=../.. but now it's returning an error regarding the binaray...
checking mysql binary... configure: error: mysql_config not found! You have to specify the directory where mysql_config resides to --with-mysql-bindir=PATH.
I tried searching for the mysql_config file anywhere in the source files (find ../.. -name "mysql_config") but it's not found anywhere, what am I missing? Is the file called something else? Is there something else I'm supposed to have downloaded? I do have MySQL installed already (via YUM/DNF), can I point this at something from the existing install?
I have attempted to install Psychtoolbox for Octave on Windows 10, per the installation instructions. Before the installation completes, I get this warning:
Screen() failed to work for some reason:
Check the troubleshooting instructions on our Wiki (Download section
and FAQ section, maybe also the Bugs section).
You may need to delete (or rename) the following DLL files in your Octave-4.4.1 installations
bin folder to make this work, then restart Octave:
C:\Octave\4.4.1\bin\libglib-2.0.0.dll
C:\Octave\4.4.1\bin\libgmodule-2.0.0.dll
C:\Octave\4.4.1\bin\opengl32.dll
Once you manage to fix the problem (simply type 'AssertOpenGL' to verify
that stuff works now), you do not need to run the installation routine again,
but can start working immediately.
I had already deleted the named DLL files, which I confirmed. I then ran AssertOpenGL and received this error:
Last Error: could not find library or dependencies: D:\Coding\PTB\Psychtoolbox\PsychBasic\Octave4WindowsFiles64\Screen.mex
Simply calling Screen directly gives this error:
error: library open failed: D:\Coding\PTB\Psychtoolbox\PsychBasic\Octave4WindowsFiles64\Screen.mex
However, the directory containing Screen.mex is at the very top of my path:
Octave's search path contains the following directories:
.
D:\Coding\PTB\Psychtoolbox\PsychBasic\Octave4WindowsFiles64
D:\Coding\PTB\Psychtoolbox
<etc>
As such, the solution to this similar question is of no use. What might I be able to do to correctly configure PTB on Octave?
What version of gstreamer are you using? I had a similar problem recently and fixed it by installing gstreamer 1.14.4. The latest version of gstreamer will not work, nor will versions earlier than 1.14.4.
I have downloaded the mysql-5.6.30.tar.gz source file, extracted and I'm using the following CMAKE command:
cmake /mysql-5.6.30 -DCMAKE_INSTALL_PREFIX=/usr/local/mysql -DWITH_CHARSET=CP1251=1
-DENABLE_THREAD_SAFE_CLIENT=1 -DMAX_INDEXES=250 -DDOWNLOAD_BOOST=1
-DWITH_BOOST=%HOME/mysqlboost -DENABLE_DOWNLOADS=1
Most of that is normal, apart from the MAX_INDEXES value of 250. The client has very specific requirements for this, and is the reason I am trying to compile this from source (there doesn't appear to be a way to change this value once MySQL is installed, must be done at compile).
CMake runs through the compilation (after i fixed various dependencies being missing and such), but at the end states:
-- Generating done
CMake Warning:
Manually-specified variables were not used by the project:
CMAKE_CC_COMPILER
DOWNLOAD_BOOST
ENABLE_THREAD_SAFE_CLIENT
MAX_INDEXES
WITH_BOOST
WITH_CHARSET
-- Build files have been written to: /mysql-5.6.30
This is a bit of an issue, as I specifically needed MAX_INDEXES to be written to the build files so I can install MySQL with it. Can anyone tell me A) Why is it ignoring every single variable I passed to it? and/or B) Is there any other way to enforce MAX_INDEXES (to at least 200) in a MySQL Installation. If it helps, it can be 5.6 or 5.7.
Thanks.
You can solve the MAX_INDEXES and ENABLE_THREAD_SAFE_CLIENT problem with this from the MySQL source directory (tested):
MY_FLAGS="DMAX_INDEXES=256 -DENABLE_THREAD_SAFE_CLIENT"
cmake -DCMAKE_C_FLAGS="$MY_FLAGS" -DCMAKE_CXX_FLAGS="$MY_FLAGS" .
The reason it ignored your variables was because they were not Cmake variables, but rather macros referenced by the source of MySQL (some).
The variables understood by Cmake are documented at https://dev.mysql.com/doc/refman/5.6/en/source-configuration-options.html
For the internal macros you have to search in the MySQL source.
According to mysql documentation on source configuration options, the configuration options you listed are eithes supported from a certain mysql v5.7 version or are not even listed on that page, meaning they are not mysql specific.
Compile a mysql v5.7.1 or higher from source to be able to set max_indexes config option.
I think it's a config error based on similar, but not identical answers to errors I found such as requirement 'fncache' not supported.
No idea where this is coming from, but it started happening AFTER the upgrade.
This is usually a problem with the server setup. It means the server does not return the expected answer.
Are you using static-http? (and please add the command line you are using when you get the error).
It seems that there is an old hg executable in your path. The error message comes when a client tries to acces a local repository which is created by a higher hg version.
The boring, necessary details: I'm on Snow Leopard running MySQL locally.
I'm trying to install the Sphinx engine for MySQL like so:
mysql> install plugin sphinx soname 'sphinx.so';
ERROR 1127 (HY000): Can't find symbol '_mysql_plugin_interface_version_' in library
I've Googled everywhere and can't seem to find an actual solution to this problem. For example this issue on the Sphinx forums seems unresolved. Someone else also raised this issue with similar results.
The first post linked to this O'Reilly article which says:
There is a common problem that might occur at this point:
ERROR 1127 (HY000): Can't find symbol '_mysql_plugin_interface_version_' in library
If you see a message like this, it is likely that you forgot to include the -DMYSQL_DYNAMIC_PLUGIN option when compiling the plugin. Adding this option to the g++ compile line is required to create a dynamically loadable plug-in.
But the article ends on that point; I have no idea what this means or how to resolve the issue.
Configure mysql like this:
./configure --prefix=/usr/local/mysql
dont use:
./configure --prefix=/usr/local/mysql --with-plugins=sphinx
It forces the compiler to link the plugin statically.
Once done you should have a file called 'ha_sphinx.so'
I finally had to just recompile MySQL entirely rather than install it as a plugin. This involved a number of gotchas in and of itself, too. But save yourself the headache of trying to recreate the same compile conditions for Sphinx that you used for MySQL and just recompile all at once following the Sphinx documentation to the letter.