#483 unicode in comments causes compile error

build problems
closed-fixed
Sam Steingold
clisp (525)
5
2008-07-22
2008-07-05
John
No

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.

Discussion

  • John
    John
    2008-07-05

    unicode fix patch

     
    Attachments
  • Sam Steingold
    Sam Steingold
    2008-07-07

    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).

     
  • Sam Steingold
    Sam Steingold
    2008-07-07

    Logged In: YES
    user_id=5735
    Originator: NO

    what is your platform? gcc? libc?
    what are the exact error messages you see?

     
  • Sam Steingold
    Sam Steingold
    2008-07-07

    • status: open --> pending-works-for-me
     
  • 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).

     
    • status: pending-works-for-me --> closed-works-for-me
     
  • onjo
    onjo
    2008-07-22

    Logged In: YES
    user_id=1891492
    Originator: NO

    I succeeded in the reproduction of such error.

    % uname -a
    Linux vmware 2.6.22-gentoo-r9 #2 SMP Tue Dec 4 23:02:25 JST 2007 i686 Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz GenuineIntel GNU/Linux

    % (LANG=C; gcc -v)
    Using built-in specs.
    Target: i686-pc-linux-gnu
    Configured with: /var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.1.2 --includedir=/usr/lib/gcc/i\ 686-pc-linux-gnu/4.1.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2/man --infodir=/usr/share/gcc\ -data/i686-pc-linux-gnu/4.1.2/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --dis\ able-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --disabl\ e-multilib --enable-libmudflap --disable-libssp --disable-libgcj --with-arch=i686 --enable-languages=c,c++,treelang,fortran --enable-shared --enable-threads=posix --e\ nable-__cxa_atexit --enable-clocale=gnu
    Thread model: posix
    gcc version 4.1.2 (Gentoo 4.1.2 p1.0.2)

    % echo $LANG
    ja_JP.eucJP

    % ./configure --prefix=$HOME/local --with-unicode --cbc build-with-gcc
    [snip]
    gcc -I/home/someone/local/include -Igllib -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -O2 -fexpens\ ive-optimizations -falign-functions=4 -DUNICODE -DDYNAMIC_FFI -I. -DCOMPILE_STANDALONE -O0 -c genclisph.c
    In file included from ../src/genclisph.d:7:
    ../src/lispbibl.d:9136: 警告: レジスタが二つのグローバルレジスタ変数として使われました
    In file included from ../src/genclisph.d:232:
    ../src/lispbibl.d: In function 'main':
    ../src/lispbibl.d:1028: error: stray '\217' in program
    ../src/lispbibl.d:1028: error: stray '\357' in program
    ../src/lispbibl.d:1028: error: stray '\274' in program
    ../src/lispbibl.d:1028: error: stray '\212' in program
    ../src/lispbibl.d:1028: error: stray '\357' in program
    ../src/lispbibl.d:1028: error: stray '\274' in program
    ../src/lispbibl.d:1028: error: stray '\212' in program
    ../src/lispbibl.d:1028: error: stray '\357' in program
    ../src/lispbibl.d:1028: error: stray '\274' in program
    ../src/lispbibl.d:1028: error: stray '\217' in program
    ../src/lispbibl.d:1028: error: 'otherwise' undeclared (first use in this function)
    ../src/lispbibl.d:1028: error: (Each undeclared identifier is reported only once
    ../src/lispbibl.d:1028: error: for each function it appears in.)
    ../src/lispbibl.d:1028: error: expected ';' before 'is'
    ../src/lispbibl.d:6507: error: stray '\342' in program
    ../src/lispbibl.d:6507: error: stray '\212' in program
    ../src/lispbibl.d:6507: error: stray '\206' in program
    ../src/lispbibl.d:6507: error: expected expression before '<' token
    ../src/lispbibl.d:6523: error: stray '\342' in program
    ../src/lispbibl.d:6523: error: stray '\212' in program
    ../src/lispbibl.d:6523: error: stray '\206' in program
    ../src/lispbibl.d:6535: error: stray '\342' in program
    ../src/lispbibl.d:6535: error: stray '\212' in program
    ../src/lispbibl.d:6535: error: stray '\206' in program
    ../src/lispbibl.d:6535: error: stray '\342' in program
    ../src/lispbibl.d:6535: error: stray '\212' in program
    ../src/lispbibl.d:6535: error: stray '\206' in program
    ../src/lispbibl.d:6535: error: stray '\342' in program
    ../src/lispbibl.d:6535: error: stray '\212' in program
    ../src/lispbibl.d:6535: error: stray '\206' in program
    ../src/lispbibl.d:6541: error: stray '\342' in program
    ../src/lispbibl.d:6541: error: stray '\212' in program
    ../src/lispbibl.d:6541: error: stray '\206' in program
    ../src/lispbibl.d:6541: error: stray '\342' in program
    ../src/lispbibl.d:6541: error: stray '\212' in program
    ../src/lispbibl.d:6541: error: stray '\206' in program
    ../src/lispbibl.d:6549: error: stray '\342' in program
    ../src/lispbibl.d:6549: error: stray '\212' in program
    ../src/lispbibl.d:6549: error: stray '\206' in program
    ../src/genclisph.d:258: 警告: 符合無しの式 < 0 という比較は常に false です
    make: *** [genclisph.o] エラー 1

     
  • onjo
    onjo
    2008-07-22

    • assigned_to: haible --> sds
     
  • Sam Steingold
    Sam Steingold
    2008-07-22

    • status: closed-works-for-me --> closed-fixed
     
  • Sam Steingold
    Sam Steingold
    2008-07-22

    Logged In: YES
    user_id=5735
    Originator: NO

    thank you for your bug report.
    the bug has been fixed in the CVS tree.
    you can either wait for the next release (recommended)
    or check out the current CVS tree (see http://clisp.cons.org\)
    and build CLISP from the sources (be advised that between
    releases the CVS tree is very unstable and may not even build
    on your platform).