Menu
▾
▴
[ clisp-Bugs-2354303 ] Build problem when ffcall is not in a system directory.
|
From: SourceForge.net <no...@so...> - 2008-12-12 18:53:25
|
Bugs item #2354303, was opened at 2008-11-27 22:01 Message generated for change (Comment added) made by whebisch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2354303&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: build problems >Status: Open Resolution: Works For Me Priority: 5 Private: No Submitted By: Waldek Hebisch (whebisch) Assigned to: Sam Steingold (sds) Summary: Build problem when ffcall is not in a system directory. Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: Waldek Hebisch (whebisch) Date: 2008-12-12 18:53 Message: I am running Fedora 9 with self-compiled kernel. uname -a Linux localhost.localdomain 2.6.25.6 #7 PREEMPT Fri Jul 4 14:09:18 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux The system uses libc 2.8 /bin/sh --version GNU bash, version 3.2.33(1)-release (x86_64-redhat-linux-gnu) Copyright (C) 2007 Free Software Foundation, Inc. Concerning config.log: I see no indication that prefixes I gave are used. "checking how to link with" lines seem to be the same regardless if I give prefix argument or not: configure:31697: checking for libsigsegv configure:31756: result: no, consider installing GNU libsigsegv configure:31809: checking how to link with libavcall configure:32264: result: -lavcall configure:32305: checking how to link with libcallback configure:32760: result: -lcallback configure:32813: checking avcall.h usability configure:32830: gcc -c -g -O2 conftest.c >&5 conftest.c:120:20: error: avcall.h: No such file or directory Actually, if I try configuring without giving prefix argument config.log is essentially the same (I see changed command line, changes to paths (since I configure in different directory) and different value of STACK_ADDRESS_RANGE (this one simply changes from run to run)). ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-12-12 17:27 Message: I am lost. first, please tell me your platform (uname -a; glibc version if linux). second, please read your config.log very carefully and see where your prefixes are used. also, look for "checking how to link with". you might also want to try cvs head. ---------------------------------------------------------------------- Comment By: Waldek Hebisch (whebisch) Date: 2008-12-12 17:20 Message: 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$ ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-12-12 16:36 Message: 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? ---------------------------------------------------------------------- Comment By: Waldek Hebisch (whebisch) Date: 2008-12-12 01:33 Message: >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. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-11-28 15:21 Message: this is now marked "pending" because we are waiting for your input ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-11-28 02:54 Message: wfm --with-libffcall-prefix and --with-libsigsegv-prefix please check config.log and investigate why the configure fails to detect the libraries. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2354303&group_id=1355 |