Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Python 2.7.5's distutils pass -R to clang #16376

Closed
nexttime mannequin opened this issue May 17, 2014 · 5 comments
Closed

Python 2.7.5's distutils pass -R to clang #16376

nexttime mannequin opened this issue May 17, 2014 · 5 comments
Labels
c: build c: packages: standard p: major / 3 t: bug

Comments

@nexttime
Copy link
Mannequin

nexttime mannequin commented May 17, 2014

This breaks e.g. building the _sqlite3 extension module, such that installation of elliptic_curves fails as well.

Attached patch is as ugly as what's already there.

Component: packages: standard

Keywords: _sqlite3 build import error elliptic_curves

Author: Leif Leonhardy

Reviewer: Volker Braun

Issue created by migration from https://trac.sagemath.org/ticket/16376
@nexttime nexttime mannequin added this to the sage-6.3 milestone May 17, 2014
@nexttime
Copy link
Mannequin Author

nexttime mannequin commented May 17, 2014

Attachment: python-2.7.5-distutils_fix_-R_for_clang.patch.gz

To be put into build/pkgs/python/patches/.

@nexttime
Copy link
Mannequin Author

nexttime mannequin commented May 17, 2014

comment:1

No branch here yet, but still...

@nexttime nexttime mannequin added the s: needs review label May 17, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@a-andre
Copy link

a-andre commented Aug 19, 2014

comment:3

_sqlite3 module and elliptic_curves were built fine here using clang 3.4.2 (and python 2.7.8) without applying the patch.

@a-andre a-andre removed this from the sage-6.4 milestone Aug 19, 2014
@nexttime
Copy link
Mannequin Author

nexttime mannequin commented Aug 19, 2014

comment:4

So apparently this got fixed upstream (such that the patch does no longer apply anyway?).

Can't check this right now, will probably do later.

@vbraun
Copy link
Member

vbraun commented Oct 25, 2014

Reviewer: Volker Braun

@vbraun vbraun closed this as completed Oct 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: build c: packages: standard p: major / 3 t: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vbraun @a-andre