You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Modify OS X installer builds to package liblzma for the new lzma module #57716
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/ned-deily'closed_at=<Date2012-04-01.07:23:18.112>created_at=<Date2011-11-30.10:07:58.694>labels= ['OS-mac', 'type-feature', 'build']
title='Modify OS X installer builds to package liblzma for the new lzma module'updated_at=<Date2012-04-01.07:23:18.111>user='https://github.com/ned-deily'
Since AFAIK Apple does not currently ship a version of liblzma with Mac OS X, the OS X installer build script should be modified to build and link a version in support of the new lzma module (bpo-6715).
I recently built the xz library on my OSX Tiger buildbot (that also does the daily DMGs via the build script), and Nadeem mentioned this ticket.
As an FYI, I wasn't able to get the xz library (5.0.3) to configure/build as a universal build (i386/ppc) in a single step (as in the build script recipes). It appears to use some compile options incompatible with multiple -arch.
For my buildbot, I built it twice (as i386 and ppc) and then combined the libraries (static and shared) using lipo. This appears to work for both the regular buildbot and the DMG creation.
In peeking at the build script this approach is a bit beyond the current recipe process, so would need more work than just a new recipe. Assuming a build/lipo process is considered legitimate for release installers, of course, I'm not that sure how much I ended up "cheating".
nicholasriley commented on Mar 13, 2012
nicholasrileymannequin
Mannequin
More actions
The configure problem is soluble with --disable-dependency-tracking (it was the -M* options to gcc that caused the problem); something similar is used for SQLite.
Activity
ned-deily commentedon Nov 30, 2011
Since AFAIK Apple does not currently ship a version of liblzma with Mac OS X, the OS X installer build script should be modified to build and link a version in support of the new lzma module (bpo-6715).
Mac/BuildScript/build-installer.py
http://tukaani.org/xz/
db3l commentedon Jan 29, 2012
I recently built the xz library on my OSX Tiger buildbot (that also does the daily DMGs via the build script), and Nadeem mentioned this ticket.
As an FYI, I wasn't able to get the xz library (5.0.3) to configure/build as a universal build (i386/ppc) in a single step (as in the build script recipes). It appears to use some compile options incompatible with multiple -arch.
For my buildbot, I built it twice (as i386 and ppc) and then combined the libraries (static and shared) using lipo. This appears to work for both the regular buildbot and the DMG creation.
In peeking at the build script this approach is a bit beyond the current recipe process, so would need more work than just a new recipe. Assuming a build/lipo process is considered legitimate for release installers, of course, I'm not that sure how much I ended up "cheating".
nicholasriley commentedon Mar 13, 2012
The configure problem is soluble with --disable-dependency-tracking (it was the -M* options to gcc that caused the problem); something similar is used for SQLite.
The attached patch should do it...
python-dev commentedon Apr 1, 2012
New changeset 0e1177499762 by Ned Deily in branch 'default':
Issue bpo-13507: OS X installer builds now build liblzma for the new
http://hg.python.org/cpython/rev/0e1177499762
ned-deily commentedon Apr 1, 2012
Thanks for the patch. Applied to default for 3.3.