Re: Curiosity
Re: Curiosity
- Subject: Re: Curiosity
- From: <email@hidden>
- Date: Wed, 21 Dec 2005 17:46:08 -0500
- Bounce-to: <email@hidden>
Ok, so if I change the setting in xcode to compile for intel, what else
do I have to do to get it to actually compile for intel, and bare in
mind when I built this tool I turned off ppc all together it was not
compiled as a fat file.
Mark
On 12/21/2005, "Shawn Erickson" <email@hidden> wrote:
>
>On Dec 21, 2005, at 2:28 PM, <email@hidden>
><email@hidden> wrote:
>
>>
>> Ok... The other day I was testing a theory. I am on a G5 right now,
>> but
>> using the newest XCode. I set it up to build for intel and not ppc. I
>> then built a bsd commandline tool.
>>
>> main()
>> {
>> print("Test successful");
>> }
>>
>> When compiled it runs perfectly on my G5. Odd since it was compiled
>> for
>> intel.
>
>Try running lipo on the resulting tool. I bet it has PPC in it. For
>example...
>
>QuadG5:~ shawnce$ lipo -info /bin/cp
>Non-fat file: /bin/cp is architecture: ppc
>
>> The theory though was that a clu independant of the api's for
>> linux/windows/mac etc. would run on Redhat or other similar oses.
>> but in
>> RH i get the unable to execute binary.
>
>You built an MACH-O formatted binary which Linux doesn't know how to
>parse (at least not out of the box).
>
>> So why, if I compile for intel
>> does it work on the ppc machine and not the intel box. or at least
>> attempt to run on the intel box?
>
>I doubt it was a pure intel binary if it ran on your PowerPC system.
>
>-Shaw
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden