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.

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

Python fails to compile with VC11 ARM configuration #59007

Closed
gongminmin mannequin opened this issue May 14, 2012 · 8 comments
Closed

Python fails to compile with VC11 ARM configuration #59007

gongminmin mannequin opened this issue May 14, 2012 · 8 comments
Labels
3.8 only security fixes build The build process and cross-build OS-windows type-feature A feature request or enhancement

Comments

@gongminmin
Copy link
Mannequin

gongminmin mannequin commented May 14, 2012

BPO 14802
Nosy @loewis, @pitrou, @ned-deily, @briancurtin, @zware, @gongminmin, @zooba
PRs
  • bpo-35758: Fix building on ARM + MSVC #11531
  • bpo-35758: Fix building on ARM + MSVC #11531
  • bpo-35758: Fix building on ARM + MSVC #11531
  • bpo-35758: Fix building on ARM + MSVC #11531
  • 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 = None
    closed_at = <Date 2019-01-21.20:51:00.702>
    created_at = <Date 2012-05-14.03:57:24.843>
    labels = ['type-feature', '3.8', 'OS-windows', 'build']
    title = 'Python fails to compile with VC11 ARM configuration'
    updated_at = <Date 2019-01-21.21:50:14.108>
    user = 'https://github.com/gongminmin'

    bugs.python.org fields:

    activity = <Date 2019-01-21.21:50:14.108>
    actor = 'ned.deily'
    assignee = 'none'
    closed = True
    closed_date = <Date 2019-01-21.20:51:00.702>
    closer = 'pitrou'
    components = ['Build', 'Windows']
    creation = <Date 2012-05-14.03:57:24.843>
    creator = 'Minmin.Gong'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 14802
    keywords = ['patch', 'patch', 'patch', 'patch']
    message_count = 8.0
    messages = ['160593', '160627', '160687', '222666', '222671', '222705', '334177', '334185']
    nosy_count = 7.0
    nosy_names = ['loewis', 'pitrou', 'ned.deily', 'brian.curtin', 'zach.ware', 'Minmin.Gong', 'steve.dower']
    pr_nums = ['11531', '11531', '11531', '11531']
    priority = 'normal'
    resolution = 'fixed'
    stage = 'resolved'
    status = 'closed'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue14802'
    versions = ['Python 3.8']

    @gongminmin
    Copy link
    Mannequin Author

    gongminmin mannequin commented May 14, 2012

    Windows ARM doesn't support full win32 api, e.g. no registry and winsock. So the python fail to compile with VC11 beta in ARM configuration.

    @gongminmin gongminmin mannequin added interpreter-core (Objects, Python, Grammar, and Parser dirs) build The build process and cross-build labels May 14, 2012
    @briancurtin
    Copy link
    Member

    Thanks for your report. Unfortunately Python 3.2 won't ever work in this way because changing compilers would be a new feature, and bug fix releases like 3.2 don't receive new features. Yesterday we completed the transition to VS2010 as a step towards our 3.3 release.

    We are open to supporting VS11, but it won't become the standard compiler suite we use until VS11 goes RTM. I'm not aware of any release schedule announced yet, but I believe we would need VS11 to be released before our first beta release, which is at the end of June. Most estimates I've seen don't look favorable for us supporting it in 3.3.

    Another issue that may hinder this is that myself, and as far as I know, the other developers, do not have ARM machines available to them. I'm interested in continuing our transition from VS2010 on to VS11 for when it's ready, but anything ARM related will likely require someone else to help out, maybe even you :)

    @briancurtin briancurtin added build The build process and cross-build OS-windows and removed interpreter-core (Objects, Python, Grammar, and Parser dirs) labels May 14, 2012
    @bitdancer bitdancer changed the title Python 3.2 fail to compile with VC11 ARM configuration Python fails to compile with VC11 ARM configuration May 14, 2012
    @bitdancer bitdancer added type-feature A feature request or enhancement and removed build The build process and cross-build labels May 14, 2012
    @loewis
    Copy link
    Mannequin

    loewis mannequin commented May 15, 2012

    In any case, there is a branch supporting Python as a metro app at

    http://hg.python.org/sandbox/loewis#win8app

    This may get folded back into Python at some point, but certainly not before Windows 8 is released.

    @BreamoreBoy
    Copy link
    Mannequin

    BreamoreBoy mannequin commented Jul 10, 2014

    Can we close this due to the extensive work being done by Steve and Zach on the Windows build environment that I believe are covered by other issues?

    @loewis
    Copy link
    Mannequin

    loewis mannequin commented Jul 10, 2014

    None of this work affects WinRT. I don't know whether support of WinRT is a goal, but it is certainly not a solved problem.

    @zooba
    Copy link
    Member

    zooba commented Jul 10, 2014

    The build environment won't help here, this requires some significant rewrites within Python to remove usage of Windows APIs that don't work under the WinRT sandbox (similar to the projects to embed Python in Chromium et al.)

    I'd still like to see it done, but it's a huge task that is probably never going to be tackled by python-dev directly.

    @pitrou
    Copy link
    Member

    pitrou commented Jan 21, 2019

    Fixed in master branch. Thank you, Minmin Gong!

    I don't think this is a candidate for a 3.7 backport. If you think otherwise, though, please say so. You'll also need to check that the backport enables proper compilation on ARM.

    @pitrou pitrou added the 3.8 only security fixes label Jan 21, 2019
    @pitrou pitrou closed this as completed Jan 21, 2019
    @ned-deily
    Copy link
    Member

    Unless Steve thinks otherwise, I agree that this isn’t a candidate for backporting to 3.7 without all the work to fully support new platform configurations.

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    3.8 only security fixes build The build process and cross-build OS-windows type-feature A feature request or enhancement
    Projects
    None yet
    Development

    No branches or pull requests

    5 participants