Announcing LLVM Snapshot Packages for Fedora Linux

[Konrad Kleine]

Dear Fedora packagers, developers and users,

we have some good news for you:

We are beginning to build nightly snapshot packages of LLVM for the latest
versions of Fedora Linux (currently 34, 35 and rawhide) for a growing list
of
architectures.

You can grab them here:

https://copr.fedorainfracloud.org/coprs/g/fedora-llvm-team/llvm-snapshots/

Feel free to enable the copr repository with

$ dnf copr enable @fedora-llvm-team/llvm-snapshots

and then install the i.e. latest clang with

$ dnf install clang

Beware, that a snapshot release of LLVM is probably more unstable than a
regular release! If you run into a problem, I would kindly ask you to wait
and try it again with the next snapshot.

We hope you enjoy this peek into the next version of LLVM that you can now
try without too much hassle and without compiling it every day on your own.

Regards,

Konrad Kleine

Senior Software Engineer, Platform Tools

Red Hat https://www.redhat.com

[e-mail]
M: +49(0)151/21000244

D87A 77F4 2A58 C72D 12A7 203B C0A0 2C32 BCB7 3099
https://www.redhat.com

[Jonathan Wakely]

On Fri, 8 Oct 2021 at 11:15, Konrad Kleine  wrote:
> Dear Fedora packagers, developers and users,
>
> we have some good news for you:
>
> We are beginning to build nightly snapshot packages of LLVM for the latest
> versions of Fedora Linux (currently 34, 35 and rawhide) for a growing list
> of
> architectures.
>
> You can grab them here:
>
> https://copr.fedorainfracloud.org/coprs/g/fedora-llvm-team/llvm-snapshots/

Nice to see this going public, I will definitely be using it, thanks!

And I'll shamelessly plug my copr with weekly GCC snapshots  ;-)
https://copr.fedorainfracloud.org/coprs/jwakely/gcc-latest/

[Neal Gompa]

On Wed, Nov 3, 2021 at 9:47 AM Jonathan Wakely  wrote:
> On Fri, 8 Oct 2021 at 11:15, Konrad Kleine  wrote:
> > Dear Fedora packagers, developers and users,
> >
> > we have some good news for you:
> >
> > We are beginning to build nightly snapshot packages of LLVM for the latest
> > versions of Fedora Linux (currently 34, 35 and rawhide) for a growing list of
> > architectures.
> >
> > You can grab them here:
> >
> > https://copr.fedorainfracloud.org/coprs/g/fedora-llvm-team/llvm-snapshots/
>
> Nice to see this going public, I will definitely be using it, thanks!
>
> And I'll shamelessly plug my copr with weekly GCC snapshots  ;-)
> https://copr.fedorainfracloud.org/coprs/jwakely/gcc-latest/

Maybe this is worth a commblog or magazine post?

[Konrad Kleine]

On Wed, 3 Nov 2021 at 14:50, Neal Gompa  wrote:
> On Wed, Nov 3, 2021 at 9:47 AM Jonathan Wakely  wrote:
> > On Fri, 8 Oct 2021 at 11:15, Konrad Kleine  wrote:
> > > Dear Fedora packagers, developers and users,
> > >
> > > we have some good news for you:
> > >
> > > We are beginning to build nightly snapshot packages of LLVM for the
>
> latest
> > > versions of Fedora Linux (currently 34, 35 and rawhide) for a growing
>
> list of
> > > architectures.
> > >
> > > You can grab them here:
>
> https://copr.fedorainfracloud.org/coprs/g/fedora-llvm-team/llvm-snapshots/
> > >
> >
> > Nice to see this going public, I will definitely be using it, thanks!
> >
> > And I'll shamelessly plug my copr with weekly GCC snapshots  ;-)
> > https://copr.fedorainfracloud.org/coprs/jwakely/gcc-latest/
>
> Maybe this is worth a commblog or magazine post?

There's going to be a blog entry about this. I cannot tell when it will be
public though.
I've submitted a lightning talk for this year's LLVM virtual event and it
will be aired tomorrow: https://llvm.swoogo.com/2021devmtg/agenda.
I hope that adding the link to the copr page on the llvm front-page will
also increase the visibility: https://github.com/llvm/llvm-www/pull/9.
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

[Reon Beon]

Cool, how about a llvm-git package when it gets more testing?

[Konrad Kleine]

Hi Reon,

On Thu, 18 Nov 2021 at 03:38, Reon Beon via devel <
[e-mail]> wrote:
> Cool, how about a llvm-git package when it gets more testing?

And what would that include?

Cheers,
Konrad

[Reon Beon]

Mesa would be nice.

[Dominique Martinet]

Hi Jonathan,

Jonathan Wakely wrote on Wed, Nov 03, 2021 at 01:47:22PM +0000:
> And I'll shamelessly plug my copr with weekly GCC snapshots  ;-)
> https://copr.fedorainfracloud.org/coprs/jwakely/gcc-latest/

I cannot seem to be able to install gcc-latest, do you know what
provides libasan/libtsan in the versions it expects?

Problem: cannot install the best candidate for the job
  - nothing provides libasan.so.8()(64bit) needed by gcc-latest-12.0.0-1.20211114git3057f1ab7375.fc34.x86_64
  - nothing provides libtsan.so.2()(64bit) needed by gcc-latest-12.0.0-1.20211114git3057f1ab7375.fc34.x86_64

Respective versions on the fedora 34 package are libasan.so.6 and
libtsan.so.0
(I'll probably upgrade to fedora 35 over the next few weeks, but
fedora35 rpms for the two seem to provide the same versions so I'm
probably missing something)

Hi Konrad,

Konrad Kleine wrote on Fri, Oct 08, 2021 at 12:13:35PM +0200:
> You can grab them here:
>
> https://copr.fedorainfracloud.org/coprs/g/fedora-llvm-team/llvm-snapshots/

Thanks! I was able to install these.
I see the system's llvm (12) got installed as the copr's llvm12 instead,
and llvm became the snapshot -- would it make sense to keep llvm as the
system's llvm (12), and install the lvm snapshot as llvm14 instead?

That would let people keep using the system's trusted llvm by default,
and only use the snapshot when they explicitely require it.

Cheers,

[Konrad Kleine]

Hi Dominique,

Thanks! I was able to install these.
> I see the system's llvm (12) got installed as the copr's llvm12 instead,
> and llvm became the snapshot -- would it make sense to keep llvm as the
> system's llvm (12), and install the lvm snapshot as llvm14 instead?

I understand why you would want that. But let me explain why we decided to
do it differently. I encourage you to check the contents of clang12 for
example. You will not find a binary executable file like "clang" inside
there. That is because it is a "compatibility package" and it only serves
the purpose to keep software running that dynamically links against a *.so
file from the version that ships with Fedora in that version you're
running. Once you decide to install a new version of clang, or llvm for
that matter, the assumption is that you want to use that without any hassle
by typing "clang" and not "clangXX", where XX is the version. This way your
migration effort to get to a new version in your compile pipeline stays
close to zero while existing software still continues to run.
> That would let people keep using the system's trusted llvm by default,
> and only use the snapshot when they explicitely require it.

I get that. In theory every Fedora version provides its own compat package
for llvm and clang. But sometimes they are too outdated for snapshots or
simply don't exist yet. That's why I began including them in my repo for
snapshots. you should see clang10-* packages for example coming from
fedora's official repos and there's not a single binary inside them.

dnf -q repoquery -l clang10-* | grep /bin

Replace the 10 with anything available on your system.

If you by "trusted" mean that it comes from Fedora directly, then yes, you
should be able to just install what's available in Fedora. But please note
that any llvm*.so file from the Fedora compat package is also something
that was built separately from the original llvm package. It's done
internally with a build condition.

Regards
Konrad
> Cheers,
>
> Dominique Martinet
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

[Jonathan Wakely]

On Thu, 18 Nov 2021 at 10:36, Dominique Martinet  wrote:
> Hi Jonathan,
>
> Jonathan Wakely wrote on Wed, Nov 03, 2021 at 01:47:22PM +0000:
> > And I'll shamelessly plug my copr with weekly GCC snapshots  ;-)
> > https://copr.fedorainfracloud.org/coprs/jwakely/gcc-latest/
>
> I cannot seem to be able to install gcc-latest, do you know what
> provides libasan/libtsan in the versions it expects?

They should be in the gcc-latest package itself. You can watch
https://github.com/jwakely/pkg-gcc-latest/issues/5 for updates, but I
haven't had time to look into it yet, sorry.

[José Abílio Matos]

On Wednesday, 3 November 2021 13.47.22 WET Jonathan Wakely wrote:
> Nice to see this going public, I will definitely be using it, thanks!
>
> And I'll shamelessly plug my copr with weekly GCC snapshots  ;-)
> https://copr.fedorainfracloud.org/coprs/jwakely/gcc-latest/

Thank you for providing it. :-)

I have one question, how should we use it?
Case in point, I am using it to compile LyX in order to fix the issues raised 
in rawhide.

In order to do that I configure LyX (using autotools) with:

path/to/lyx/configure --with-version-suffix=-devel CC=/opt/gcc-latest/bin/gcc 
CXX=/opt/gcc-latest/bin/g++

in order to use the latest gcc.

Compiling I got an issue with a missing import. After fixing this it compiled.
The problem is running the resulting binary:

$ src/lyx
[1] 61542
src/lyx: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required 
by src/lyx)

Any help here?

Regards,

[José Abílio Matos]

On Thursday, 27 January 2022 16.14.36 WET José Abílio Matos wrote:
> $ src/lyx
>
> [1] 61542
>
> src/lyx: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required
> by src/lyx)
>
> Any help here?

OK, one option is set the linker path
$ LD_LIBRARY_PATH=/opt/gcc-latest/lib64/ src/lyx

[Jonathan Wakely]

On Thu, 27 Jan 2022 at 16:29, José Abílio Matos  wrote:
> On Thursday, 27 January 2022 16.14.36 WET José Abílio Matos wrote:
> > $ src/lyx
> >
> > [1] 61542
> >
> > src/lyx: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required
> > by src/lyx)
> >
> >
> > Any help here?
>
> OK, one option is set the linker path
>
> $ LD_LIBRARY_PATH=/opt/gcc-latest/lib64/ src/lyx

See the docs: https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dynamic_or_shared.html...

[Jonathan Wakely]

On Tue, 1 Feb 2022 at 11:25, Jonathan Wakely  wrote:
> On Thu, 27 Jan 2022 at 16:29, José Abílio Matos  wrote:
> > On Thursday, 27 January 2022 16.14.36 WET José Abílio Matos wrote:
> > > $ src/lyx
> > >
> > > [1] 61542
> > >
> > > src/lyx: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required
> > > by src/lyx)
> > >
> > >
> > > Any help here?
> >
> > OK, one option is set the linker path
> >
> > $ LD_LIBRARY_PATH=/opt/gcc-latest/lib64/ src/lyx
>
> See the docs: https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dynamic_or_shared.html...

Which is also mentioned at https://jwakely.github.io/pkg-gcc-latest/
so I've added a link to that page from the copr description.

[José Abílio Matos]

On Tuesday, 1 February 2022 11.54.01 WET Jonathan Wakely wrote:
> Which is also mentioned at https://jwakely.github.io/pkg-gcc-latest/
> so I've added a link to that page from the copr description.

Thank you.
That answered all my questions (regarding this issue :-) ).

Regards,

[Davide Cavalca]

On Fri, 2021-10-08 at 12:13 +0200, Konrad Kleine wrote:
> Dear Fedora packagers, developers and users,
>
> we have some good news for you:
>
> We are beginning to build nightly snapshot packages of LLVM for the
> latest
> versions of Fedora Linux (currently 34, 35 and rawhide) for a growing
> list of
> architectures.
>
> You can grab them here:
>
> https://copr.fedorainfracloud.org/coprs/g/fedora-llvm-team/llvm-snapshots/

This is excellent, thanks for putting it together! Would you be open to
adding builds for EPEL and CentOS Stream? I saw some preliminary work
in that direction in
https://github.com/kwk/llvm-daily-fedora-rpms/commit/cc9d02dc300aeed583ccda9...
but it was later reverted. I'd be happy to help with testing that if
needed (also adding the EPEL list in case other folks are interested).

Cheers
Davide

[Konrad Kleine]

Davide,

thank you for your interest in this. May I ask what plans you have using it
for? We're investigating an integration into CentOS Stream.

Regards
Konrad

On Thu, 27 Jan 2022 at 17:55, Davide Cavalca via devel <
[e-mail]> wrote:
> On Fri, 2021-10-08 at 12:13 +0200, Konrad Kleine wrote:
> > Dear Fedora packagers, developers and users,
> >
> > we have some good news for you:
> >
> > We are beginning to build nightly snapshot packages of LLVM for the
> > latest
> > versions of Fedora Linux (currently 34, 35 and rawhide) for a growing
> > list of
> > architectures.
> >
> > You can grab them here:
>
> https://copr.fedorainfracloud.org/coprs/g/fedora-llvm-team/llvm-snapshots/
>
> This is excellent, thanks for putting it together! Would you be open to
> adding builds for EPEL and CentOS Stream? I saw some preliminary work
> in that direction in
>
> https://github.com/kwk/llvm-daily-fedora-rpms/commit/cc9d02dc300aeed583ccda9...
> but it was later reverted. I'd be happy to help with testing that if
> needed (also adding the EPEL list in case other folks are interested).
>
> Cheers
> Davide
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

[Davide Cavalca]

On Tue, 2022-02-01 at 13:59 +0100, Konrad Kleine wrote:
> Davide,
>
> thank you for your interest in this. May I ask what plans you have
> using it for? We're investigating an integration into CentOS Stream.

Hi Konrad,

the immediate usecase for us is making it easier to do development on
BPF upstream and run the test suite. CentOS Stream would actually work
well in this case, as that's what we actually run, though I don't think
the delta between targeting CentOS Stream and EPEL would be that
significant.

Cheers
Davide