hello,
As you have suggested us to have a local copy of _structs.h, we have copied
it in to /sw/cilkheader (which we have created) and we have included the
following lines in cilk.info file
SetCPPFLAGS: -I%p/cilkheader
Now we could successfully run fink -m rebuild cilk and could install cilk in
our mac machine.
But after installation and creation of cilkc binary, now when we tried
another cilk example, it was again referring to systems's _structs.h in
/usr/include/mach/i386 folder.
How to bypass this and make our cilkc binary to look in to our %p/cilkheader
folder.
Also , we want to test our info file on power pc , but we do not have a
power pc machine. Can anyone of you help us in this regard.
We can mail you the info file.
On Thu, Mar 11, 2010 at 5:26 AM, Max Horn <m...@quendi.de> wrote:
>
> Am 09.03.2010 um 16:55 schrieb Pranay Airan:
>
>
> Hello,
>>
>> I am facing problem while creating info file, i discuss this problem
>> earlier and got some suggestions but still i am unclear how to proceed
>>
>> in my port when porting for MAC while i am compiling any program which
>> includes stdlib.h it gives syntax error, which in turn found to be in
>> usr/include/mach/i386/_structs.h where the error is in parsing Bit fields,
>> as MAX and Alexander pointed that problem is in compiler which is not able
>> to parse this bit fields, i want to know why this bit fields are not present
>> in linux and is this header file structure is same for Power PC as well?
>>
>
> To answer that part of your question: This header file is part of "Mach",
> the kernel of the Mac OS X operating system. As such, this header is a
> non-portable header file, which is specific to Mac OS X; it does not exist
> on other unix-like system, such as Linux or FreeBSD. Normally, no code
> should ever directly include that file, but other system headers might pull
> it in.
>
> It is not same for PowerPC, as the path to the file correctly indicates.
> Its PowerPC counterpart can be found in /usr/include/mach/ppc/_structs.h --
> the 32bit version, that is; besides "i386" and "ppc" there are also "ppc64"
> and "x86_64" which have yet other versions of these headers, for 64bit
> systems.
>
>
> Note that Linux, FreeBSD, Windows, etc., have their own set of
> non-portable, system specific headers. Oh, and quite some of these use bit
> fields, too ;).
>
>
> Cheers,
> Max
>
--
Thanks
Pranay Airan
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
