libtiff-4.6.0-2.fc40 continues to ship old .so.5* libraries

Andrea (in CC) recently pointed me to libtiff installation warnings on Fedora/RISCV side: [..] Installing : libtiff-4.6.0-2.fc40.riscv64 5/5 Running scriptlet: libtiff-4.6.0-2.fc40.riscv64 5/5 /usr/sbin/ldconfig:

Re: Fedora RISC-V port needs to put shared objects into /usr/lib64/lp64d

On Mon, Apr 29, 2024 at 3:31 PM Stephen Smoogen wrote: > > I guess we need to see what RPM owns that symlink and get it into the build > root > > Stephen Smoogen, Red Hat Automotive > Let us be kind to one another, for most of us are fighting a hard battle. -- > Ian MacClaren > > > On Mon, Apr

Re: Fedora RISC-V port needs to put shared objects into /usr/lib64/lp64d

On Wed, Apr 24, 2024 at 2:16 PM Florian Weimer wrote: > > * Andrea Bolognani: > > > Wouldn't changing -mabi effectively make the result a new Fedora > > architecture? IIUC, binaries built with -mabi=lp64d wouldn't be able > > to load libraries built with -mabi=lp64dv and vice versa. > > > > If

Re: Fedora RISC-V port needs to put shared objects into /usr/lib64/lp64d

On Mon, Apr 22, 2024 at 1:12 PM Florian Weimer wrote: > > * David Abdurachmanov: > > > We most likely will not have ABIs installed in parallel, but we might > > change ABI. Currently Linux distributions target "RV64GC", but we > > don't really want that for th

Re: Fedora RISC-V port needs to put shared objects into /usr/lib64/lp64d

On Mon, Apr 22, 2024 at 1:08 PM Florian Weimer wrote: > > * Daniel P. Berrangé: > > > On Fri, Apr 19, 2024 at 02:21:57PM +0200, Florian Weimer wrote: > >> There are multiple PRs and patches floating around that make RISC-V use > >> the /usr/lib64 directory, like other 64-bit ports. However,

Re: Fedora RISC-V port needs to put shared objects into /usr/lib64/lp64d

On Sun, Apr 21, 2024 at 2:19 AM Kevin Kofler via devel wrote: > > David Abdurachmanov wrote: > > We currently use a symlink (as Richard) mentioned, but it's not ideal > > and causes problems (e.g. meson generates wrong paths breaking some > > packages [one example: libplac

Re: Fedora RISC-V port needs to put shared objects into /usr/lib64/lp64d

On Fri, Apr 19, 2024 at 8:36 PM Andrea Bolognani wrote: > > On Fri, Apr 19, 2024 at 02:21:57PM +0200, Florian Weimer wrote: > > There are multiple PRs and patches floating around that make RISC-V use > > the /usr/lib64 directory, like other 64-bit ports. However, RISC-V > > recommends to use

Re: Modern C failures in Haskell stack

On Fri, Feb 16, 2024 at 9:38 AM Jens-Ulrik Petersen wrote: > > Thanks Richard for the PR and Florian for the patch > > On Thu, Feb 15, 2024 at 11:28 PM Richard W.M. Jones wrote: >> >> On Thu, Feb 15, 2024 at 12:57:21PM +0100, Florian Weimer wrote: >> > For the first issue, please try this GHC

Re: Question about conditional BuildRequires lines

On Wed, Feb 14, 2024 at 5:55 PM Tom Hughes via devel wrote: > > On 14/02/2024 15:48, Richard W.M. Jones wrote: > > On Wed, Feb 14, 2024 at 03:21:38PM +, Tom Hughes wrote: > >> On 14/02/2024 14:54, Richard W.M. Jones wrote: > >> > >>> https://src.fedoraproject.org/rpms/rapidjson/pull-request/7

Re: A note about riscv64 changes

> > https://src.fedoraproject.org/rpms/gdal/pull-request/21 > > > > > > > > For many years we have been building Fedora for the RISC-V > > > > architecture on a separate build system at > > > > http://fedora.riscv.rocks/koji/ , and maintaining do

Re: "noarch sysroot subpackages" commit breaks glibc compile on riscv64

On Thu, Feb 1, 2024 at 3:24 PM Florian Weimer wrote: > Please try this: > > diff --git a/glibc.spec b/glibc.spec > index 6116752..e4d5e44 100644 > --- a/glibc.spec > +++ b/glibc.spec > @@ -1571,6 +1571,10 @@ for lib in lib lib64; do > set +x > slbase=$(basename

Re: "noarch sysroot subpackages" commit breaks glibc compile on riscv64

On Thu, Feb 1, 2024 at 4:10 PM David Abdurachmanov wrote: > > On Thu, Feb 1, 2024 at 3:44 PM Richard W.M. Jones wrote: > > > > On Thu, Feb 01, 2024 at 02:24:10PM +0100, Florian Weimer wrote: > > > * David Abdurachmanov: > > > > > > > Hi Florian,

Re: "noarch sysroot subpackages" commit breaks glibc compile on riscv64

On Thu, Feb 1, 2024 at 3:44 PM Richard W.M. Jones wrote: > > On Thu, Feb 01, 2024 at 02:24:10PM +0100, Florian Weimer wrote: > > * David Abdurachmanov: > > > > > Hi Florian, > > > > > > I was trying to build the latest glibc [0] in Fedora

Re: RISC-V ABI issue with ULEB128

On Thu, Jan 4, 2024 at 4:07 PM Nick Clifton wrote: > > Hi David, > > > binutils-2.31-18.fc40 didn't land in f40 as Bodhi CI gating marked it > > as failed. The failures don't seem to be related to binutils package > > itself. Seems like CI test is/was broken, or maybe a temporary network > >

Re: RISC-V ABI issue with ULEB128

On Thu, Jan 4, 2024 at 11:20 AM Nick Clifton wrote: > > Hi David, Hi Florian, > > Here's the bug: > > https://sourceware.org/bugzilla/show_bug.cgi?id=31179 > RISC-V: The SET/ADD/SUB fix breaks ABI compatibility with 2.41 objects > > It refers to this change in

Re: RISC-V ABI issue with ULEB128

On Tue, Jan 2, 2024 at 7:20 PM Peter Robinson wrote: > > On Tue, Jan 2, 2024 at 5:15 PM David Abdurachmanov > wrote: > > > > On Tue, Jan 2, 2024 at 6:26 PM Peter Robinson wrote: > > > > > > On Tue, Jan 2, 2024 at 2:05 PM David Abdurachmanov > > >

Re: RISC-V ABI issue with ULEB128

On Tue, Jan 2, 2024 at 6:26 PM Peter Robinson wrote: > > On Tue, Jan 2, 2024 at 2:05 PM David Abdurachmanov > wrote: > > > > On Tue, Jan 2, 2024 at 3:54 PM Florian Weimer wrote: > > > > > > * David Abdurachmanov: > > > > > > > On Tu

Re: RISC-V ABI issue with ULEB128

On Tue, Jan 2, 2024 at 3:54 PM Florian Weimer wrote: > > * David Abdurachmanov: > > > On Tue, Jan 2, 2024 at 1:09 PM Richard W.M. Jones wrote: > >> > >> > >> I'm not sure exactly the effect on RISC-V binaries, but I wanted to > >> raise it her

Re: F40 Change Proposal: Optimized Binaries for the AMD64 Architecture (System-Wide)

On Tue, Jan 2, 2024 at 1:20 PM Vít Ondruch wrote: > > > Dne 28. 12. 23 v 17:12 Aoife Moloney napsal(a): > > The dynamic linker already has the `glibc-hwcaps` mechanism to load > optimized implementations of ''shared objects'' [3]. This means that > packages can provide optimized libraries and

Re: RISC-V ABI issue with ULEB128

On Tue, Jan 2, 2024 at 1:09 PM Richard W.M. Jones wrote: > > > I'm not sure exactly the effect on RISC-V binaries, but I wanted to > raise it here to get the attention of the Fedora toolchain team ... > > Here's the bug: > > https://sourceware.org/bugzilla/show_bug.cgi?id=31179 > RISC-V: The

Re: -fstack-clash-protection needs to be disabled on riscv64 (#2242327)

On Fri, Oct 6, 2023 at 12:58 PM Florian Weimer wrote: > > I had to revert part of this commit: > > commit 0676a754f0508957f289eac5eda01091778cebc2 > Author: David Abdurachmanov > Date: Wed Jul 10 16:21:32 2019 +0300 > > rpmrc: update optflags for riscv64 > >

Re: Is there a chance to phase out `/lib64` directory?

On Wed, Jun 28, 2023 at 3:22 AM Kevin Kofler via devel wrote: > > Kalev Lember wrote: > > I would like to have a layout similar to what Debian is doing, so that > > shared libraries would go in /usr/lib/x86_64-redhat-linux/ and /usr/lib64 > > would be a legacy symlink pointing to it. > > That

Re: subarchitectures and RISC-V, was Re: F39 proposal: RPM 4.19 (System-Wide Change proposal)

On Sat, Apr 15, 2023 at 7:08 AM Jeff Law wrote: > > > > On 4/14/23 20:14, Neal Gompa wrote: > > >> > > > > We should not screw up with RISC-V in Fedora like RHEL did with ARM. > > Yes, I'm saying RHEL's ARM strategy was a mistake, and still is, to > > some degree. We see aspects of this being

Re: subarchitectures and RISC-V, was Re: F39 proposal: RPM 4.19 (System-Wide Change proposal)

On Sat, Apr 15, 2023 at 5:30 AM Neal Gompa wrote: > > On Fri, Apr 14, 2023 at 10:01 PM Jeff Law wrote: > > > > > > > > On 4/12/23 10:08, przemek klosowski via devel wrote: > > >> > > >> That may rule out certain processors, but it ultimately provides a > > >> higher performing baseline

Re: subarchitectures and RISC-V, was Re: F39 proposal: RPM 4.19 (System-Wide Change proposal)

On Sat, Apr 15, 2023 at 5:01 AM Jeff Law wrote: > > > > On 4/12/23 10:08, przemek klosowski via devel wrote: > >> > >> That may rule out certain processors, but it ultimately provides a > >> higher performing baseline architecture for systems that are > >> (hopefully) going to be good performing

Re: subarchitectures and RISC-V, was Re: F39 proposal: RPM 4.19 (System-Wide Change proposal)

On Sat, Apr 15, 2023 at 4:49 AM Jeff Law wrote: > > > > On 4/12/23 10:57, David Abdurachmanov wrote: > > > > > We have been focusing and building for RV64GC, which is kinda > > represented by the RVA20 profile. RVA20 is considered a major profile, > >

Re: subarchitectures and RISC-V, was Re: F39 proposal: RPM 4.19 (System-Wide Change proposal)

On Wed, Apr 12, 2023 at 7:08 PM przemek klosowski via devel wrote: > > > On 4/11/23 22:08, Jeff Law wrote: > > On 4/11/23 19:14, przemek klosowski via devel wrote: > >> The situation in the RISC-V universe is even more complicated because > >> of all the extensions > >> > >> ... > >> Whatever

Re: Risc-V SIG?

On Thu, Feb 9, 2023 at 2:24 PM Richard W.M. Jones wrote: > > On Thu, Feb 09, 2023 at 08:06:33AM -0500, Neal Gompa wrote: > > On Thu, Feb 9, 2023 at 8:01 AM Richard W.M. Jones wrote: > > > David is building Fedora 37+ for RISC-V: > > > > > > http://fedora.riscv.rocks/koji/ > > > > > > > If I

Re: RISC-V -- are we ready for more, and what do we need to do it?

On Mon, Jan 9, 2023 at 3:22 PM Josh Boyer wrote: > > On Mon, Jan 9, 2023 at 9:15 AM Neal Gompa wrote: > > > > On Mon, Jan 9, 2023 at 8:47 AM Josh Boyer wrote: > > > > > > On Sun, Jan 8, 2023 at 2:42 AM David Abdurachmanov > > > wrote: > >

Re: RISC-V -- are we ready for more, and what do we need to do it?

On Sun, Jan 8, 2023 at 2:28 AM Jeff Law wrote: > > > > On 1/6/23 23:41, David Abdurachmanov wrote: > > > > Summary from multi-year discussions/feedback on this: > > - We don't have proper hardware to put into the data center that holds > > servers used by

Re: RISC-V -- are we ready for more, and what do we need to do it?

On Sat, Jan 7, 2023 at 2:42 AM Jeff Law wrote: > > > > On 1/6/23 16:19, Jun Aruga (he / him) wrote: > > I posted the same article on Fedora Discussion.[1] However let me > > share it again on the devel@ to tell it to many people. > > > > This is interesting news about RISC-V this week. Perhaps,

Re: F37 proposal: GNU Toolchain Update (glibc 2.36, binutils 2.38) (late System-Wide Change proposal)

On Fri, Jul 1, 2022 at 8:56 PM Ben Cotton wrote: > > https://fedoraproject.org/wiki/Changes/GNUToolchainF37 > > This document represents a proposed Change. As part of the Changes > process, proposals are publicly announced in order to receive > community feedback. This proposal will only be

Re: RISC-V -- are we ready for more, and what do we need to do it?

On Thu, Oct 7, 2021 at 1:30 AM Neal Gompa wrote: > > On Wed, Oct 6, 2021 at 1:50 PM Josh Stone wrote: > > > > On 10/4/21 12:12 PM, Neal Gompa wrote: > > > On Mon, Oct 4, 2021 at 3:07 PM Kevin Fenzi wrote: > > >> * How good is emulation support > > > > > > The lack of real hardware for RISC-V

Re: RISC-V -- are we ready for more, and what do we need to do it?

On Mon, Oct 4, 2021 at 10:13 PM Neal Gompa wrote: > > On Mon, Oct 4, 2021 at 3:07 PM Kevin Fenzi wrote: > > > > On Mon, Oct 04, 2021 at 01:03:27PM -0400, Matthew Miller wrote: > > > Hi all! I just got back from Open Source Summit, several of the talks I > > > found interesting were on RISC-V --

Re: correct combination (arch & abi) for rebulding gcc SRPM for RV64IMAFD on top of RISC-V Fedora image

On Tue, Mar 16, 2021 at 5:28 PM Richard W.M. Jones wrote: > > On Mon, Mar 15, 2021 at 11:24:47AM +0100, Florian Weimer wrote: > > * Takayuki Nagata: > > > > > I think "--with-arch=" should be "rv64g" for gcc without compressed > > > instruction support, because the default is RV64GC[0]. > > > >

Re: srpm rebuilding on RISC-V fedora image

On Thu, Mar 4, 2021 at 8:29 AM Billa Surendra wrote: > > > Without Correcting right URL to fedora-33-riscv64.cfg file we can not use > MOCK for rebuilding SRPM's for RISC-V architecture. Can anyone please > suggest what I can do now to correct it?. How can I contact MirrorManager to > correct

Re: How to build RISC-V Fedora disk image by muself

On Tue, Mar 2, 2021 at 4:03 AM Matthew Miller wrote: > > On Mon, Mar 01, 2021 at 09:28:40PM +, Richard W.M. Jones wrote: > > > > I am not sure how the image is actually built, but I have tried to > > > > build an image with appliance-creator on a RISC-V VM, and the built > > > > image is

Re: looking for scipy on python 3.8 (RISCV Fedora Release 32)

On Fri, May 22, 2020 at 8:53 PM David Abdurachmanov wrote: > > On Fri, May 22, 2020 at 5:57 PM Arun Sukumaran Latha > wrote: > > > > Thanks David for looking into the same. > > > > One more package I would need help build in fedora riscv for ultimately

Re: looking for scipy on python 3.8 (RISCV Fedora Release 32)

i/buildinfo?buildID=158506 Protobuf is not done yet. There seems to a regression in GCC 10 that causes the latest release (and a master branch) to fail. I will see if I can overcome it this weekend. Cheers, david > > Regards, > Arun SL > > On Mon, May 18, 2020 at 11:11 PM David Abdu

Re: looking for scipy on python 3.8 (RISCV Fedora Release 32)

ing those, but that will take some time. Cheers, david > Regards, > Arun SL > > On Sun, May 17, 2020, 17:25 David Abdurachmanov > wrote: >> >> On Sun, May 17, 2020 at 1:52 PM Arun Sukumaran Latha >> wrote: >> > >> > Thanks David, >> > >> > T

Re: looking for scipy on python 3.8 (RISCV Fedora Release 32)

f you can help me here as well. This particular package failed to build last time (compile time errors). I can give a look into it. Cheers, david > > Regards, > Arun SL > > On Sun, May 17, 2020 at 2:02 PM David Abdurachmanov > wrote: >> >> On Sat, May 16, 2

Re: looking for scipy on python 3.8 (RISCV Fedora Release 32)

On Sat, May 16, 2020 at 8:26 PM Arun Sukumaran Latha wrote: > > Hello All, > > I was working on getting tensorflow compiled within the RISCV Fedora > environment. > I am using the latest release 32 build. > Currently I am unable to install the dependent library, scipy due to the same > not

Re: Port fedora for RISC-V with out compressed instructions

On Thu, Dec 19, 2019 at 11:40 AM Sreenadh S wrote: > > We want to port fedora for RISC-V with out compressed (RV64IMAFD) > instructions. > > We are from Centre for Development of Advanced Computing (C-DAC) India. > We have implemented an Out-of order quad core RISC-V processor on FPGA. > > The

Re: Fedora without compressed instruction support

On Thu, Dec 5, 2019 at 12:30 PM Billa Surendra wrote: > > Dear David Abdurachmanov, > > I have seen your presentation about fedora bootstrap on RV64, it was very > nice presentation actually. I am planning to boot a RISC-V Fedora on QEMU > Emulator, but I want to do some

Re: I want build a RISC-V Fedora for supporting RV64IMAFD only not Compressed support

On Fri, Nov 15, 2019 at 4:07 PM Richard W.M. Jones wrote: > > On Fri, Nov 15, 2019 at 10:44:50AM +0530, Billa Surendra wrote: > > Dear Richard, > > > > I have booted Stage4 disk images > > on QEMU emulator, but > > it supporting compressed

Re: Donate 1 minute of your time to test upgrades from F29 to F30

On Sat, Mar 2, 2019 at 10:39 AM Nicolas Chauvet wrote: > > Le jeu. 28 févr. 2019 à 10:23, Miroslav Suchý a écrit : > > > > Do you want to make Fedora 30 better? Please spend 1 minute of your time > > and try to run: > > > > sudo dnf --releasever=30 --setopt=module_platform_id=platform:f30 >