> But it doesn't detect guile correctly. How do you explain
> that adding them manually after running ./configure solves
> the link stage problem? The logic around detecting Guile is
> suspect.
What configure actually does is the following:
It creates a small test file with the following content
----- guiletest.cc -------------
#ifdef __cplusplus
extern "C"
#endif
char gh_scm2doubles();
int main() {
gh_scm2doubles()
; return 0; }
----- end of guiletest.cc -------
then it calls `guile-config link` to find out what link flags
are needed (this depends on how Guile itself was configured)
Let's say that guile-config link returns
-L/usr/lib -lguile -lqthreads -ldl -lreadline -lm
then configure runs the compiler
c++ guiletest.cc -L/usr/lib -lguile -lqthreads -ldl -lreadline -lm
and checks that the exit code of the compilation is OK.
Could you please try this manually on your machine and tell
us what fails.
/Mats
