Intel's Clear Linux optimizations
by František Zatloukal
Hi,
Phoronix recently release article[1] about Intel's Clear Linux with some
cool graphs showing nice performance gain compared to Xubuntu.
I didn't have time to dig in and look how it's performing against Fedora,
but I'd assume Fedora can be compared to Xubuntu in terms of compiler
settings.
I think i'll be interesting to look into it and find out if Fedora can't
tweak compiler settings (eg use LTO for critical things like Mesa, Kernel,
...). I think it could be interesting fo Fedora users to have this enabled
if there are not any disadvantages other than compile time, compile memory
usage and so on.
What do you think?
[1]
http://www.phoronix.com/scan.php?page=article&item=intel-clr-opengl&num=1
--
Best regards / S pozdravem,
František Zatloukal
Project Coordinator
Red Hat
1 month
kcov: code coverage for programs and python/shell scripts
by Dridi Boukelmoune
Greetings developers,
I just submitted a review request [1] for kcov [2] that I recently
discovered. It has no relation to Linux's kcov and is more akin to
lcov, except that all it needs is a binary with DWARF debuginfo
instead of requiring compile-time instrumentation.
I came across kcov when I was looking for a way to measure code
coverage in a Rust project and I'm impressed. It supposedly has a low
overhead, but so far I've been monitoring small single-threaded
programs so I can't really tell. I haven't tested python and shell
support, although I have cases where it would be relevant, but I don't
have time yet.
The package itself is simple, but it bundles javascript and doesn't
build on all main platforms so I may have to be granted an exception
from some group starting with an F. Been busy lately, I'm a little
behind on anything Fedora. If that's the case, please RTFM me a link
to the wiki, and if you want to take the review I'll gladly take one
in return.
Cheers,
Dridi
[1] https://bugzilla.redhat.com/show_bug.cgi?id=kcov
[2] https://simonkagstrom.github.io/kcov/index.html
1 month, 3 weeks
Rstudio
by Steve Grubb
Hello,
I like to have everything on my system in a package. So, I looked around and
found no recipe or rpm for Rstudio. This is really a shame because every
tutorial on R kinda tells you to install it. Even the Coursera classes in the
Data Science track make you install it and send a screenshot to prove it.
So, I spent some time getting it packaged and working. I am placing the spec
file and necessary patch here so that google finds it and saves other people the
trouble. I'm not wanting to submit the package to Fedora because its more work
than I have time for. If anyone else wants to take it from here and submit
and/or maintain it, feel free.
http://people.redhat.com/sgrubb/files/Rstudio/
Enjoy...
-Steve
9 months
SciDAVis and liborigin3 vs liborigin & liborigin2 - bundle or obsolete?
by Alexander Ploumistos
Hello,
Since its retirement from Fedora, SciDAVis[0] has undergone
significant development and I think it is ready to be re-included in
our package collection. After a few months of private builds that I
distributed among co-workers and friends, I set up a copr[1] and I've
been keeping up with the upstream project.
SciDAVis comes with a bundled copy of liborigin[2], which the upstream
developers helped me unbundle. Its version has been bumped to 3.0.0
internally, although there hasn't been a 3.0.0 release yet. In Fedora
we carry liborigin2 (code from the latest public release) and
liborigin (snapshot from 2008) which both help import different
versions of Origin project files. The new release will render them
both obsolete.
SciDAVis and liborigin share a number of contributors, but at the
moment their codebases have diverged; upstream liborigin trunk has
been adjusted to work with development versions of LabPlot 2.x, while
the copy bundled with SciDAVis is closer to that of a future
liborigin-3.0.0 release, but they are not interchangeable. I asked the
developers to clarify their plans and I was told[3] that the two
versions will merge back, though some API changes might come in the
meantime.
I have checked if there are any packages at the moment that require
liborigin* or liborigin*-devel and I have found none (though I'd be
grateful if someone who feels more at ease with dnf could
double-check). If not for this divergence, I would submit scidavis and
liborigin3 for review as separate packages, with Provides & Obsoletes
for the previous liborigin* and liborigin*-devel versions and be done
with it. However I would have to use the unbundled copy from SciDAVis
as source for liborigin3. Should I proceed with that anyway or should
I keep it bundled until such time as the two codebases have merged?
Best regards
Alex
0. https://sourceforge.net/projects/scidavis/
1. https://copr.fedorainfracloud.org/coprs/alexpl/scidavis/
2. https://sourceforge.net/projects/liborigin/
3. https://sourceforge.net/p/scidavis/discussion/708155/thread/4c8da018/#cf6b
9 months, 1 week
Using devtoolset for EPEL builds
by Zuzana Svetlikova
Hi,
I need/want/would like to build new node 6 for EL6, but gcc is too old.
For that reason, I'd like to use devtoolset-4-gcc, but the build fails
(obviously) because the package doesn't exist.
So, is there a way to make that work somehow?
I am not sure about enabling external repos during build, maybe someone
will be wiser.
Here's the build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=15970697
Zuzka
9 months, 2 weeks
apitrace, bundled libbacktrace
by Sandro Mani
Hi,
apitrace 5.0 bundles libbacktrace, which looks like is living within the
gcc sources. libbacktrace is not build as a shared library from the gcc
sources, and not packaged.
Is it feasible to build libbacktrace as a shared library and ship it in
a corresponding package? Or should I rather go for a bundling exception
request?
Thanks,
Sandro
10 months
F27 System Wide Change: NSS Default File Format SQL
by Jaroslav Reznik
= System Wide Change: NSS Default File Format SQL =
https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql
Change owner(s):
* Kai Engert <kaie(a)redhat.com>
Change the NSS library default to use the sqlite based data storage,
when applications don't specify their preferred storage file format.
== Detailed Description ==
Applications that use the NSS library often use a database for storage
of keys, certificates and trust. NSS supports two different file
formats, one called DBM (based on berkeley DB files) and another one
called SQL (based on sqlite DB files).
Today's default file format used by NSS, used when applications omit
the type parameter, is the older DBM file format, which forbids
parallel access to the storage. The suggestion is to change the
default file format to SQL, which allows parallel access to the
storage.
Applications, or users using the NSS command line utilities, often
provide the database storage location using a simple directory path
parameter. Some might not be aware, or forget, that the parameter can
be prefixed with a type modifier, either "dbm:" or "sql:".
As a result, when not providing this parameter, the file format used
will be the fragile DBM file format. This is particuarly problematic,
if a user attempts to modify the NSS storage using command line tools,
while another process, such as a daemon, is running concurrently,
which also accesses the same database in the DBM file format. This
often results in corrupted database storage, which cannot be
recovered.
By changing the default, all applications that currently use the DBM
file format, will automatically be migrated to the SQL file format.
NSS has the ability to discover if a storage location (a directory)
contains the DBM file format. If configured to use the modern SQL
format, NSS will automatically perform a one-time conversion from the
DBM to the SQL format.
The same applies to the NSS command line utilities. If the NSS library
default is changed to SQL, the NSS tools will also trigger the
one-time conversion, or access the already converted files.
== Scope ==
* Proposal owners:
A small downstream patch needs to be applied to the NSS library
package, which changes the library default.
* Other developers:
It's up to developers of NSS applications, if they accept the new
default and an automatic conversion, or if they prefer to continue to
use the classic DBM storage format. Although not recommended,
developers can easily do so, by adding a "dbm:" prefix to the storage
parameter they provide to NSS at NSS library initialization time.
* Release engineering: [1]
No help should be necessary. No mass rebuild necessary.
* Policies and guidelines: N/A
* Trademark approval: N/A
[1] https://pagure.io/releng/issue/6883
Thanks,
Jaroslav
10 months, 4 weeks
CI projects in Copr
by Miroslav Suchý
Hi,
I am gathering informations about various use of CI with Copr. Do you use Copr for building packages for nightlies? For
building packages before pull request is merged? Do you have your set up described somewhere? What is the name of your
project?
Please let me know. Either here or via private reply.
It will help me to understand your use of Copr and to make Copr better.
Thanks in advance.
Miroslav Suchy
11 months, 3 weeks
Re: Is it possible atlas is linked wrongly by new binutils?
by Richard W.M. Jones
On Thu, Aug 10, 2017 at 11:21:30AM +0200, Jakub Martisko wrote:
>
>
> On 9.8.2017 11:37, Richard W.M. Jones wrote:
> >
> > ocaml-gsl (OCaml bindings for GNU Scientific Library) currently
> > fails to link to atlas:
> >
> > + /usr/bin/ocamlfind ocamlopt -g -I lib -linkpkg -package bigarray -I lib -I examples lib/gsl.cmxa examples/blas_ex.cmx -o examples/blas_ex.native
> > /usr/lib64/atlas/libsatlas.so: undefined reference to `dlarfy_'
> > /usr/lib64/atlas/libsatlas.so: undefined reference to `slarfy_'
> > /usr/lib64/atlas/libsatlas.so: undefined reference to `clarfy_'
> > /usr/lib64/atlas/libsatlas.so: undefined reference to `zlarfy_'
> > collect2: error: ld returned 1 exit status
> >
> > However this only happens with the very latest atlas that was built by
> > binutils 2.29 (atlas-3.10.2-18.fc27.x86_64). It doesn't occur with
> > the previous version of atlas (atlas-3.10.2-16.fc26) even though there
> > seems to have been no change in atlas.
> >
> > $ nm -D /usr/lib64/atlas/libtatlas.so | grep larfy
> > U clarfy_
> > U dlarfy_
> > U slarfy_
> > U zlarfy_
> >
> > I looked in /usr/lib64 on my development machine which has atlas
> > installed but there is no .so* file that I can find which defines
> > these symbols. I also couldn't work out where in the atlas code
> > (which is a bit strange) these references are used.
> >
> > Hence the question: Is this breakage in atlas? binutils?
> >
> > Rich.
> >
>
> OK so it seems that according to git commit messages LAPACK
> has been rebased from 3.6.0 to 3.7.1 day before that mass
> rebuild [1][2]. Those "larfy" subroutines have been added to
> LAPACK in 3.7.0 and have not been present before[3]. I've
> tried to make a scratch build of atlas [4] and the missing
> symbols seem to be present...
>
> $ nm -D ./libtatlas.so.3|grep larfy
>
> T clarfy_
> T dlarfy_
> T slarfy_
> T zlarfy_
It looks as if you scratch build just changes ‘rm’ to ‘rm -f’ at one
point in the spec file. Is that change also needed?
I can do a bump and rebuild of atlas with or without that change - let
me know.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
11 months, 3 weeks
