[issue9164] 2.7 sysconfig should handle arch duplicates
New submission from Jyrki Wahlstedt :
Hi,
in building Python 2.7 (using MacPorts)I end up in a situation that the build
stops in sysconfig.py due to duplicate arch args on compile line. Compiling
stops, because there is no way to find machine value from ('i386', 'i386',
'x86_64', 'x86_64'). The duplicates should be removed so that
findall-sort-tuple would give only the unique values.
--
components: Build
messages: 109314
nosy: jyrkiwahlstedt
priority: normal
severity: normal
status: open
title: 2.7 sysconfig should handle arch duplicates
type: compile error
versions: Python 2.7
___
Python tracker
<http://bugs.python.org/issue9164>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9164] 2.7 sysconfig should handle arch duplicates while building universal on OS X
Jyrki Wahlstedt added the comment: The fix could be something like replace line 649 in sysconfig.py: archs = tuple(archs) with: archs = tuple(sorted(list(set(archs This removes the duplicates, but as transforming the list to set does not seem to keep order, it is necessary to sort the list (hence the previous line sorting the list could be dropped perhaps). -- title: 2.7 sysconfig should handle arch duplicates -> 2.7 sysconfig should handle arch duplicates while building universal on OS X ___ Python tracker <http://bugs.python.org/issue9164> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9164] 2.7 sysconfig should handle arch duplicates while building universal on OS X
Jyrki Wahlstedt added the comment: The same line appears in Lib/distutils/util.py, line 148, and requires to be treated the same. These are the changes I had to make to get the build done for both 32- and 64-bit architectures. -- ___ Python tracker <http://bugs.python.org/issue9164> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9164] 2.7 sysconfig should handle arch duplicates while building universal on OS X
Jyrki Wahlstedt added the comment: Well, the background here is that at MacPorts the builds are done using Portfiles (I maintain some), and it seems that the current way of getting things configured and built leads to redundant, extraneous arch arguments. I don't know the internals of port system that well as to be able to explain, how the arguments are collected. I am starting to investigate port command to see, if something can be done there. Then, duplicate arguments are not illegal, may be seen elsewhere also, so if this can be dealt with cleanly, I'm happy. I check the configure logs this evening. -- ___ Python tracker <http://bugs.python.org/issue9164> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9164] 2.7 sysconfig should handle arch duplicates while building universal on OS X
Jyrki Wahlstedt added the comment: Ok, here's a bit of the missing information: - as per the first message, I'm not using command line to build, I use MacPorts (having been able to build 2.5, 2.6, and 3.1 with no problems) - I checked some of internal workings (by asking), and MacPorts gives the architecture arguments in several of the make process flags, compilation and link, so the multiple flags come from that - after port configure, there are duplicate architecture flags in Makefile, which seems to just the way the change has been checked So, thanks for putting this in (appear with the next release?) -- status: pending -> open ___ Python tracker <http://bugs.python.org/issue9164> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9164] 2.7 sysconfig should handle arch duplicates while building universal on OS X
Jyrki Wahlstedt added the comment: For some reason I unintentionally managed to change status, putting it back to pending. -- status: open -> pending ___ Python tracker <http://bugs.python.org/issue9164> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24282] 3.5 gdbm extension build fails with "'clinic/_gdbmmodule.c.h' file not found"
New submission from Jyrki Wahlstedt: On OS X (with MacPorts) the following happens: === DEBUG: Environment: CC='/usr/bin/clang' CC_PRINT_OPTIONS='YES' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_Users_jwa_work_macports-trunk_dports_python_py-gdbm/py35-gdbm/work/.CC_PRINT_OPTIONS' CFLAGS='-arch x86_64' CPATH='/opt/local/include' CXX='/usr/bin/clang++' CXXFLAGS='-arch x86_64' F90FLAGS='-m64' FCFLAGS='-m64' FFLAGS='-m64' LDFLAGS='-arch x86_64' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.10' OBJC='/usr/bin/clang' OBJCFLAGS='-arch x86_64' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_Users_jwa_work_macports-trunk_dports_python_py-gdbm/py35-gdbm/work/Python-3.5.0b1/Modules" && /opt/local/Library/Frameworks/Python.framework/Versions/3.5/bin/python3.5 setup.py --no-user-cfg build' DEBUG: Executing command line: cd "/opt/local/var/macports/build/_Users_jwa_work_macports-trunk_dports_python_py-gdbm/py35-gdbm/work/Python-3.5.0b1/Modules" && /opt/local/Library/Frameworks/Python.framework/Versions/3.5/bin/python3.5 setup.py --no-user-cfg build running build running build_ext building '_gdbm' extension creating build creating build/temp.macosx-10.10-x86_64-3.5 /usr/bin/clang -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch x86_64 -I/opt/local/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c _gdbmmodule.c -o build/temp.macosx-10.10-x86_64-3.5/_gdbmmodule.o _gdbmmodule.c:45:10: fatal error: 'clinic/_gdbmmodule.c.h' file not found #include "clinic/_gdbmmodule.c.h" ^ 1 error generated. error: command '/usr/bin/clang' failed with exit status 1 === -- components: Extension Modules messages: 244017 nosy: jwa priority: normal severity: normal status: open title: 3.5 gdbm extension build fails with "'clinic/_gdbmmodule.c.h' file not found" type: compile error versions: Python 3.5 ___ Python tracker <http://bugs.python.org/issue24282> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24282] 3.5 gdbm extension build fails with "'clinic/_gdbmmodule.c.h' file not found"
Jyrki Wahlstedt added the comment: This worked ok in a3… (not in a4 anymore) -- ___ Python tracker <http://bugs.python.org/issue24282> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24282] 3.5 gdbm extension build fails with "'clinic/_gdbmmodule.c.h' file not found"
Jyrki Wahlstedt added the comment: Thanks for the quick follow-up! I'll get the work done at our end:) -- ___ Python tracker <http://bugs.python.org/issue24282> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
