Hi Andy, Ralf, et al.,
On Mon, Dec 20, 2010 at 6:23 AM, Andy Wingo wrote:
>> How much understanding of the machinery should be expected
>> of the hapless project builder?
>
> I'm not sure, but: .
I am sure of this: It needs to be minimized. If there are insurmountable
problems in figur
On 12/20/2010 07:59 AM, Bruce Korb wrote:
> Hi Andy, Ralf, et al.,
>
> On Mon, Dec 20, 2010 at 6:23 AM, Andy Wingo wrote:
>>> How much understanding of the machinery should be expected
>>> of the hapless project builder?
>>
>> I'm not sure, but: .
>
> I am sure of this: It needs to be m
On Mon, 20 Dec 2010, Eric Blake wrote:
If a distro insists on shipping 64-bit libraries under /usr/lib64, then
it would be ...
This is not so much a "distro insisting" but rather the Linux file system
standard for bi-arch systems!
Regards
Peter Breitenlohner
On 12/20/2010 03:59 PM, Bruce Korb wrote:
Hi Andy, Ralf, et al.,
(With my Fedora Packaging Committee member hat on) In Fedora
and RHEL, users are supposed to pass
--libdir=/usr/lib64 to configure
on x86_64 and
It is unclear that you-all can do otherwise, without having OSX-style
mixed word si
On 12/20/2010 04:12 PM, Peter Breitenlohner wrote:
On Mon, 20 Dec 2010, Eric Blake wrote:
If a distro insists on shipping 64-bit libraries under /usr/lib64, then
it would be ...
This is not so much a "distro insisting" but rather the Linux file system
standard for bi-arch systems!
multi-arch
On 12/20/2010 04:05 PM, Eric Blake wrote:
On 12/20/2010 07:59 AM, Bruce Korb wrote:
Hi Andy, Ralf, et al.,
On Mon, Dec 20, 2010 at 6:23 AM, Andy Wingo wrote:
How much understanding of the machinery should be expected
of the hapless project builder?
I'm not sure, but: .
I am sure
On 12/20/2010 08:36 AM, Ralf Corsepius wrote:
>> If a distro insists on shipping 64-bit libraries under /usr/lib64, then
>> it would be in the distro's best interest to also ship a config.site
>> variable that defaults --libdir to the appropriate /usr/lib64 location.
>
> This isn't of much help on
On 12/20/2010 04:41 PM, Eric Blake wrote:
On 12/20/2010 08:36 AM, Ralf Corsepius wrote:
If a distro insists on shipping 64-bit libraries under /usr/lib64, then
it would be in the distro's best interest to also ship a config.site
variable that defaults --libdir to the appropriate /usr/lib64 locat
Howdy,
It is feeling like circular responsibilities to me.
So far, the circle seems unbroken. Let's start by
enumerating the ways of breaking it and then, perhaps,
figure out the easiest way. Currently, it is actually
broken by users having to know that for a particular
distribution, they have t
On 2010-12-20 08:54 -0800, Bruce Korb wrote:
> If the default build is 64 bit, why does it make sense that the
> default library directory is the 32 bit library?
As far as I know, the only reason for this design is to avoid breaking
32-bit proprietary software with /usr/lib paths hardcoded into th
On 12/20/2010 10:54 AM, Bruce Korb wrote:
If the default build is 64 bit, why does it make sense that the
default library directory is the 32 bit library?
Because the user may not be building for multiple architectures, in
which case a default of $prefix/lib for libdir makes perfect sense an
On 12/20/10 09:11, Nick Bowler wrote:
> On 2010-12-20 08:54 -0800, Bruce Korb wrote:
>> If the default build is 64 bit, why does it make sense that the
>> default library directory is the 32 bit library?
>
> As far as I know, the only reason for this design is to avoid breaking
> 32-bit proprietar
On 12/20/10 11:20, Ralf Wildenhues wrote:
> * Bruce Korb wrote on Mon, Dec 20, 2010 at 03:09:48PM CET:
>> How much understanding of the machinery should be expected
>> of the hapless project builder?
>
> I've skimmed most of the conversation in this thread now.
>
> The crucial part, I think,
13 matches
Mail list logo
