On Wed, 8 Jan 2020 at 15:53, Dmitry Butskoy <[email protected]> wrote:
>
> Considering how Firefox is built, I see it uses:
> devtoolset-8
> rust-toolset-1.35
> llvm-toolset-7.0
>
> I try to build new SeaMonkey-2.53 (formerly Mozilla, Netscape), it has
> code based on Firefox and requires the same toolsets under EPEL7.
>
> Unfortunately, it seems EPEL7 build has no "rust-toolset-1.35" and
> "llvm-toolset-7.0".
>
> Even worse is that "rust-toolset-1.35" is not provided by whell-known
> CentOS repo, and seems to be available to RHEL subscribers only...
>
> Are there any chances in the near future that:
> 1) More (or all) toolsets will be allowed for EPEL builds;
> 2) EPEL builds will use "official" packages from the correspond RHEL
> channel?
>

So we have access to the /rhel-7-rhscl-for-x86_64-server-rpms channel
which does have devtoolset-8 in it. It does not seem to have the
rust-toolset or llvm-toolset and I don't see any channel we have
access to which does. As such we are stuck at the moment :(.


>
> Regards,
> Dmitry Butskoy
> https://fedoraproject.org/wiki/User:Buc
>
> P.S. I know EPEL7 provides rust-1.40, but the code I try to compile is
> ready for rust <= 1.37 only :/
> P.P.S. I know about "bundling and pre-compile", but certainly hope to
> avoid it.
> _______________________________________________
> epel-devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[email protected]



-- 
Stephen J Smoogen.
_______________________________________________
epel-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to