[EPEL-devel] Re: R-3.3.0 errors compiling packages in CentOS 6

Rob O'Neale writes: > Then edit the FLIBS line in /usr/lib64/R/etc/Makeconf and remove all > the references to the static libraries /builddir//lib*.a (as per > the errors above). It happens I ran into the problem again on an update after

[EPEL-devel] RHEL build system

I was reviewing some documentation which includes: Redhat for example has a very optimal tool chain which they use for their Enterprise product line and it is not available to other distributions (or rebuilds) and thus their resulting binaries and libraries have been more performant then

[EPEL-devel] using epel-rpm-macros

How is the epel-rpm-macros package supposed to work? I have epel-rpm-macros-6-4 installed, which is up-to-date against epel-testing, and is supposed to make %license work like %doc but doesn't seem to have any effect. I get the same errors using %license in %files as without it installed

[EPEL-devel] Re: using epel-rpm-macros

Jason L Tibbitts III writes: > If you have a build dependency on the SCL tools then you're obviously > not building for EPEL, Well, I'm building for people running EPEL, and I didn't see this isn't with packages that depend on anything scl. The

[EPEL-devel] Re: Wrong mpich dependencies?

Orion Poplawski writes: > On 11/21/2016 06:08 AM, Tuomo Soini wrote: >> On Mon, 21 Nov 2016 12:52:12 +0100 >> Antonio Trande wrote: >> >>> Hi all. >>> >>> 'petsc' build is failing on epel7 because missing 'mpich-devel'; >>>

[EPEL-devel] Re: Can EPEL Repository provide LAPACK package which is compiled against OpenBLAS?

[Apologies if this appears twice, but it doesn't seem to have got through.] Brandon Hsu writes: > Hi, > > I try to compile and install some programs in CentOS 7 which depends on > LAPACK. > > I hope to use LAPACK linked to OpenBLAS,

[EPEL-devel] Re: Can EPEL Repository provide LAPACK package which is compiled against OpenBLAS?

Brandon Hsu writes: > Hi, > > I try to compile and install some programs in CentOS 7 which depends on > LAPACK. > > I hope to use LAPACK linked to OpenBLAS, which gives better performance > compared to Reference BLAS. OpenBLAS provides its own LAPACK, which has

[EPEL-devel] building with devtoolset

I thought devtoolset was now available for building EPEL packages, but I've just tried with something that needs a more recent gcc than el6's but neither devtoolset-6 nor -7 are found. Should that work? ___ epel-devel mailing list --

[EPEL-devel] missing -devel packages in 8 beta

Does anyone know what the situation is with -devel packages in RHEL8 beta? Many seem to be missing, so it's difficult to test EPEL builds for 8, and you can't necessarily rebuild ones that are shipped in the distribution; an example is openmpi, with most of the BRs missing. (I can't even do

[EPEL-devel] Re: missing -devel packages in 8 beta

Stephen John Smoogen writes: > Most -devel packages have been moved into the CodeReady Linux Builder > https://developers.redhat.com/blog/2018/11/15/introducing-codeready-linux-builder/ > which is supposed to be available in the developer subscription. If > the package you need isn't there then

[EPEL-devel] Re: missing -devel packages in 8 beta

R P Herrold writes: > What particular -devel are you seeking? Is it > non-versioned, such that you can work-around > with an earlier one? I gave an example; I assume the openmpi BRs are in the builder repo. > Customarily I would just bootstrap forward to a needed leaf > node package from

[EPEL-devel] any objections to BLIS soname bump in el7?

I'd like to upgrade the el7 blis package (v0.4) to the latest version (v0.6), which has a soname bump. It's not currently required by anything else in EPEL, and the BLAS compatibility shims won't change. Any objection? The current version has a potential security problem from using popen, and is

[EPEL-devel] Re: any objections to BLIS soname bump in el7?

Stephen John Smoogen writes: > Brought up at the meeting and there were no objections to doing this. Thank > you. Thanks, but I was really interested in uses outside Fedora packages, though I don't know of any for the non-BLAS interface, and there's probably no good place to ask. If you're

[EPEL-devel] EPEL8 R package rebuilds

I just tried to build an R package in copr, and it failed because an R dependency (which I maintain) needs rebuilding for R 4. Apart from the question of why R was updated to an incompatible version, what was supposed to happen about rebuilding things as a consequence? I got a large amount of

[EPEL-devel] Re: Getting conman into EPEL8

For what it's worth, there's a conman build for x86_64 and aarch64 in the loveshack/livhpc copr (untested). ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora

[EPEL-devel] how to do epel8 fedpkg mockbuild?

What do you need to do these days to run an epel-8 mock build? fedpkg mockbuild fails for me with Error: Error downloading packages: Status code: 403 for

[EPEL-devel] Re: how to do epel8 fedpkg mockbuild?

Pavel Raiskup writes: > I'd encourage anyone to update to the latest fedpkg (v1.42): > https://bodhi.fedoraproject.org/updates/?packages=fedpkg > > And Mock (configs v36.6): > https://bodhi.fedoraproject.org/updates/?packages=mock What I was using, in the hope it would help, is the latest in

[EPEL-devel] Re: how to do epel8 fedpkg mockbuild?

I wrote: > What do you need to do these days to run an epel-8 mock build? > fedpkg mockbuild fails for me with > > Error: Error downloading packages: > Status code: 403 for >