• Alexis <ceo alexisware.com> Feb 23 2004
• "Walter" <walter digitalmars.com> Feb 23 2004
• Craig Bowlas <craigbowlas yahoo.co.uk> Feb 24 2004
• "Walter" <walter digitalmars.com> Feb 24 2004

Alexis <ceo alexisware.com> writes:

Hello,

I get these errors when parsing, and I didn't even use the STL in my 
project yet:

Warning: P:\DM\stlport\stlport\config\stl_apple.h(33): Encountered 
preprocessor #error directive
Warning: P:\DM\stlport\stlport\config\stl_apple.h(41): Encountered 
preprocessor #error directive
Warning: P:\DM\stlport\stlport\stdarg.h(23): Invalid include file name: 
_STLP_NATIVE_C_HEADER(stdarg.h)
Warning: P:\DM\stlport\stlport\ctype.h(23): Invalid include file name: 
_STLP_NATIVE_C_HEADER(ctype.h)
Warning: P:\DM\stlport\stlport\string.h(24): Invalid include file name: 
_STLP_NATIVE_C_HEADER(string.h)
Warning: P:\DM\stlport\stlport\stdlib.h(23): Invalid include file name: 
_STLP_NATIVE_C_HEADER(stdlib.h)
Parse Completed

Did I forget to #define something?

Thank you,
Alexis.

"Walter" <walter digitalmars.com> writes:

Perhaps you have it on your include path.

"Alexis" <ceo alexisware.com> wrote in message
news:Xns94989F2E94B3Eagolzman 63.105.9.61...
 Hello,

 I get these errors when parsing, and I didn't even use the STL in my
 project yet:

Craig Bowlas <craigbowlas yahoo.co.uk> writes:

On Mon, 23 Feb 2004 20:02:06 -0800, "Walter" <walter digitalmars.com>
wrote:

Perhaps you have it on your include path.

"Alexis" <ceo alexisware.com> wrote in message
news:Xns94989F2E94B3Eagolzman 63.105.9.61...
 Hello,

 I get these errors when parsing, and I didn't even use the STL in my
 project yet:





I have seen this problem too.  The two error directives were because
the apple config for stlport was being loaded!  I forced the issue by
a quick mod to stlcomp.h to force the DMC config file to load, this
lost the #error issues, but the include files still are claimed
invalid.  This problem was not seen when the SGI version of STL was
used to build this project.  The project is a windows MFC app, built
using the IDDE and compiler 8.40.

Any idea why was the DMC config file was not loaded automatically, and
what is the problem with the standard include files?

Craig.

"Walter" <walter digitalmars.com> writes:

"Craig Bowlas" <craigbowlas yahoo.co.uk> wrote in message
news:0efm30ddcelt3l4jo3hedmll1k1uo6ll71 4ax.com...
 On Mon, 23 Feb 2004 20:02:06 -0800, "Walter" <walter digitalmars.com>
 wrote:

Perhaps you have it on your include path.

"Alexis" <ceo alexisware.com> wrote in message
news:Xns94989F2E94B3Eagolzman 63.105.9.61...
 Hello,

 I get these errors when parsing, and I didn't even use the STL in my
 project yet:





 I have seen this problem too.  The two error directives were because
 the apple config for stlport was being loaded!  I forced the issue by
 a quick mod to stlcomp.h to force the DMC config file to load, this
 lost the #error issues, but the include files still are claimed
 invalid.  This problem was not seen when the SGI version of STL was
 used to build this project.  The project is a windows MFC app, built
 using the IDDE and compiler 8.40.

 Any idea why was the DMC config file was not loaded automatically, and
 what is the problem with the standard include files?


I don't know why. I can't reproduce the problem here.