* Simon McVittie s...@debian.org [110408 22:23]:
On Fri, 08 Apr 2011 at 21:51:03 +0200, Bill Allombert wrote:
Requiring the user to pass -I to the compiler should be discouraged.
I disagree: independently of multiarch, many libraries do this deliberately
to allow for parallel-installation,
Steve Langasek vor...@debian.org writes:
Hi there,
On Wed, Mar 23, 2011 at 03:05:53AM +, Wookey wrote:
The Multiarch specification only covers libraries and does not
specifically deal with include files.
To make multiarch useful for cross-building as well as co-installation of
On Fri, Apr 08, 2011 at 07:44:27PM +0200, Goswin von Brederlow wrote:
On Wed, Mar 23, 2011 at 03:05:53AM +, Wookey wrote:
The Multiarch specification only covers libraries and does not
specifically deal with include files.
To make multiarch useful for cross-building as well as
On Sat, Apr 02, 2011 at 01:14:28AM -0700, Steve Langasek wrote:
Hi there,
On Wed, Mar 23, 2011 at 03:05:53AM +, Wookey wrote:
The Multiarch specification only covers libraries and does not
specifically deal with include files.
To make multiarch useful for cross-building as well
Steve Langasek vor...@debian.org writes:
On Fri, Apr 08, 2011 at 07:44:27PM +0200, Goswin von Brederlow wrote:
On Wed, Mar 23, 2011 at 03:05:53AM +, Wookey wrote:
The Multiarch specification only covers libraries and does not
specifically deal with include files.
To make multiarch
On Fri, 08 Apr 2011 at 21:51:03 +0200, Bill Allombert wrote:
Requiring the user to pass -I to the compiler should be discouraged.
I disagree: independently of multiarch, many libraries do this deliberately
to allow for parallel-installation, and use pkg-config to give out appropriate
CFLAGS.
On Fri, Apr 08, 2011 at 09:51:03PM +0200, Bill Allombert wrote:
I already made this comment, but I strongly think it should be normative.
Specifically we should mandate that:
1) /usr/include/triplet be added to the default hearder search path of
triplet-gcc.
It seems strange to me that we
On Fri, Apr 08, 2011 at 10:17:20PM +0200, Goswin von Brederlow wrote:
What could be allowed is using the new include paths with a Depends on
the multiarch package even if the package itself is not multiarch.
No. multiarch-support declares runtime support for ld.so. It has nothing
to do
On Fri, Apr 08, 2011 at 02:01:33PM -0700, Steve Langasek wrote:
On Fri, Apr 08, 2011 at 09:51:03PM +0200, Bill Allombert wrote:
I already made this comment, but I strongly think it should be normative.
Specifically we should mandate that:
1) /usr/include/triplet be added to the default
Hi there,
On Wed, Mar 23, 2011 at 03:05:53AM +, Wookey wrote:
The Multiarch specification only covers libraries and does not
specifically deal with include files.
To make multiarch useful for cross-building as well as co-installation of
libraries we need to install headers to
On Wed, Mar 23, 2011 at 11:02:59AM +, Simon McVittie wrote:
On Wed, 23 Mar 2011 at 03:05:53 +, Wookey wrote:
To make multiarch useful for cross-building as well as co-installation of
libraries we need to install headers to /usr/include/triplet, which
needs an FHS exception.
Some
On Wed, 23 Mar 2011 at 03:05:53 +, Wookey wrote:
To make multiarch useful for cross-building as well as co-installation of
libraries we need to install headers to /usr/include/triplet, which
needs an FHS exception.
Some libraries (notably GLib and D-Bus) already isolate their
The Multiarch specification only covers libraries and does not
specifically deal with include files.
To make multiarch useful for cross-building as well as co-installation of
libraries we need to install headers to /usr/include/triplet, which
needs an FHS exception.
Here is a patch to policy
13 matches
Mail list logo
