1 |
On Thu, 2004-04-08, 17:30:45 +0200, in |
2 |
<1081438245.407570253d839@××××××××××××.be>, Jochen Maes |
3 |
<sejo@g.o> wrote: |
4 |
> Quoting Drake Wyrm <wyrm@×××××.com>: |
5 |
> |
6 |
> > On Wed, 2004-04-07, 14:29:47 -0400, in |
7 |
> > <200404071429.47124.vapier@g.o>, Mike Frysinger |
8 |
> > <vapier@g.o> wrote: |
9 |
> > > On Wednesday 07 April 2004 02:51 pm, Meir Kriheli wrote: |
10 |
> > > > Question is: Can there be more than one arch in ACCEPT_KEYWORDS |
11 |
> > > > in a single system (like: "~amd64 ~x86") ? Is such state legal |
12 |
> > > > at all ? |
13 |
> > > |
14 |
> > > should it be done ? no ... does it work ? yes ... users do it ... |
15 |
> > > should it be supported ? no ... |
16 |
> > |
17 |
> > I disagree. Hypothetical situation: one box serving /usr to several |
18 |
> > hosts of different ARCHes. Maybe we should look improving support |
19 |
> > for such a situation. |
20 |
> |
21 |
> Serving /usr for serveral hosts of different ARCHes, like in the |
22 |
> example, this would imply that fe. X would be compiled for x86, but |
23 |
> the amd64 ARCH using the /usr won't be able to use that X version (in |
24 |
> 64 bit) imho. |
25 |
|
26 |
I could be wrong, but I see little difficulty in cross-compiling for |
27 |
amd64 from an x86 server. Any amd64 or gcc gurus available to clear this |
28 |
up? How wild and crazy different can you be with '-mcpu=foo' flags? |
29 |
|
30 |
Irregardless, the only section under /usr required to be |
31 |
arch-independent is /usr/share. FHS doesn't specify this usage (probably |
32 |
doesn't allow it, either), but perhaps we could constrain the |
33 |
arch-specific stuff to /usr/CPU-VEND-KERNEL-OS/{bin,lib,sbin,whatever}. |
34 |
Anybody know of a good precedent regarding how to make this work? |
35 |
|
36 |
-- |
37 |
Batou: Hey, Major... You ever hear of "human rights"? |
38 |
Kusanagi: I understand the concept, but I've never seen it in action. |
39 |
--Ghost in the Shell |