Re: Determining how the app is run (intel/ppc/rosetta/os version)?
Re: Determining how the app is run (intel/ppc/rosetta/os version)?
- Subject: Re: Determining how the app is run (intel/ppc/rosetta/os version)?
- From: Gerben Wierda <email@hidden>
- Date: Sat, 27 May 2006 00:23:34 +0200
On May 26, 2006, at 23:45, glenn andreas wrote:
On May 26, 2006, at 2:48 PM, Gerben Wierda wrote:
My app contains:
x86 binary compiled with gcc 4 against 10.4 SDK
ppc binary compiled with gcc 3 against the 10.3 SDK to make sure it
is compatible with 10.3 on ppc
The ppc binary is a known trigger of the partial OS freeze bug of
10.4.6
The x86 binary does not work properly on 10.4.4 - 10.4.6 (on x86)
[Note: if I compile the ppc with gcc 4 against the 10.4 SDK it also
does not work properly on ppc hardware. This seems to be a
myApp/Tiger issue which does not occur when I compile with gcc3
against the 10.3 SDK. I do not know yet what triggers it)
So, I want to make sure that the app
- exits with a warning when run in rosetta on 10.4.6
- exits with a warning when run natively on 10.4.4-10.4.6 (assuming
that 10.4.7 will be OK again and I have good reason to hope so)
So basically it appears that you're saying that the Intel version
doesn't work on any shipping system (and may, or may not, on a future
system). So why is it even a universal app? Definitely seems easier
to just ship a PPC only version until an OS version has been publicly
released that you've qualified as working (rather than shipping code
that requires an untested unreleased OS).
My code worked fine up to 10.4.3 on the Developer Tranistion Kit, both
natively and with Rosetta. You can imagine my surprise that when Apple
did ship the first intel macs with 10.4.4 my ap got problems. I reacted
by releasing a ppc-only version and contacting Apple to find out what
was the cause of the problem (either something boneheaded by me or an
OS problem).
The ppc-version triggers the 10.4.6 partial freeze bug on intel
systems. Hence, the current situation is:
10.2.8 - ran fine until I discontinued 10.2 last January (this code
has seen quite a bit of use, starting with 10.1 even for a previous
version)
10.3.9 - runs fine
10.4.2/3 - (DTK) runs fine natively and with Rosetta
10.4.4/5 - runs fine with ppc linked against 10.3.9 SDK, problems when
running x86 natively
10.4.6 - triggers the partial freeze bug when ppc linked against
10.3.9 SDK is run with rosetta, might be ok natively with intel (I was
unable to reproduce the intermittent bug that happened on 10.4.4 and
10.4.5 so something improved on the x86 side) but as long as the source
of that problem is not known, I am wary.
As an Apple Developer I know what the situation is with the 10.4.7
seed, but I cannot comment specifics here.
G
PS. I experience this list as not a very friendly one. Basically,
people seem to have very short fuses when they suspect (but do not
know) stupid newbie behaviour. If I had known that, I would have not
asked my original question like I did but put the
explanations/apologies in beforehand. I know this list has some very
knowledgeable people, but the reactions I get on a simple technical
question are rather negative in tone and often not about the question
or technical issue at hand. I ask a simple question I have to defend
myself first why I should ever need the information, that I should not
release my code anyway, etc. In my opinion, such talk is better left
for cocoa-talk or cocoa-dev-talk if such lists exist. The assumption
behind many replies seem to be on the negative side. Maybe some
subscribers feel that they have to guard the OS for stupid code to
appear on it?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden