Ladislav Mecir wrote:

> Hi all,
> 
> I am trying to compile LyX in Mandrake 10.0 Official with Xforms
> frontend. Originally ./configure complained about not being able to find
> forms.h which I solved easily. Now it complains:
> 
> ** Cannot find libforms or libxforms. Please check that the xforms
> library is correctly installed on your system.

I take it that this is where libforms.so is installed?

You should find the offending test program (the one that failed, flagging
the error in the configure script) in config.log, together with a line
detailing how the compiler was invoked.

Something like:

configure:3327: checking for strerror in -lcposix
configure:3358: gcc -o conftest -g -O2   conftest.c -lcposix   >&5
/usr/bin/ld: cannot find -lcposix
collect2: ld returned 1 exit status
configure:3361: $? = 1
configure: failed program was:
| #line 3334 "configure"
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "lyx"
| #define PACKAGE_TARNAME "lyx"
| #define PACKAGE_VERSION "1.4.0cvs"
| #define PACKAGE_STRING "lyx 1.4.0cvs"
| #define PACKAGE_BUGREPORT "[EMAIL PROTECTED]"
| #define DEVEL_VERSION 1
| #define PACKAGE "lyx-1.4.0cvs"
| #define VERSION "1.4.0cvs"
| #define HAVE_KPSEWHICH 1
| /* end confdefs.h.  */
|
| /* Override any gcc2 internal prototype to avoid an error.  */
| #ifdef __cplusplus
| extern "C"
| #endif
| /* We use char because int might match the return type of a gcc2
|    builtin and then its argument prototype would still apply.  */
| char strerror ();
| int
| main ()
| {
| strerror ();
|   ;
|   return 0;
| }

I beleve that the actual test you're looking for in config.log is described
as:

configure:11739: checking for fl_initialize in -lforms
configure:11770: g++ -o conftest -g -O -W -Wall  -isystem
/usr/X11R6/include  conftest.cc -lforms -lXpm  -lSM -lICE -lc -lm  
-L/usr/X11R6/lib -lX11  >&5

Here, it works, so the test program is not listed. You should cut and paste
the failing code into a separate 'conftest.cc' file and ascertain how to
get the compiler to compile it successfully.

HTH,
-- 
Angus

Reply via email to