This repository has been archived by the owner on Jun 24, 2022. It is now read-only.
Python 2.6 #6
Open
Python 2.6 #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Comment from Jan:
in target/tools/src/python-2.4.5/setup.py:527 (and below):
db_setup_debug = False # verbose debug prints from this script?
Setup.py looks for /usr/include/*db*3,4*/db.h, which is entirely broken:
it should ask GCC if it can find db.h (and/or look at the include
flags); we are cross compiling and it entirely ignores that option.
This holds for all of the extension modules that are checked here. It
would be nice if we could add %(system_prefix)s for where it looks for
all extensions; on the other hand: trusting GUB's dependencies and
patching Setup.dist is OK too.
This reverts commit aa457a0. The real fix is teaching setup.py about cross compilation.
This reverts commit 48b18f5. The real fix is teaching setup.py about cross compilation.
This also removes the need for dbm and crypt fixes (actually, crypt and nis should not build, as we do not have those libraries in GUB).
Also, rename python-2-6 to python-2.6 and add python-2.4 package.
Fix the compilation of shared python modules, the install target, and the ImportError on "import hashlib" in python 2.6.
Conflicts: gub/specs/python.py lilypond.make
|
Upgrading python from 2.4 has been requested for a couple of years (issue 1895). It would rid us of 2.4 problems and ease the transition to a common python2 and python3 codebase. It's obviously affecting the LilyPond build, so @PhilHolmes can you test this branch and see if you can still build LilyPond? |
|
Issue 1895 mentioned above has been marked as duplicate of LilyPond issue 1079. |
|
Today I launched 'make LILYPOND_BRANCH=stable/2.20 lilypond' on Ubuntu 14.04 i686 (running in VirtualBox) and I got this error: IIUC, it fails because conditional expressions were added in python2.5. @PhilHolmes Have you ever got these errors? Here's the traceback: |
This was referenced Nov 10, 2018
|
I suggest to abandon this pull request since we should rather upgrade to 4.7.x. However, it might serve as an aid in the transition. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is based on Jan's upstream master, but I include here one more python 2.6 fix required to fully build lilypond.