[Ecls-list] win32 compilation error

[Juan Jose Garcia Ripoll]

On Fri, 2006-03-24 at 10:27 +0100, Marko Kocić wrote:
> Ok, I found out what was wrong with MCW_EM. Seems I had both gcc
> 3.4 and 4.1 include files so gcc made a mess. I cleaned all old
> gcc files and I now have the following error.
> 
> gcc -c -I. -I/c/dev/cvstree/ecl/ecl/build
> -I/c/dev/cvstree/ecl/ecl/src/c -I../ecl/gc  -g -O2 -D_THREAD_SAFE
> --fstrict-aliasing -Dmingw32  -o package.o package.c
> c:/dev/cvstree/ecl/ecl/src/c/package.d: In function 'cl_make_package':
> c:/dev/cvstree/ecl/ecl/src/c/package.d:725: error: initializer element
> is not constant
> c:/dev/cvstree/ecl/ecl/src/c/package.d:725: error: (near
> initialization for 'KEYS[0]')
> c:/dev/cvstree/ecl/ecl/src/c/package.d:725: error: initializer element
> is not constant
> c:/dev/cvstree/ecl/ecl/src/c/package.d:725: error: (near
> initialization for 'KEYS[1]')

This is probably a windows specific thing. I have seen it in the past
when we failed to provide a proper declaration for cl_objects mentioning
it belongs to a dll. The reason was that in that case the symbol
cl_object is replaced with a call to a function that retrieves the
address of the variable in the dll. However this should not happen when
building ECL because the references to cl_objects are themselves static.

Juanjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20060324/e8b1a267/attachment.sig>