[issue1006238] cross compile patch

Matthias Klose added the comment: closing this issue. please continue in issue 3754. -- components: +Cross-Build -Build nosy: +doko resolution: -> out of date status: open -> closed ___ Python tracker _

[issue1006238] cross compile patch

wrobell added the comment: Hi Eric, Good point. I was just about ask, which bug and patch are the primary ones? :) -- ___ Python tracker ___ _

[issue1006238] cross compile patch

Éric Araujo added the comment: Hi wrobell. As a new feature, this could not be backported to stable versions. Regarding status, there are currently a number of duplicate or overlapping reports and patches, it’s rather difficult to find out which one should be reviewed. --

[issue1006238] cross compile patch

Senthil Kumaran added the comment: Code compatibility wise there is not much difference between Python3.2 and Python3.3. So you can do it for Python3.2 (in a bitbucket cpython branch) and it is found stable, there are good chances that it will be can be made in Python3.3 and future. I don't thin

[issue1006238] cross compile patch

wrobell added the comment: Senthil, I would be more than happy to do that but for Python 3.2 (or there is no chance to backport it?). Python 3.3 is too far in time at the moment. -- ___ Python tracker

[issue1006238] cross compile patch

Senthil Kumaran added the comment: hello wrobell , I see that issue3754 has patches for more recent line of code and issue 1597850 is related too. Would you like to test the patches in there? If successful, this feature can be pushed further (and considered) for inclusion. -- nosy:

[issue1006238] cross compile patch

wrobell added the comment: What is the current status of this patch? What is missing to apply it upstream? -- nosy: +wrobell ___ Python tracker ___ ___

[issue1006238] cross compile patch

Changes by René Schümann : -- nosy: +WhiteTiger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue1006238] cross compile patch

Changes by David Kern : -- nosy: +David.Kern ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue1006238] cross compile patch

Éric Araujo added the comment: It seemed to me that there were quite a number of messages asking about how to apply the patch and what to do after the configure step. -- ___ Python tracker _

[issue1006238] cross compile patch

Mike Frysinger added the comment: i really dont understand your point. python uses autoconf and therefore any questions about python's usage of autoconf to accomplish cross-compiles is completely valid here. no one was asking for general autoconf help. -- __

[issue1006238] cross compile patch

Éric Araujo added the comment: > Will a new developer be assigned to this bug? If someone is willing to take charge, yes. We’re all volunteers, with varying free time and skill sets. For example, I’m not an expert about compilation, so I try to learn thanks to those issues. > why are we was

[issue1006238] cross compile patch

Jacob Godserv added the comment: I have two questions: Will a new developer be assigned to this bug? And, why are we wasting comments and grave-digging five-year-old discussions? -- ___ Python tracker _

[issue1006238] cross compile patch

Éric Araujo added the comment: See also #3754. Please remember that the bug tracker is meant to develop Python, not offer support about autoconf or patch(1). -- nosy: +eric.araujo versions: +Python 3.3 -Python 3.2 ___ Python tracker

[issue1006238] cross compile patch

Changes by Gregory P. Smith : -- assignee: gregory.p.smith -> nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue1006238] cross compile patch

Mark Lawrence added the comment: As a cross compile patch and being a feature request this must target 3.2. -- nosy: +BreamoreBoy versions: +Python 3.2 -Python 2.7 ___ Python tracker

[issue1006238] cross compile patch

Changes by Ezio Melotti : -- keywords: +needs review stage: test needed -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue1006238] cross compile patch

Jacob Godserv added the comment: The stage of this bug could be changed to "patch review", since a patch is available. -- ___ Python tracker ___ _

[issue1006238] cross compile patch

Jacob Godserv added the comment: This bug affects me as well. Adding myself to CC. -- nosy: +javaJake ___ Python tracker ___ ___ Py

[issue1006238] cross compile patch

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue1006238] cross compile patch

Mike Frysinger added the comment: the chflags is specifically documented as needing a runtime test: # On Tru64, chflags seems to be present, but calling it will # exit Python which is why i left the default of AC_TRY_RUN but cross-compile falls back to a simple link test. btw, a compile test i

[issue1006238] cross compile patch

Gregory P. Smith added the comment: these two have been merged and applied to trunk. """ i fixed the chflags specific check a long time ago (as i imagine others have as well): http://sources.gentoo.org/dev-lang/python/files/python-2.6-chflags- cross.patch same goes for the printf %zd test: htt

[issue1006238] cross compile patch

Garrett Cooper added the comment: Ok. Taking a look at trunk... The following could be converted to AC_TRY_COMPILE statements for the 3rd AC_TRY_RUN tuple: 1. $ac_enable_profiling : 697 2. $ac_cv_no_strict_aliasing_ok : 921 3. $ac_cv_opt_olimit_ok : 1070 4. $ac_cv_olimit_ok : 1092 5. $ac_cv_pt

[issue1006238] cross compile patch

Mike Frysinger added the comment: Gregory: there's no need to be a dick. i'm pointing out the obvious -- bugs have been open literally for *years* with zero assistance/feedback from anyone who can actually get things merged. people have posted patches, but no one has said "xxx needs to be done

[issue1006238] cross compile patch

Garrett Cooper added the comment: On Sun, Nov 1, 2009 at 5:50 AM, Mike Frysinger wrote: > > Mike Frysinger added the comment: > > AC_TRY_RUN is already documented: > http://www.gnu.org/software/autoconf/manual/html_node/Obsolete-Macros.html#index-AC_005fTRY_005fRUN-1992 > > there are a bunch o

[issue1006238] cross compile patch

Gregory P. Smith added the comment: Removing a toxic person from the cc list. Mike, please go harm some other all volunteer project. -- nosy: -vapier ___ Python tracker ___

[issue1006238] cross compile patch

Mike Frysinger added the comment: AC_TRY_RUN is already documented: http://www.gnu.org/software/autoconf/manual/html_node/Obsolete-Macros.html#index-AC_005fTRY_005fRUN-1992 there are a bunch of distros out there (like OE and Gentoo) that have been maintaining cross-compile patches for python.

[issue1006238] cross compile patch

Gregory P. Smith added the comment: Documenting the parameters needed to avoid all AC_TRY_RUNs is a good first step for any that are not obvious how to convert from AC_TRY_RUN into something else. -- ___ Python tracker

[issue1006238] cross compile patch

Garrett Cooper added the comment: I'm trying to resolve this issue on: 2.6-releasemaint trunk 3.1-releasemaint py3k first by resolving issues configure.in, but there are a TON of AC_TRY_RUN's, which means that this code cannot be cross-compiled as-is (25 on 2.x -- 27 on 3.x). Is requiring the

[issue1006238] cross compile patch

Changes by Gregory P. Smith : -- assignee: -> gregory.p.smith nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list ma

[issue1006238] cross compile patch

Garrett Cooper added the comment: Coming back to this issue, I really want to resolve it on TRUNK and for it to make its way into 2.6.3 and 2.x trunk, as well as 3.0.2 and 3.x trunk. I am more than happy to sign a contributor agreement if this will push things along quicker. Thanks, -Garrett -

[issue1006238] cross compile patch

Changes by Thomas Heller : -- nosy: +theller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue1006238] cross compile patch

Roumen Petrov added the comment: Mike, the python configure script fail to detect some of toolchain tools. -- nosy: +rpetrov ___ Python tracker ___ ___

[issue1006238] cross compile patch

Mike Frysinger added the comment: Garrett: your configure method is overly complicated. all you need to do is set --build=binos_c3.4.3-p1.mips64-octeon-linux. autoconf will figure out all the other toolchain settings. ___ Python tracker

[issue1006238] cross compile patch

Garrett Cooper added the comment: Am I correct in this understanding, or is Pgen unneeded after the grammar file is generated? ___ Python tracker ___ __

[issue1006238] cross compile patch

Garrett Cooper added the comment: I can definitely chime in on this issue. A (proper) testcase would be to do something like the following: # Example item -- this isn't what you'll be using... CROSS_COMPILE_PREFIX=binos_c3.4.3-p1.mips64-octeon-linux- AS="${CROSS_COMPILE}as" \ CC="${CROSS_COMP

[issue1006238] cross compile patch

Changes by Daniel Diniz : -- stage: -> test needed type: -> feature request versions: +Python 2.7 -Python 2.3 ___ Python tracker ___ _