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.

Author db3l
Recipients db3l, nadeem.vawda, ned.deily, ronaldoussoren
Date 2012-01-29.20:52:12
SpamBayes Score 5.2343367e-08
Marked as misclassified No
Message-id <1327870333.29.0.727263784515.issue13507@psf.upfronthosting.co.za>
In-reply-to
Content
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".
History
Date User Action Args
2012-01-29 20:52:13db3lsetrecipients: + db3l, ronaldoussoren, nadeem.vawda, ned.deily
2012-01-29 20:52:13db3lsetmessageid: <1327870333.29.0.727263784515.issue13507@psf.upfronthosting.co.za>
2012-01-29 20:52:12db3llinkissue13507 messages
2012-01-29 20:52:12db3lcreate