Date: Wed, 19 Feb 1997 14:01:13 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Andy Eskilsson <x-aes AT telelogic DOT se>
cc: djgpp AT delorie DOT com
Subject: Re: Detecting djgpp before compiling.
In-Reply-To: <ksu3n9kv8y.fsf@telelogic.se>
Message-ID: <Pine.SUN.3.91.970219135628.23212C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 19 Feb 1997, Andy Eskilsson wrote:

> Well one of the brick walls I banged my head to is stat, unfortunetaly
> python doesn't use the constants defined in stat.h, but defines them
> itself after 'de facto standard definitions' for example.. 

I suggest you report this as a bug to the author(s) of python.

> (And no, I can't get python to use the constants in stat.h)

Why not?

> solution to this problem would be to detect that I am using djgpp in
> configure, either I compile somehing like #ifdef __djgpp__ retun 1
> #else return 0, or well is there any other solution?

The DJGPP FAQ explains how to write DJGPP-specific code in section 8.6.
If you need to detect this at configure time, make the script test 
whether $DJDIR environment variable is defined.

But the best solution is to use <sys/stat.h>.