➜
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.
Created on 2010-02-08 09:02 by global667, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| build.txt | global667, 2010-02-08 09:02 | Complete build process | ||
| Messages (3) | |||
|---|---|---|---|
| msg99040 - (view) | Author: WK. (global667) | Date: 2010-02-08 09:02 | |
get followed while compiling with $ /configure --with-universal-archs="64-bit" $ make #warning Building for Intel with Mac OS X Deployment Target < 10.4 is invalid. See attachment for complete build process. |
|||
| msg99095 - (view) | Author: WK. (global667) | Date: 2010-02-09 08:40 | |
Should use setup.py instead of make. |
|||
| msg99097 - (view) | Author: Ronald Oussoren (ronaldoussoren) *  |
Date: 2010-02-09 08:51 | |
I don't understand the second message: you should use make instead of setup.py during the build/installation of python from source. The build warnings are harmless, although you aren't building what you think you are. The configure line should be "./configure --enable-universalsdk=/ --with-universal-archs=64-bit", the with-universal-archs option is ignored without enabling the universalsdk. Note that 2.7 and 3.2 (an possibly 2.6.5) will complain when you specify --with-universal-archs without specifying --enable-universalsdk. (Keeping the issue closed because there doesn't seem to be a real issue) |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:57 | admin | set | github: 52130 |
| 2010-02-09 08:51:15 | ronaldoussoren | set | resolution: works for me messages: + msg99097 |
| 2010-02-09 08:40:34 | global667 | set | status: open -> closed messages: + msg99095 |
| 2010-02-08 09:02:57 | global667 | create | |