On Dec 19, 2012, at 11:57 PM, Matthias Klose wrote:
>hard-coding gcc is wrong. you should use CC and have this code at a position
>where it's clear which CC to use.
>
>if this patch is debian local, you can drop the dpkg-architecture check.
This is actually much simpler than I first though. We a
Am 19.12.2012 21:30, schrieb Barry Warsaw:
> On Dec 19, 2012, at 12:50 PM, Jakub Wilk wrote:
>
>> * Barry Warsaw , 2012-12-14, 16:29:
>>> ++dnl Debian multiarch support in sys.implementation._architecture
>>> ++dnl Try `dpkg-architecture -qDEB_BUILD_MULTIARCH` first, then ++dnl
>>> `gcc --print-m
On Dec 19, 2012, at 12:50 PM, Jakub Wilk wrote:
>* Barry Warsaw , 2012-12-14, 16:29:
>>++dnl Debian multiarch support in sys.implementation._architecture
>>++dnl Try `dpkg-architecture -qDEB_BUILD_MULTIARCH` first, then
>>++dnl `gcc --print-multiarch`.
>>++AC_SUBST(MULTIARCH_BUILD)
>>++AC_CHECK_PR
* Barry Warsaw , 2012-12-14, 16:29:
++dnl Debian multiarch support in sys.implementation._architecture
++dnl Try `dpkg-architecture -qDEB_BUILD_MULTIARCH` first, then
++dnl `gcc --print-multiarch`.
++AC_SUBST(MULTIARCH_BUILD)
++AC_CHECK_PROG(HAS_DPKG_ARCHITECTURE, dpkg-architecture, found, not-fo
Package: python2.7
Version: 2.7.3~rc2-2.1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
We have several cases where the multiarch triplet is needed for the
proper building or functioning of other Python modules or
applications. A recent example is virtualenv.
5 matches
Mail list logo
