Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#510 Build problem when ffcall is not in a system directory.

build problems
closed-works-for-me
Sam Steingold
clisp (525)
5
2008-12-14
2008-11-27
Waldek Hebisch
No

Current clisp distribution unbundled libffcall
and libsigsegv. Unfortunatly, many popular
Linux distributions do not include them.
When libffcall and/or libsigsegv are installed
in a nonstandard directory clisp-2.47 configure
can not find them. Giving --with-libsigsegv-prefix
(which is mentioned in unix/INSTALL) does not
help -- apparently this argument is ignored by
configure. For ffcall I was unable to find
official method to specify alternative location.

Also modifying CFLAGS and/or LDFLAGS did not
help: adding -I to CFLAGS allowed to find
header files, but when I modified LDFLAGS,
then configure was able to find the libraries,
but subconfigure in i18n failed, complaining
about modified LDFLAGS.

Discussion

1 2 3 > >> (Page 1 of 3)
  • Sam Steingold
    Sam Steingold
    2008-11-28

    • labels: --> clisp
    • assigned_to: nobody --> sds
    • milestone: --> build problems
     
  • Sam Steingold
    Sam Steingold
    2008-11-28

    wfm --with-libffcall-prefix and --with-libsigsegv-prefix
    please check config.log and investigate why the configure fails to detect the libraries.

     
  • Sam Steingold
    Sam Steingold
    2008-11-28

    • status: open --> pending
     
  • Sam Steingold
    Sam Steingold
    2008-11-28

    this is now marked "pending" because we are waiting for your input

     
  • Waldek Hebisch
    Waldek Hebisch
    2008-12-12

    From config log:

    configure:26222: checking for libsigsegv
    configure:26252: gcc -o conftest -g -O2 conftest.c -lsigsegv >&5
    conftest.c:60:21: error: sigsegv.h: No such file or directory

    AFAICS configure contains no mechanizm to pass correct include and
    library options for libsigsegv and libffcall to the compiler used for feature testing (gcc in this case). As I wrote in the original
    report after appropriate setting of CFLAGS and LDFLAGS configure
    finds libsigsegv and libffcall, but then fails later.

     
  • Waldek Hebisch
    Waldek Hebisch
    2008-12-12

    • status: pending --> open
     
  • Sam Steingold
    Sam Steingold
    2008-12-12

    my config.log says:
    configure:27208: checking for libsigsegv
    configure:27238: gcc -o conftest -I/home/sds/top/Linux-x86_64/include conftest.c /home/sds/top/Linux-x86_6/lib/libsigsegv.a -lc >&5
    configure:27245: $? = 0
    configure:27267: result: yes
    configure:27275: checking how to link with libsigsegv
    configure:27277: result: /home/sds/top/Linux-x86_64/lib/libsigsegv.a -lc

    I invoke configure with arguments
    --with-libsigsegv-prefix=/home/sds/top/Linux-x86_64 --with-libffcall-prefix=/home/sds/top/Linux-x86_64
    what is your exact configure command line?

     
  • Sam Steingold
    Sam Steingold
    2008-12-12

    • status: open --> pending
     
  • Waldek Hebisch
    Waldek Hebisch
    2008-12-12

    I used the following configure line (in the root directory
    of the source tree):

    ./configure --with-libffcall-prefix=/home/hebisch/lisp/pp4/usr --with-libsigsegv-prefix=/home/hebisch/lisp/pp4/usr >clogg 2>&1 &

    libffcall and libsigsegv are in the specified directory:
    -bash-3.2$ ls /home/hebisch/lisp/pp4/usr/include/
    avcall.h sigsegv.h trampoline_r.h vacall_r.h
    callback.h trampoline.h vacall.h
    -bash-3.2$ ls /home/hebisch/lisp/pp4/usr/lib/
    libavcall.a libcallback.a libsigsegv.a libtrampoline.a
    libavcall.la libcallback.la libsigsegv.la libvacall.a
    -bash-3.2$

     
  • Waldek Hebisch
    Waldek Hebisch
    2008-12-12

    • status: pending --> open
     
1 2 3 > >> (Page 1 of 3)