Re: procps doesn't buildd - /lib versus /lib64
On Mon, 2004-03-01 at 12:31, David S. Miller wrote:
> On 01 Mar 2004 09:28:51 -0500
> Albert Cahalan <firstname.lastname@example.org> wrote:
> > 1. make -m64 the default, as x86-64 does
> x86-64 does this because this generates the most efficient code
> (due to access to more registers etc.),
> not because it makes the build environment better or worse to
> deal with for people in your situation.
I'm sure that's a factor. The choice is also more
It would be possible to make an ILP32 x86-64 ABI
using 32-bit pointers in 64-bit mode if you really
wanted performance. Where do those libraries go?
The same problem appears for i386 if you wanted to
change the calling convention to something modern.
(maybe -regparm=3 plus floats in SSE2 registers)
Anyway, how about the idea of having the "install"
program remap things? It could be configurable
based on a file in /etc that defines mappings for
directories and perhaps other things. Then neither
the Debian procps packager nor I would have much
need to deal with this issue; as of now it's looking
like Debian's 32-bit sparc build will require:
make lib64=lib ALL_CFLAGS=-O2 ...
(a native build on 32-bit sparc would not require this)
> PPC64 is doing the same thing as sparc64, or something similar,
> is it not?
Yes, but PPC64 needs an ABI change for other reasons anyway.
It's using an old POWER ABI with Itanic-style function
descriptors and some other slow oddities I forget now.