#245 makefile error on win32 msvc6 build

build problems
closed
clisp (524)
5
2006-03-10
2005-02-14
John Small
No

CLisp 2.33.80

makefile.msvc6(d) line 820

Using nmake the

if ; then; else fi

is not a valid construct, i.e.

if cmp cflags.h.new cflags.h > /dev/null 2>&1; then
${RM} cflags.h.new; else ${MV} cflags.h.new cflags.h; fi

If I comment that line out the overall build fails on the
spvw_memfile.d file with for example the error on line 1332

READ(mem.conses.heap_start,len);

error C2064: term does not evaluate to a function

Discussion

  • Sam Steingold

    Sam Steingold - 2005-02-14
    • milestone: 100335 --> build problems
    • assigned_to: sds --> ampy
     
  • John Small

    John Small - 2005-02-14

    Logged In: YES
    user_id=1199665

    This statement:

    if cmp cflags.h.new cflags.h > /dev/null 2>&1; then
    ${RM} cflags.h.new; else ${MV} cflags.h.new cflags.h; fi

    should read $(RM) and $(MV) instead of ${RM} and ${MV}

    Also ssize_t throughout the files should read size_t.

    And the cccp generates extra semicolons that cause stream.d
    to start failing at line 4855. Perhaps this is due to the
    various
    CFLAGS that MSVC 6 doesn't understand like:

    -Os -Oy -Ob1

     
  • Jörg Höhle

    Jörg Höhle - 2006-02-23

    Logged In: YES
    user_id=377168

    I built clisp/cvs with MSVC6 today, after applying a tiny
    patch to win32aux.d The testsuite passes, as well as
    the new check-exec-image in 2.38.

    makefile/makemake.in does not contain the offending lines
    anymore.

    Here are the compiler flags I used
    CC = cl $(MFLAGS) -G5 -Ot -Oy -Ob1 -Gs -Gf -Gy -Og -W4
    (be prepared for thousands of warnings from -W4).
    -Os should work as well, but I was interested in -Ot.

     
  • Jörg Höhle

    Jörg Höhle - 2006-02-23
    • assigned_to: ampy --> hoehle
    • status: open --> pending
     
  • SourceForge Robot

    • status: pending --> closed
     
  • SourceForge Robot

    Logged In: YES
    user_id=1312539

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

     

Log in to post a comment.