Menu
▾
▴
[ clisp-Bugs-569025 ] CLISP uses arisparc.d instead of arisparc64.d
|
From: SourceForge.net <no...@so...> - 2007-11-11 20:28:04
|
Bugs item #569025, was opened at 2002-06-14 10:15 Message generated for change (Comment added) made by sds You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=569025&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: Pending Resolution: None Priority: 5 Private: No Submitted By: fragMental (fragmental) Assigned to: Bruno Haible (haible) Summary: CLISP uses arisparc.d instead of arisparc64.d Initial Comment: system type: sparc-sun-solaris2.8 CC: Sun Workshop/Forte Developer 6 version: clisp-2.28 configure invocation: ./configure --prefix=/site The configuration process halts with the message: cc -g -I. -I../../ffcall/avcall -S ../../ffcall/avcall/minitests.c "../../ffcall/avcall/tests.c", line 90: warning: initializer does not fit or is out of range: -1 "../../ffcall/avcall/tests.c", line 250: warning: initializer does not fit or is out of range: -1 cc -g -I. -I../../ffcall/avcall -c ../../ffcall/avcall/minitests.c "../../ffcall/avcall/tests.c", line 90: warning: initializer does not fit or is out of range: -1 "../../ffcall/avcall/tests.c", line 250: warning: initializer does not fit or is out of range: -1 /bin/sh ./libtool --mode=link cc -g minitests.o libavcall.la -o minitests cc -g minitests.o -o minitests ./.libs/libavcall.a ./minitests > minitests.out *** Error code 139 make: Fatal error: Command failed for target `check' To continue building CLISP, the following commands are recommended (cf. unix/INSTALL step 4): cd src ./makemake --prefix=/site --with-readline --with- gettext > Makefile make config.lisp vi config.lisp make make check bash-2.03# Attempts to continue building as instructed, results in a horde of warnings when running 'make', e.g.: "control.d", line 1887: warning: _Bool is a keyword in ISO C99 "control.d", line 2019: warning: integer overflow detected: op "<<" Finally, the make process is halted with the following error report: cc -E arisparc.c | grep -v '^#' | grep -v '^ *#line' | sed - e 's,% ,%,g' -e 's,\. ,.,g' > arisparc.s "arisparc.d", line 160: invalid input token: 1f "arisparc.d", line 304: invalid input token: 1f "arisparc.d", line 307: invalid input token: 2f "arisparc.d", line 315: invalid input token: 3f "arisparc.d", line 365: invalid input token: 1f "arisparc.d", line 368: invalid input token: 2f "arisparc.d", line 376: invalid input token: 3f "arisparc.d", line 622: invalid input token: 2f "arisparc.d", line 628: invalid input token: 1b "arisparc.d", line 652: invalid input token: 2f "arisparc.d", line 658: invalid input token: 1b "arisparc.d", line 682: invalid input token: 2f "arisparc.d", line 686: invalid input token: 1b "arisparc.d", line 686: fatal: too many errors cc: acomp failed for arisparc.c cc -dalign -fsingle -DUNIX_BINARY_DISTRIB - DUNICODE -c arisparc.s /opt/SUNWspro/bin/../WS6U2/bin/fbe: error: missing definition for local symbol "2F" cc: assembler failed for arisparc.s *** Error code 2 make: Fatal error: Command failed for target `arisparc.o' bash-2.03# I have also tried compiling clisp-2.27 instead of 2.28, but with the same results. Does anyone have any suggestions or help to offer? Thanks in advance. ---------------------------------------------------------------------- >Comment By: Sam Steingold (sds) Date: 2007-11-11 15:28 Message: Logged In: YES user_id=5735 Originator: NO if indeed the problem is that clisp thinks your machine is 32-bit while it is actually 64-bit, if would help if you ran $ ./makemake debug >/dev/null and sent the output here. is the machine actually a 32-bit one or a 64-bit one??? ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2007-11-11 15:28 Message: Logged In: YES user_id=5735 Originator: NO this is the standard request for more information. 1. what is your platform? ("uname -a" on a Unix system) compiler version? libc (on Linux)? 2. where did you get the sources? when? (absolute dates are prefered over the relative ones) 3. how did you build CLISP? (what command, options &c) please do a clean build (remove your build directory and build CLISP with "./configure --build build" or at least do a "make distclean" before "make") 4. if you are using pre-built binaries, the problem is likely to be in the incompatibilities between the platform on which the binary was built and yours; please try compiling the sources. 5. what is the output of (lisp-implementation-version)? 6. what is the value of *features*? 7. please supply the full output (copy and paste) of all the error messages. If you cannot build CLISP, you can obviously skip 5 and 6, but then you should provide more information in 1. please see <http://clisp.cons.org/clisp.html#bugs> for more information. Thanks. PS. This bug report is now marked "pending" and will auto-close unless you respond (in which case it will auto-re-open). ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2005-07-27 17:18 Message: Logged In: YES user_id=5735 this bugs appears to be caused by CLISP using arisparc.d instead of arisparc64.d http://article.gmane.org/gmane.lisp.clisp.devel:14533 http://sourceforge.net/mailarchive/message.php?msg_id=12487386 ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2002-06-14 12:07 Message: Logged In: YES user_id=5735 I suggest that you try GCC 2.95, which is known to work well. I assign this to Bruno, who might be able to say more. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=569025&group_id=1355 |