This section tries to help the Ceylan users with all the issues they can encounter when building or installing the Ceylan library. More precisely, this section focuses on Ceylan internal issues. To deal with errors lying on the user code specifically (when the Ceylan library is misused), then refer to the Ceylan user's guide troubleshooting section.
libtool: unrecognized option `--tag=CXX'
Try `libtool --help' for more information.
checktools
make target is evaluated, then the most ancient supported version for libtool will be displayed with the found one, in yellow. Just check that yours is more recent than the requested version. For example, libtool found, using [version 1.4.3, must be 1.5.2 or higher]
will probably lead to build failures.size of array CEYLAN_stop_wrong_size_for_XXX is negative
This error has been triggered by the Ceylan build system because one of the basic data types which have been defined by Ceylan is not of the expected size.
For example, Sint16
should be a signed integer on 16 bits. If ever, on a specific platform and with a specific compiler, Ceylan assumption was wrong about the size in memory of a data type, the previous error is fired.
You therefore have found a bug in Ceylan, please click here to send us a bug report (it should take you less than half a minute to do so), telling us what is your compiler (name and version), what is your platform (CPU and OS) and which data type failed (the XXX in CEYLAN_stop_wrong_size_for_XXX). Thank you !
Creating executable XXX on YYY: libtool: link: warning: library `ZZZ' was moved.
Be sure to run make all
from the root directory (ex: $CEYLAN_ROOT/src
): only the main makefile has for purpose to install the examples. Executing a make from test directory will build it, not install it. To check, just look at the dates of the executable to be found under $CEYLAN_ROOT/bin
.
To get rid of annoying issues with tabulation length and window sizes, we recommend using nedit (or its counterpart nc
) as source code editor, with following settings:
If you have information more detailed or more recent than those presented in this document, if you noticed errors, neglects or points insufficiently discussed, or if you would like to contribute and help us, even a little bit, drop us a line !