|
View:
New views
1 Messages
—
Rating Filter:
Alert me
|
|
|
[ clisp-Bugs-2011096 ] unicode in comments causes compile errorBugs item #2011096, was opened at 2008-07-05 02:58
Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2011096&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: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: John (johndoejr) Assigned to: Bruno Haible (haible) Summary: unicode in comments causes compile error Initial Comment: When compiling the source, some unicode characters in comments cause compile error. A patch to omit the comments is needed for successful compile in my environment (ja_JP.UTF-8). The situation has been the same from 2.38 (as far as I am aware of) to the latest 2.46. ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2008-07-22 02:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-07-07 15:42 Message: Logged In: YES user_id=5735 Originator: NO what is your platform? gcc? libc? what are the exact error messages you see? ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-07-07 15:42 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). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2011096&group_id=1355 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ clisp-devel mailing list clisp-devel@... https://lists.sourceforge.net/lists/listinfo/clisp-devel |
| Free Forum Powered by Nabble | Forum Help |