Closed Bug 589391 Opened 11 years ago Closed 11 years ago

ensure proper minimum Mac OS X system version is set for each architecture

Categories

(Core :: General, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- beta5+

People

(Reporter: jaas, Assigned: jaas)

Details

Attachments

(2 files)

Attached patch fix v1.0Splinter Review
Currently if you try to run an i386/x86_64 universal binary on Mac OS X 10.5 you'll get a crash when the OS tries to run the x86_64 component of the universal binary, which it does by default. We need to use "LSMinimumSystemVersionByArchitecture" to specify the minimum OS version for each architecture.

"LSMinimumSystemVersionByArchitecture" can be safely used in conjunction with the more general "LSMinimumSystemVersion".
Attachment #468008 - Flags: review?(smichaud)
blocking2.0: --- → beta5+
Note, there shouldn't be any problem specifying the minimum required OS for both i386 and x86_64 even when a binary is not universal and contains only one architecture.
Hmm, this doesn't solve the problem for x86_64-only binaries on 10.5. Apparently "LSMinimumSystemVersionByArchitecture" is not used when the binary is not universal. It doesn't do any harm to have it there, but it doesn't fix the the non-universal x86_64 on 10.5 problem.
Summary: use LSMinimumSystemVersionByArchitecture to set minimum OS per architecture on Mac OS X → ensure proper minimum Mac OS X system version is set for each architecture
Attachment #468008 - Flags: review?(smichaud) → feedback?(smichaud)
Apparently nothing fixes the non-universal x86_64 on 10.5 problem. No combination of "LSMinimumSystemVersion" or "LSMinimumSystemVersionByArchitecture" fixes the problem so we should probably just go with my original patch.
Attachment #468008 - Flags: feedback?(smichaud) → review?(smichaud)
Attachment #468008 - Flags: review?(smichaud) → review+
Attachment #468008 - Flags: review?(ted.mielczarek)
Attachment #468008 - Flags: review?(ted.mielczarek) → review+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.