This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: PythonLauncher universal build fails due to missing -arch and -sysroot
Type: compile error Stage:
Components: macOS Versions: Python 3.1, Python 3.2, Python 2.7, Python 2.6
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: ronaldoussoren Nosy List: ned.deily, ronaldoussoren
Priority: normal Keywords:

Created on 2010-04-19 13:43 by ned.deily, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
issue-python-launcher-arch.txt ned.deily, 2010-04-19 13:43
Messages (2)
msg103594 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2010-04-19 13:43
Fixes for Issue8366 corrected build failures with universal builds on OS X due to changes in the settings of CFLAGS and BASECFLAGS, which had caused -arch values to be added to both CFLAGS and BASECFLAGS.  The Mac Makefile for the PythonLauncher app needs to be changed as well, otherwise universal builds can now fail with errors like:

ld warning: in FileSettings.o, file is not of required architecture
ld warning: in MyAppDelegate.o, file is not of required architecture
ld warning: in MyDocument.o, file is not of required architecture
ld warning: in PreferencesWindowController.o, file is not of required architecture
ld warning: in doscript.o, file is not of required architecture
ld warning: in main.o, file is not of required architecture
Undefined symbols for architecture i386:
  "_main", referenced from:
      __start in crt1.o
ld: symbol(s) not found for architecture i386

The attached patch corrects the problem.
msg103755 - (view) Author: Ronald Oussoren (ronaldoussoren) * (Python committer) Date: 2010-04-20 20:54
I've fixed this issue in all branches and can now do clean builds.

BTW. Builds with the 10.4u SDK on OSX fail at the moment for 2.7 and 3.2, that's due to issue 7724, I've attached a patch to that issue that should fix it (for the trunk, porting it to 3.2 should be trivial).
History
Date User Action Args
2022-04-11 14:57:00adminsetgithub: 52707
2010-04-20 20:54:04ronaldoussorensetstatus: open -> closed
resolution: fixed
messages: + msg103755
2010-04-19 13:43:41ned.deilycreate