[SOLVED] what is causing rebuilding CLISP from slackware-current to fail with regard to FASTCGI

badbetty · 04-27-2018, 02:28 AM

Hello, good morning

Following on from previous threads regarding recompiling Clisp, where with the help received on here I managed to get it done so to speak, there is another problem now when configuring to build with FASTCGI module using '--with-module=fastcgi'. The errors are below showing the build process bailing out.

I cannot fathom what's wrong as it seems all that should be required is to add the relevant --with-module and all should be fine.

If i remove the --with-module, the build completes.

If any one has any ideas, please share. Thank you.

configure: ** FastCGI (Programs)
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking build system type... (cached) x86_64-pc-linux-gnu
checking host system type... (cached) x86_64-pc-linux-gnu
checking for ld used by gcc... (cached) /usr/x86_64-slackware-linux/bin/ld
checking if the linker (/usr/x86_64-slackware-linux/bin/ld) is GNU ld... (cached) yes
checking for shared library run path origin... (cached) done
checking host CPU and C ABI... (cached) x86_64
checking for the common suffixes of directories in the library search path... (cached) lib64,lib64
checking how to link with libfcgi... -lfcgi
configure: ** FastCGI (Headers)
checking fcgi_stdio.h usability... no
checking fcgi_stdio.h presence... no
checking for fcgi_stdio.h... no
configure: error: cannot find FastCGI headers
make[1]: Entering directory '/tmp/clisp-2.49.20180409.0e4d38776f59/builddir/fastcgi'
make[1]: *** No rule to make target 'clisp-module'. Stop.
make[1]: Leaving directory '/tmp/clisp-2.49.20180409.0e4d38776f59/builddir/fastcgi'
Makefile:2358: recipe for target 'fastcgi' failed
make: *** [fastcgi] Error 2
make: Leaving directory '/tmp/clisp-2.49.20180409.0e4d38776f59/builddir'

drmozes · 04-27-2018, 03:33 AM

Quote:

configure: ** FastCGI (Headers)
checking fcgi_stdio.h usability... no
checking fcgi_stdio.h presence... no
checking for fcgi_stdio.h... no
configure: error: cannot find FastCGI headers

Code:

root@wizbit:/tmp/clisp-2.49.20180409.0e4d38776f59# grep -ri "fastcgi headers" .
./modules/fastcgi/configure.in:  AC_MSG_ERROR([cannot find FastCGI headers])
./modules/fastcgi/configure:  as_fn_error $? "cannot find FastCGI headers" "$LINENO" 5
root@wizbit:/tmp/clisp-2.49.20180409.0e4d38776f59# cd modules/fastcgi/
root@wizbit:/tmp/clisp-2.49.20180409.0e4d38776f59/modules/fastcgi# less README
[..]
        (1) SYSTEM REQUIREMENTS
            -------------------

You will need to:

    - Know how to compile CLISP from source code (the binaries do
      not contain the extra modules compiled in).

    - Understand FastCGI by reading up on it at http://www.fastcgi.com

    - Download the FastCGI developer's kit, build it, and install it
      See http://www.fastcgi.com  Win32 users should see
          http://www.caraveo.com/fastcgi/
[..]

Did you do that already? The headers are missing, so either they are not in the expected place, or they're not there at all.
fgcgi_stdio is not present on my system.

badbetty · 04-27-2018, 03:49 AM

No, in short. Even more strangely, Ive just tried on a different machine (and again 'no' to your question) and it has worked. I'm in the process of trying to sort out what is different.

In my naivety, I'd understood that with fastcgi now being a module in the CLISP build tree, the 'dev kit' fastcgi stuff was no longer relevant. The --with-module=fastcgi was all that is now required. Have I misunderstood.

I'll pick through some more.

ponce · 04-27-2018, 03:59 AM

Quote:

Originally Posted by badbetty

No, in short. Even more strangely, Ive just tried on a different machine (and again 'no' to your question) and it has worked. I'm in the process of trying to sort out what is different.

In my naivety, I'd understood that with fastcgi now being a module in the CLISP build tree, the 'dev kit' fastcgi stuff was no longer relevant. The --with-module=fastcgi was all that is now required. Have I misunderstood.

I'll pick through some more.

if it worked on a different machine could be because on that one you have installed fcgi on it: on a host I got fcgi_stdio.h as part of the fcgi package.

badbetty · 04-27-2018, 05:10 AM

oh good grief...you were spot on. Why is everyone so much more savvy at all this than me! :-)

I can't even remember when I put fcgi package on. It would seem, as was intimated by drmozes, the CLISP fastcgi module does need some fastcgi header stuff etc to be loaded before build.

Thank you.