Embeddable Common-Lisp

Dear William,

thanks for your report. Unfortunately, the Windows ports have lagged behind
in the path towards the next release.

Having fixed most problems in the Unix ports, I am now working on bringing
back online the Windows test farm and fixing both the Microsoft Visual
Studio C++ port and the Mingw32 port.

Until these problems are fixed I recommend you to stay with stable releases
(10.4)

I apologize for the inconvenience.

Juanjo

On Thu, Dec 16, 2010 at 8:47 AM, William Wang <javacave@...> wrote:

> on window xp sp2,
> cvs get lastest ecl code,
>
> cvs.exe -z3 -d:pserver:anonymous@...
>
>  checkout ecl
>
>
> compile option:
>
> make clean;./configure --prefix=/usr/local   --enable-threads
> --enable-unicode ;make
>
> get error:
> rm -f tmp.c
> if test -f ../CROSS-DPP ; then ../CROSS-DPP /temp/ecl/ecl/src/c/package.d
> tmp.c
> ; else ./dpp.exe /temp/ecl/ecl/src/c/package.d tmp.c ; fi
> dpp: d:/temp/ecl/ecl/src/c/package.d -> tmp.c
> gcc -DECLDIR="\"/usr/local/lib/ecl-10.7.1\"" -I. -Id:/temp/ecl/ecl/build
> -I/temp
> /ecl/ecl/src/c -I../ecl/gc -DECL_API -DECL_NO_LEGACY    -g -O2 -g -O2
> -D_THREAD_
> SAFE -Dmingw32 -c -o package.o tmp.c
> d:/temp/ecl/ecl/src/c/package.d: In function 'ecl_intern':
> d:/temp/ecl/ecl/src/c/package.d:368:11: error: expected ';' before ':'
> token
> d:/temp/ecl/ecl/src/c/package.d:395:22: error: expected identifier or '*'
> before
>  numeric constant
> d:/temp/ecl/ecl/src/c/package.d: In function 'cl_export2':
> d:/temp/ecl/ecl/src/c/package.d:539:11: error: expected ';' before ':'
> token
> d:/temp/ecl/ecl/src/c/package.d:563:22: error: expected identifier or '*'
> before
>  numeric constant
> make[2]: *** [package.o] Error 1
> make[2]: Leaving directory `/temp/ecl/ecl/build/c'
> make[1]: *** [libeclmin.a] Error 2
> make[1]: Leaving directory `/temp/ecl/ecl/build'
> make: *** [all] Error 2
>
>
> mingw is latest mingw-get-inst-20101030.exe is gcc 4.5.0.
>
> complie 10.4.1 is ok.
>
> thanks.
>
>
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _______________________________________________
> Ecls-list mailing list
> Ecls-list@...
> https://lists.sourceforge.net/lists/listinfo/ecls-list
>
>


-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com

On Fri, 17 Dec 2010 15:36:37 +0100
Juan Jose Garcia-Ripoll <juanjose.garciaripoll@...> wrote:

> Having fixed most problems in the Unix ports, I am now working on bringing
> back online the Windows test farm and fixing both the Microsoft Visual
> Studio C++ port and the Mingw32 port.

I just wanted to say, thanks for still caring about the mingw32 port;
although I fortunately didn't have to build software distributions for
win32 lately, if I did, mingw32 would be my first try for the following
reasons:

- can be used for cross-compilation from unix
- or using the cygwin->mingw32 cross-compiler, via a unix-like full
  development environment on win32 (emacs/vim, shell, toolchain, etc)
- mingw32-built applications allow easier standalone installation, not
  requireing the msvc++ runtime libraries which don't seem to be
  installed by default on some (all?) windows, or are outdated by
  default...

I see a number of opensource projects which used to support mingw32 but
which no longer officially do, however.  So cheers for caring.
-- 
Matt

On Sat, Dec 18, 2010 at 4:12 AM, Matthew Mondor <mm_lists@...:

> I see a number of opensource projects which used to support mingw32 but
> which no longer officially do, however.  So cheers for caring.
>

I only do it because there is a persistent demand for it.

Mingw32+Msys is a rather slow, inconvenient and difficult to use toolchain.
I understand the library distribution issues, but once ECL's NSIS system is
brought back online one could probably include the MSVC runtime in it
without much problems. As for the cross-compilation part, nowadays this is
not a problem, given the existence of VirtualBox and other virtualization
software that allows you to run Windows, log into it via ssh, share files,
build, download the result...

Juanjo

-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com