Message-ID: <cbef1b686a0a2c38ecb7c0e61eba6d22406f3cbc.camel@cogitri.dev>
Subject: Re: Planning for 3.12 feature freeze
From: Rasmus Thomsen <oss@cogitri.dev>
To: ~alpine/devel@lists.alpinelinux.org
Date: Mon, 30 Mar 2020 12:51:20 +0200
In-Reply-To: <20200330124614.2afc0075@ncopa-desktop.copa.dup.pw>
References: <20200330121403.71f8e7f9@ncopa-desktop.copa.dup.pw>
	 <72a881ad47bc7e8d79e8c7d94a9d23319fd5288f.camel@cogitri.dev>
	 <20200330124614.2afc0075@ncopa-desktop.copa.dup.pw>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Mon, 2020-03-30 at 12:46 +0200, Natanael Copa wrote:
> On Mon, 30 Mar 2020 12:35:58 +0200
> Rasmus Thomsen <oss@cogitri.dev> wrote:
> 
> > As for fixing the rust triplets: I started to doubt if that's
> > actually
> > useful. I mean it _is_ nice to have a custom triplet with our name
> > on
> > it for the options we set, but right now there are some really
> > weird
> > issues during compilation with custom triplets that I can't seem to
> > get
> > behind and we currently have to work around some rust crates not
> > working with custom triplets and needing patches (see e.g. FF).
> I believe those problems comes from inconsistent triples, at least in
> the firefox case? I think the firefox patch is an ugly hack for a
> different underlying problem.
> 
> -nc

No, in the Firefox case it happens because FF has a hardcoded list of
triplets and we're not on that list. There have been some improvements
in a third-party crate that FF uses for triplet detection (so
compilation itself works if FF were to use the latest version...), but
FF's python configure thingie still needs patches either way.

Regards,

Rasmus