From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Cc: vapier@gentoo.org, Alexis Ballier <aballier@gentoo.org>,
mips@gentoo.org, multilib@gentoo.org
Subject: Re: [gentoo-mips] On MIPS using the same CHOST for all multilib ABIs
Date: Mon, 30 Dec 2013 10:44:25 +0100 [thread overview]
Message-ID: <20131230104425.69a086bf@gentoo.org> (raw)
In-Reply-To: <201312291321.22221.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]
Dnia 2013-12-29, o godz. 13:21:21
Mike Frysinger <vapier@gentoo.org> napisał(a):
> we've run into issues in the past where people install a toolchain via
> crossdev that uses the same tuple as the non-default ABI one (e.g. people on
> an amd64 system do `crossdev i686-pc-linux-gnu`) and then the multilib code
> gets confused. but it's been much more of a hassle to try and get configure
> scripts to use compile tests rather than probe the CHOST, so we've just lived
> with this lesser evil.
Out of curiosity, does a dedicated i686 toolchain on a multilib amd64
host have any benefits over the toolchain's -m32 options? Well, except
for not needing the explicit options.
> > > > (1) here is not really a killer feature but I'd rather avoid
> > > > changing this at this point. (2) is actually a killer feature,
> > > > since the eclass sets CHOST properly and thanks to that
> > > > AC_CHECK_TOOL and friends can find multilib *-config progs and
> > > > stuff without any special hackery.
> > >
> > > *-config progs are dead. use pkg-config.
> >
> > ok; but shouldnt we kill that tc-getPKG_CONFIG() which returns
> > $CHOST-pkg-config then ?
>
> i didn't mean specifically use `pkg-config`. packages should be using .pc files
> instead of *-config scripts.
'Should' is far away from reality. I'd rather avoid Gentoo inventing
pkg-config files for random packages where upstream simply refuses to
do that.
Then, there's LLVM. Their llvm-config has some more options than
pkg-config does, and it supports selecting single components. If we're
to do something semi-equal to that, we'd end up with 116 pkg-config
files, plus around 23 for clang. And each new supported target
increases that number by 5-7 files.
Of course, we could put them all in a single file.. but then we're
replacing one crap with another. And forcing the --as-needed hack
on top of it.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2013-12-30 9:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 22:58 [gentoo-mips] On MIPS using the same CHOST for all multilib ABIs Michał Górny
2013-12-28 23:55 ` Markos Chandras
2013-12-29 2:12 ` Mike Frysinger
[not found] ` <20131229163354.35b65df5@gentoo.org>
2013-12-29 18:21 ` Mike Frysinger
2013-12-30 9:44 ` Michał Górny [this message]
2013-12-29 21:40 ` [gentoo-mips] " Joshua Kinard
2013-12-29 21:48 ` Markos Chandras
2013-12-29 21:48 ` Michał Górny
2013-12-29 21:48 ` Markos Chandras
2013-12-29 21:52 ` Anthony G. Basile
2013-12-29 22:04 ` Michał Górny
2013-12-29 23:56 ` Mike Frysinger
2013-12-30 7:51 ` Mike Frysinger
2013-12-30 8:17 ` sébastien bertoletto
2013-12-29 22:13 ` Markos Chandras
2013-12-29 22:19 ` Anthony G. Basile
2013-12-29 22:33 ` Markos Chandras
2013-12-29 23:47 ` Anthony G. Basile
2014-01-16 20:01 ` [gentoo-mips] " Michał Górny
2014-01-16 21:05 ` Anthony G. Basile
2014-01-16 21:24 ` Michał Górny
2014-01-16 22:29 ` Anthony G. Basile
2014-01-17 4:47 ` Michał Górny
2014-01-17 18:20 ` Markos Chandras
2014-01-17 18:36 ` Matt Turner
2014-01-17 19:38 ` Markos Chandras
2014-01-17 21:57 ` Matt Turner
2014-01-17 18:51 ` Michał Górny
2014-01-17 19:44 ` Markos Chandras
2014-01-21 20:52 ` Markos Chandras
2014-01-22 14:24 ` Anthony G. Basile
2014-01-22 14:38 ` Michał Górny
2014-01-22 20:39 ` Markos Chandras
2014-01-22 21:07 ` Anthony G. Basile
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131230104425.69a086bf@gentoo.org \
--to=mgorny@gentoo.org \
--cc=aballier@gentoo.org \
--cc=gentoo-mips@lists.gentoo.org \
--cc=mips@gentoo.org \
--cc=multilib@gentoo.org \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox