1 |
could we also get a LIBDIR into this spec? something where we could edit |
2 |
the profile to say: |
3 |
|
4 |
[ "$ARCH" == "amd64" ] && ARCH_LIBDIR="lib64" |
5 |
[ "$ARCH" == "x86" ] && ARCH_LIBDIR="lib" |
6 |
|
7 |
or... |
8 |
|
9 |
[ "$ARCH" == "mips-o32" ] && ARCH_LIBDIR="lib" |
10 |
[ "$ARCH" == "mips-n32" ] && ARCH_LIBDIR="lib32" |
11 |
[ "$ARCH" == "mips-n64" ] && ARCH_LIBDIR="lib64" |
12 |
|
13 |
(only done in a way that makes more sense for a profile) |
14 |
|
15 |
and then also have the following addition to econf: |
16 |
|
17 |
[ "${ARCH_LIBDIR}" != "" ] && EXTRA_ECONF="--libdir=/usr/${ARCH_LIBDIR} |
18 |
${EXTRA_ECONF}" |
19 |
|
20 |
that way, user and ebuild specified configuration will overwrite the |
21 |
default --libdir if specified, and the default behavior of not |
22 |
specifying --libdir isnt changed what this var isnt set. i would really |
23 |
appreciate if this edit found it's way into portage before 2.0.51, as it |
24 |
wont effect anything now and will help me to work on getting ebuilds |
25 |
lib64 aware locally (even without the multilib dependency changes). |
26 |
|
27 |
also, with an ARCH_LIBDIR setting, we can fix any ebuild that doesnt use |
28 |
/usr/lib (like kde) by specifying --libdir=/usr/kde/3.3/${ARCH_LIBDIR} |
29 |
if ARCH_LIBDIR is set (and only if it's set)... all without changing the |
30 |
default behavior when it isnt. |
31 |
|
32 |
my previous econf edit idea didnt allow for as much flexibility, and |
33 |
with this setup we get support for any arch that needs a specific libdir |
34 |
for free... like with mips needing lib, lib32, and lib64 depending on |
35 |
ABI. so the work i do getting amd64 multilib ready will also help mips |
36 |
get there too. it's a win/win/win/win situation :) |
37 |
|
38 |
|
39 |
Travis Tilley <lv@g.o> |
40 |
|
41 |
-- |
42 |
gentoo-dev@g.o mailing list |