[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ltdl, -ansi compiler flag and windows host

From: Roumen Petrov
Subject: Re: ltdl, -ansi compiler flag and windows host
Date: Sun, 15 Nov 2009 14:39:03 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20090907 SeaMonkey/1.1.18

Bob Friesenhahn wrote:
On Sat, 14 Nov 2009, Roumen Petrov wrote:

Hi All,

The failed case if project with ltdl included. If the project is configured with "-ansi" flag set to CFLAGS the build of installable ltdl fail with:

When -ansi is set compiler define __STRICT_ANSI__.

No idea how to fix and I don't know reasons for above expression. Why __STRICT_ANSI__ is part of expression ?

I believe that the intention of GCC is that when -ansi is provided that the compiler conforms to ANSI C. Note that for ANSI C, POSIX, and OpenGroup Unix standards, requesting the standard compilation environment *excludes* any interfaces and functionality which are not provided by that specification. It is necessary to request a standard which supplies everything which is needed. That is why such requests are often not made. In this case, the Windows APIs for loading modules are not available.


May be, You are right.
The modification of lt_private .h is result of this discussion http://www.mail-archive.com/address@hidden/msg02530.html

About flags and GCC internal defines :
1) __STRICT_ANSI__ is defined to 1 for -ansi, -std=c89 -std=c99 and may be other flags. and is not defined by default or for -posix flags

2) in all above cases GCC (mingw host) define internally
#define __stdcall __attribute__((__stdcall__))
for -posix and without flag compiler define
#define _stdcall __attribute__((__stdcall__))

Note other defined attributes are out of scope.

May be check for __STRICT_ANSI__ has to be added to LT_UNUSED ?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]