Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / CodeWarrior / January 2004



Tip: Looking for answers? Try searching our database.

SIGINT, SIGILL etc. redifined errors?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Steve James - 16 Jan 2004 12:08 GMT
Hi,

When compiling a debug version of my Mach-0 project (CW8.3, 10.3.2), I
had errors with redifined macros: SIGINT, SIGILL, SIGABRT etc. (in
sys/signal.h) from netdb.h, and params.h
I tracked the duplicates in csignal (MSL/Common/include), and
temporarily commented them out and everything works OK. (I do need
access to that directory for other headers.)

When I came to compile the release version, though, I have the same
problem even with csignal edited. I've searched everywhere for where
this clash could be but can find no other #defines of these anywhere.
I've even done a complete text content search through my entire disks,
but these do not appear to be defined elsewhere?
So my biggest problem is how to get around this? I need netdb.h, and
params.h because I'm re-using the Apple SimplePing code.

My other concern is why the copies in csignal are defined with different
values to how they are in signal.h? ... and whether or not it is safe to
leave csignal edited like this?

Thanks

Steve
MW Ron - 16 Jan 2004 14:57 GMT
>Hi,
>
[quoted text clipped - 4 lines]
>temporarily commented them out and everything works OK. (I do need
>access to that directory for other headers.)

You did this wrong,  the problem is you don't have the 10.2.7 SDK
installed and your source tree for OS X Volume set to that.

>When I came to compile the release version, though, I have the same
>problem even with csignal edited. I've searched everywhere for where
[quoted text clipped - 7 lines]
>values to how they are in signal.h? ... and whether or not it is safe to
>leave csignal edited like this?

Get the XCode Tools CD,  reinstall it, choose the optional packages  and
there is a 10.2.7 SDK  install that,  you can do this even after doing
the original installation.

In CodeWarrior 8.3  global Preferences...
change your Source Tree for OS X Volume
from
/
to
/Developers/SDKs/MacOSX10.2.7SDK/

You can but don't have to reprecompile any precompiled headers.

Don't forget to undo the changes you made before

If you have to rebuild the libraries for 8.3 in OS X 10.3  do the above
and

NOTE this is an unofficial and non-supported fix.  Since it involves
changing Apple's header

In Apple's Limits.h
in /Developers/SDKs/MacOSX10.2.7SDK/usr/include/ppc/limits.h

Change

#ifndef _PPC_LIMITS_H_
#define _PPC_LIMITS_H_

#define    CHAR_BIT    8        /* number of bits in a char */
#define    MB_LEN_MAX    6        /* Allow 31 bit UTF2 */

#define    CLK_TCK        100        /* ticks per second */

to

#ifndef _PPC_LIMITS_H_
#define _PPC_LIMITS_H_

#define    CLK_TCK        100        /* ticks per second */

#if !_MSL_USING_MW_C_HEADERS

#define    CHAR_BIT    8        /* number of bits in a char */
#define    MB_LEN_MAX    6        /* Allow 31 bit UTF2 */

At the end of the file add
#endif  /* _MSL_USING_MW_C_HEADERS */
before
#endif /* _PPC_LIMITS_H_ */

Rebuild the precompiled headers and rebuild the MSL Mac OS X libraries

You should be OK

Signature

Metrowerks, maker of CodeWarrior   -  "Software Starts Here"  
Ron Liechty - MWRon@metrowerks.com - <http://www.metrowerks.com>

Steve James - 19 Jan 2004 11:30 GMT
Thanks for the help, but unfortunately there are some changes in the
CoreAudio headers between 10.2.7 and 10.3 (e.g.
kAudioFileGlobalInfo_WritableTypes), so all my CoreAudio
stuff is messed up now too.
I could probably find a workaraound for this too, but I can see it's
going to end up a world of hurt.

Are all these clashes/issues solved in CW9?
I'm perfectly happy to upgrade, but am keen to know that it would be a
remedy.

Thanks

Steve

>>Hi,
>>
[quoted text clipped - 74 lines]
>
> You should be OK
MW Ron - 19 Jan 2004 16:01 GMT
>Thanks for the help, but unfortunately there are some changes in the
>CoreAudio headers between 10.2.7 and 10.3 (e.g.
>kAudioFileGlobalInfo_WritableTypes), so all my CoreAudio
>stuff is messed up now too.

You can't do the 10.3 specifics with CodeWarrior 8.3 it won't work you
have to stick with the 10.2.7 SDK

>I could probably find a workaraound for this too, but I can see it's
>going to end up a world of hurt.
>
>Are all these clashes/issues solved in CW9?
>I'm perfectly happy to upgrade, but am keen to know that it would be a
>remedy.

I haven't seen any problems with a properly set up project on 10.3 with
CW 9.1.  Without some example project I can run I can't guarantee
anything bit I don't recall any problems.

Ron

>>>Hi,
>>>
[quoted text clipped - 4 lines]
>>>temporarily commented them out and everything works OK. (I do need
>>>access to that directory for other headers.)

Signature

Metrowerks, maker of CodeWarrior   -  "Software Starts Here"  
Ron Liechty - MWRon@metrowerks.com - <http://www.metrowerks.com>

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.