similar to: Rebuild against FlexiBLAS

I agree that the "R Installation and Administration" guide statement about FlexiBLAS needs an update. Standard R in CentOS Stream 9, which is now downstream from Fedora, gives the following result for Matrix products in sessionInfo(): > sessionInfo() R version 4.3.1 (2023-06-16) Platform: x86_64-redhat-linux-gnu (64-bit) Running under: CentOS Stream 9 Matrix products: default

On 10/11/23 23:12, George Ostrouchov wrote: > I agree that the "R Installation and Administration" guide statement about FlexiBLAS needs an update. Standard R in CentOS Stream 9, which is now downstream from Fedora, gives the following result for Matrix products in sessionInfo(): > >> sessionInfo() > R version 4.3.1 (2023-06-16) > Platform: x86_64-redhat-linux-gnu

Hi, I'm hitting that issue since Mesa 20.0.6 and it is present still in latest version 20.1.7 ``` [tkloczko at barrel SPECS]$ coredumpctl gdb 3926866 PID: 3926866 (test_va_api) UID: 1000 (tkloczko) GID: 1000 (tkloczko) Signal: 11 (SEGV) Timestamp: Sun 2020-09-13 18:57:06 BST (32s ago) Command Line: ./test_va_api Executable:

Hello, I encountered errors when building rpm on fedora33: Versions: libvirt: v6.9.0-rc2 gcc-10.2.1-5.fc33.x86_64 meson-0.55.3-1.fc33.noarch ninja-build-1.10.1-2.fc33.x86_64 binutils-2.35-11.fc33.x86_64 Steps: 1. Archive libvirt source code to ~/rpmbuild/SOURCES/libvirt-6.9.0.tar.xz 2. Copy libvirt.spec.in to ~/rpmbuild/SPECS/libvirt.spec. Then `sed -i s/@VERSION@/6.9.0/g

$ libguestfs-test-tool ... libguestfs: launch: version=1.42.0fedora=33,release=5.fc33,libvirt ... libguestfs: build appliance libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib/guestfs) ... It appears that this configure test is now failing:

Patch 2 certainly allows you to set the thread model. However patch 3 shows that if you set it to nbdkit.THREAD_MODEL_PARALLEL it will crash. If you look closely at the stack trace (attached below) you can see that ignoring threads which are in parts of nbdkit unrelated to Python: Thread 4: In pread, waiting in time.sleep(). This thread has released the GIL. Thread 2: Started to

On Fri, Oct 30, 2020 at 10:30:00AM +0800, Han Han wrote: > Hello, > I encountered errors when building rpm on fedora33: > > Versions: > libvirt: v6.9.0-rc2 > gcc-10.2.1-5.fc33.x86_64 > meson-0.55.3-1.fc33.noarch > ninja-build-1.10.1-2.fc33.x86_64 > binutils-2.35-11.fc33.x86_64 > > Steps: > 1. Archive libvirt source code to

On Wed, 16 Apr 2025 at 09:48, Roger Bivand via R-SIG-Fedora < r-sig-fedora at r-project.org> wrote: > Building R 4.5.0 from source on Fedora 42 hits problems because 42 ships > with Tcl/Tk 9. tcl8-devel and tk8-devel are available and can be used, but > I haven't yet found a viable incantation yet. Neither R released nor devel > support Tcl/Tk 9

On Tue, 9 Jun 2020 at 10:21, I?aki Ucar <iucar at fedoraproject.org> wrote: > > > Given the huge amount of builds (and rebuilds) in this process, I am > > strongly disinclined to attempt this work for Fedora 32 (the idea of > > hundreds of bodhi overrides does not fill me with joy), but I would not > > prevent someone else who wished to try to do so. > > Note

Dear Miguel Esteva, I couldn't get a Red Hat "ubi9" container to install enough dependencies to build R. Is there a way to reproduce your setup on a virtual machine somewhere? On Fri, 3 May 2024 00:42:43 +0000 Miguel Esteva via R-help <r-help at r-project.org> wrote: > *** caught segfault *** > > address 0x1801fa8f70, cause 'memory not mapped' > >

On Wed, 16 Apr 2025 at 10:11, I?aki Ucar <iucar at fedoraproject.org> wrote: > On Wed, 16 Apr 2025 at 09:48, Roger Bivand via R-SIG-Fedora < > r-sig-fedora at r-project.org> wrote: > > > Building R 4.5.0 from source on Fedora 42 hits problems because 42 ships > > with Tcl/Tk 9. tcl8-devel and tk8-devel are available and can be used, > but > > I

Hello, Would a less resource-intensive value, such as 1, be a safer default CPU value for confint? I noticed excessive CPU usage on a I.T. administrator-managed server which was being three-quarters used by another staff member when the confidence interval calculation in an R Markdown document suddenly changed from two seconds to ninety seconds because of competition for CPUs between users. Also,

Building R 4.5.0 from source on Fedora 42 hits problems because 42 ships with Tcl/Tk 9. tcl8-devel and tk8-devel are available and can be used, but I haven't yet found a viable incantation yet. Neither R released nor devel support Tcl/Tk 9 https://www.tcl-lang.com/software/tcltk/9.0.html. Building against external BLAS is also not self-evident, so may need guidance. Any suggestions welcome!

Seems like this in 83986 [1] needs a fix in Lapack.c: if (dladdr((void *) F77_NAME(ilaver), &dl_info)) { char buf[PATH_MAX+1]; char *res = realpath(dl_info.dli_fname, buf); if (res) { SEXP nfo = R_NilValue; if (strstr(res, "flexiblas")) nfo = R_flexiblas_info(); if

Maybe Elliott? On Tue, 23 Jun 2020 at 15:01, Tom Callaway <spotrh at gmail.com> wrote: > > At this point, I simply don't have the time. > > Tom > > On Tue, Jun 23, 2020, 6:06 AM I?aki Ucar <iucar at fedoraproject.org> wrote: >> >> On Tue, 9 Jun 2020 at 10:21, I?aki Ucar <iucar at fedoraproject.org> wrote: >> > >> > > Given

From the R Installation and Admin manual: "There is a tendency for re-distributors of R to use ?enhanced? linear algebra libraries without explaining their downsides.? There?s a downside not mentioned in the manual that caught and baffled me for a while. I was using all 64 cores of an AWS instance via parallel::mclapply() and doing matrix multiplications in the parallelized function. If

I've not worked changing underlying computational infrastructure, but developers who do might want to use ideas from FlexiBLAS. Apologies in advance if this is well-known. Best JN > From: Martin Koehler koehlerm at mpi-magdeburg.mpg.de > Date: January 07, 2016 > Subject: FlexiBLAS Version 1.3.0 Release > > It is our pleasure to announce the new release of FlexiBLAS. We do not

On Tuesday, 23 June 2020 14.01.39 WEST Tom Callaway wrote: > At this point, I simply don't have the time. > > Tom What needs to be done and how can the work be streamlined? I asked this since this procedure will happen for other updates (in one year I know but time flies). I am a provenpackager so that I can drive the process. Regards, -- Jos? Ab?lio [[alternative HTML

? Tue, 21 May 2024 08:00:11 +0000 Dario Strbenac via R-devel <r-devel at r-project.org> ?????: > Would a less resource-intensive value, such as 1, be a safer default > CPU value for confint? Which confint() method do you have in mind? There is at least four of them by default in R, and many additional classes could make use of stats:::confint.default by implementing vcov(). >

Hi Ivan, An apology, I was away for quite a bit. To reproduce the setup: I have been using the default GCC in RHEL 9.1. gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/11/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-redhat-linux Configured with: ../configure --enable-bootstrap --enable-host-pie