We've experienced this same error. Of course, you can avoid it by
building against the "10.4 SDK" but that doesn't help you if you want
to build against the system headers.
Also, I tried the fix about ordering the access paths and received the
discouraging but descriptive error:
"#error You must have the non-MSL C header file access path before the
MSL access path"
.... in the "stddef.h" MSL header.
I tried building against the Mac OS X10.5 developer preview system
headers, and received similar errors.
Anyone know what we can do here?
- Dave
Howard Hinnant wrote:
> In article <1155745183.863416.201800@[EMAIL PROTECTED]
>,
> "Robert" <justnacl@[EMAIL PROTECTED]
> wrote:
>
> > We still build our older toolkit with CW on PPC macs and recently
> > upgraded to Xcode 2.4. When rebuilding the CW libraries and
> > pre-compiled headers we got an error:
> >
> > CodeWarrior gives a "type cannot be made with a global register
> > variable" error about the __asm("_scalb$UNIX2003" ) construct on line
> > 647 of math.h in Xcode 2.4. I show the relevant lines of math.h from
> > 2.3 and 2.4 below. Although the BuildLibraries.mcp projects built,
when
> > I tried to build the
> > Build.MacOSX.mcp->BuildMacOSXSup****t.mcp->MacHeadersMach-O.mcp
> > precompiled headers, it gave the math.h error about 18 times. This
did
> > not stop the rest of the build, but that may be because I already had
> > libraries.
> >
> > We are running MacOS 10.4.7 on a G5 iMac.
> >
> > Anyone seen this? Have a fix? It would be nice if Apple kept stuff out
> > of the standard headers that broke other compilers (obsolete or not).
>
> Inspect your access paths preference panel. Ensure that the order of
> your access paths is:
>
> {Compiler}MSL/MSL_C
> {OS X Volume}usr/include
>
> and not vice-versa.
>
> -Howard
|
