Adam Borowski kilobyte at angband.pl writes:
This looks just like the solution ultimately chosen for #682183, except for
the include being monstrous. Let's instead add a file to libc6-dev with
the following:
#define DEB_HOST_MULTIARCH x86_64-linux-gnu
And then #include DEB_HOST_MULTIARCH
On Thu, 2013-01-17 at 12:06 +, Thorsten Glaser wrote:
Adam Borowski kilobyte at angband.pl writes:
This looks just like the solution ultimately chosen for #682183, except for
the include being monstrous. Let's instead add a file to libc6-dev with
the following:
#define
On Thu, Jan 17, 2013 at 01:21:41PM +, Ben Hutchings wrote:
On Thu, 2013-01-17 at 12:06 +, Thorsten Glaser wrote:
Adam Borowski kilobyte at angband.pl writes:
#define DEB_HOST_MULTIARCH x86_64-linux-gnu
And then #include DEB_HOST_MULTIARCH /foo/bar.h or what?
Is that even
On Thu, Jan 17, 2013 at 08:51:34AM +0800, Paul Wise wrote:
Would it be possible to use something similar to the bits/ dir in
eglibc? Or would your proposal replace that?
/usr/include/python2.7/bits - /usr/include/x86_64-linux-gnu/python2.7/bits
Not Multi-Arch: same safe. (Note how
On Wed, Jan 16, 2013 at 03:28:53PM -0800, Russ Allbery wrote:
Matthias Klose d...@debian.org writes:
There are some issues when you do have an architecture dependent header
file which needs to be in the multiarch specific include directory. If
the header file is directly located in
There are some issues when you do have an architecture dependent header file
which needs to be in the multiarch specific include directory. If the header
file is directly located in /usr/include, then moving it to
/usr/include/multiarch-tuple usually is not a problem (except for quoting
issues as
On Wed, Jan 16, 2013 at 11:32:45PM +0100, Matthias Klose wrote:
There are some issues when you do have an architecture dependent header file
which needs to be in the multiarch specific include directory. If the header
file is directly located in /usr/include, then moving it to
Matthias Klose d...@debian.org writes:
There are some issues when you do have an architecture dependent header
file which needs to be in the multiarch specific include directory. If
the header file is directly located in /usr/include, then moving it to
/usr/include/multiarch-tuple usually is
Would it be possible to use something similar to the bits/ dir in
eglibc? Or would your proposal replace that?
/usr/include/python2.7/bits - /usr/include/x86_64-linux-gnu/python2.7/bits
And in /usr/include/python2.7/*
#include python2.7/bits/foo.h
--
bye,
pabs
http://wiki.debian.org/PaulWise
9 matches
Mail list logo