Gentoo Archives: gentoo-mips

From: "Michał Górny" <mgorny@g.o>
To: gentoo-mips@l.g.o
Cc: hwoarang@g.o
Subject: Re: [gentoo-mips] On MIPS using the same CHOST for all multilib ABIs
Date: Fri, 17 Jan 2014 18:52:04
Message-Id: 20140117195154.4b512793@pomiot.lan
In Reply to: Re: [gentoo-mips] On MIPS using the same CHOST for all multilib ABIs by Markos Chandras
1 Dnia 2014-01-17, o godz. 18:20:30
2 Markos Chandras <hwoarang@g.o> napisał(a):
3
4 > On 01/17/2014 04:47 AM, Michał Górny wrote:
5 > > Dnia 2014-01-16, o godz. 17:29:43 "Anthony G. Basile"
6 > > <blueness@g.o> napisał(a):
7 > >
8 > >> On 01/16/2014 04:24 PM, Michał Górny wrote:
9 > >>> Because AC_PATH_TOOL uses CHOST and some random Gentoo
10 > >>> invention.
11 > >>
12 > >> I got that AC_PATH_TOOL and AC_CHECK_TOOL prefix whatever utility
13 > >> they search for with the canonicalized chost (usually from
14 > >> config.guess), but I still don't see why we need this to avoid
15 > >> hackery? Can you give me a practial example because right now I
16 > >> just don't see a serious problem.
17 > >
18 > > libgpg-error installs ${CHOST}-gpg-error-config.
19 > >
20 > > Now libgcrypt (and possibly other tools) are using AC_PATH_TOOL to
21 > > find it. If we have proper CHOSTs, they find the right
22 > > gpg-error-config and we don't have to put any more effort into
23 > > that. Then libgcrypt installs ${CHOST}-libgcrypt-config.
24 > >
25 > > Now other tools are using AC_PATH_TOOL to find proper
26 > > libgcrypt-config. If we have proper CHOSTs, it just works and we
27 > > don't have to put any more effort into that.
28 > >
29 > > Same goes for LLVM & Mesa.
30 > >
31 > > If we play by the rules nicely, all pieces fit together nicely and
32 > > we don't have to worry. If we don't, we ask the developers to spit
33 > > Gentoo- specific hackery all over the place.
34 > >
35 > You need to consider that besides changing CHOST to new stages (which
36 > is a lengthy and tiring process), you somehow need to migrate existing
37 > users to the new CHOST (no?) otherwise the multilib eclass (or any
38 > other eclass/package) that depends on CHOST will be broken as soon as
39 > they update their tree and try to install package updates.
40 > This is definitely not a pleasant user experience.
41
42 Well, I'd like someone who knows better than I do to explain how much
43 does changing non-native CHOST affect. I will try to test it a bit by
44 changing CHOST_x86=i686-pc-linux-gnu to i386-* locally but an expert
45 opinion would be preferred.
46
47 --
48 Best regards,
49 Michał Górny

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-mips] On MIPS using the same CHOST for all multilib ABIs Markos Chandras <hwoarang@g.o>