X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Wed, 16 Sep 2015 23:55:46 +0200 (CEST) From: Roland Lutz To: "Hannu Vuolasaho (vuokko AT msn DOT com) [via geda-user AT delorie DOT com]" Subject: RE: [geda-user] New experimental netlist features In-Reply-To: Message-ID: References: ,<55E8773B DOT 9000902 AT jump-ing DOT de>,,<55E8831A DOT 8050307 AT jump-ing DOT de>,,<55E891FA DOT 2010509 AT jump-ing DOT de>,,<55E8AE6C DOT 2090304 AT jump-ing DOT de>,,,,<55F9C1BF DOT 9030603 AT jump-ing DOT de>,,, User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Thu, 17 Sep 2015, Hannu Vuolasaho (vuokko AT msn DOT com) [via geda-user AT delorie DOT com] wrote: > configure fails; > > checking for a Python interpreter with version>= 2.7... python > checking for python... /usr/bin/python > checking for python version... 3.4 > checking for python platform... linux > checking for python script directory... ${prefix}/lib/python3.4/site-packages > checking for python extension module directory... ${exec_prefix}/lib/python3.4/site-packages > checking python3.4/Python.h usability... no > checking python3.4/Python.h presence... no > checking for python3.4/Python.h... no > configure: error: python headers not found > configure: error: ./configure failed for xorn This appears to be a combination of two bugs in AM_PATH_PYTHON: 1.) It interprets its argument as a minimum version; there is no way to specify a maximum version. Consequentially, it selects Python 3.4 when it should select Python 2.7. 2.) It detects Python 3.4 as installed while it's actually just the minimal subset which is installed (python3.4m vs. python3.4). Given that the macro itself isn't too complex, I guess the easiest way to fix this would be to include a custom version of the macro in the repository. I'll look into this tomorrow.