[M3commit] FW: Must -D_GNU_SOURCE for these to work

[Jay]

It worked for me..and not without it as expected.
Is there a danger of, like, bifurcating the ABI across different source files, when they have different #defines?
 
You know, I would not want a situation such as:
 
/usr/include/foo.h:
typedef struct _foo_t {
 int a;
#ifdef _GNU_SOURCE
 int b;
} foo_t;
 
and then different files traffic in foo_t, with varying defined-ness _GNU_SOURCE.
 
I think #define _FILE_OFFSET_BITS can cause this sort of thing for example.
 
  -Jay



From: hosking at cs.purdue.eduTo: jay.krell at cornell.eduDate: Wed, 18 Feb 2009 17:14:13 +1100CC: m3commit at elegosoft.comSubject: Re: [M3commit] FW: Must -D_GNU_SOURCE for these to work


For some reason that does not appear to work.  It needs to be defined on the command line as -D_GNU_SOURCE.

On 18 Feb 2009, at 17:05, Jay wrote:

The source file should have #define _GNU_SOURCE at the top, right?Thanks for these changes.  - Jay> Date: Wed, 18 Feb 2009 06:52:47 +0000> To: m3commit at elegosoft.com> From: hosking at elego.de> Subject: [M3commit] CVS Update: cm3> > CVSROOT: /usr/cvs> Changes by: hosking at birch. 09/02/18 06:52:47> > Modified files:> cm3/m3-libs/m3core/src/runtime/POSIX/: RTSignalC.c > > Log message:> Add __linux __i386 and __amd64. Must -D_GNU_SOURCE for these to work.> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20090218/397349e6/attachment-0002.html>