Re: Cygwin gcc "initializer element is not constant" problem

2003-01-02 Thread Jason Tishler
Igor, On Thu, Jan 02, 2003 at 03:03:21PM -0500, Igor Pechtchanski wrote: > How about doing exactly what the message suggests (see attached)? I think that I found the best solution -- auto-import the functions by just removing the "__declspec(dllimport)" indicators. If interested, see attached.

Re: Cygwin gcc "initializer element is not constant" problem

2003-01-02 Thread Igor Pechtchanski
On Thu, 2 Jan 2003, Jason Tishler wrote: > The attached code snippet, j2.c, demonstrates a Cygwin specific > compilation problem that affects many Python shared extension modules: > > $ gcc -c j2.c > j2.c:17: initializer element is not constant > j2.c:17: (near initialization for `f.ge

Cygwin gcc "initializer element is not constant" problem

2003-01-02 Thread Jason Tishler
The attached code snippet, j2.c, demonstrates a Cygwin specific compilation problem that affects many Python shared extension modules: $ gcc -c j2.c j2.c:17: initializer element is not constant j2.c:17: (near initialization for `f.get') It appears that Cygwin gcc considers function po