Re: Building from a local source code checkout

Martin Castillo skribis: > Why can't guix use the argument package name argument? > v-- this one > guix build python-activepapers --with-source=$HOME/Dev/AP Because there can be several packages passes as arguments to ‘guix build’. Now it would make sense to DTRT when there’s j

Re: website: showcase or list videos and slides, sources of all talks

Hello, sirgazil skribis: > On 20/12/17 17:32, Ludovic Courtès wrote: >> Hartmut Goebel skribis: >> >>> Am 19.12.2017 um 17:15 schrieb ng0: > It should be here: > >https://www.gnu.org/software/guix/blog/tags/talks/ >https://www.gnu.org/software/guix/blog/tags/papers/

Re: [WIP][PATCH] profiles: info-dir-file: Don't consider unwanted manifest entries

Martin Castillo writes: > Hi, > > in the second patch file: >> + ;; We only need to build the 'dir' file for inputs that does > containing info >> + ;; manuals. > s/containing/contain > Okay, thanks! > On 15.12.2017 16:12, 宋文武 wrote:> Hello! >> >> Currently we run profile hooks for all manife

Re: OpenBLAS and performance

Ricardo Wurmus writes: >> I was confused. I see the only version of the library shipped is built >> with pthreads. I think there should be serial, pthreads, and OpenMP >> versions, as for Fedora. > > Do these library variants have the same binary interface, so that a user > could simply preload

Re: OpenBLAS and performance

Ludovic Courtès writes: > Hello, > > Dave Love skribis: > >> Fedora sensibly builds separately-named libraries for different flavours >> , but I'd >> argue also for threaded versions being available with the generic soname >> in librray

Porting GuixSD to ARM article.

Hi Guix! A new article is available on Guix's website. It summarizes recent progress on ARM porting topic. https://www.gnu.org/software/guix/blog/2017/porting-guixsd-to-armv7/ Feel free to ask any question or propose follow-up actions here! Many thanks to Ludo, Danny and Ricardo for the early r

Re: website: showcase or list videos and slides, sources of all talks

On 22/12/17 04:32, Ludovic Courtès wrote: Hello, sirgazil skribis: On 20/12/17 17:32, Ludovic Courtès wrote: Hartmut Goebel skribis: Am 19.12.2017 um 17:15 schrieb ng0: It should be here: https://www.gnu.org/software/guix/blog/tags/talks/ https://www.gnu.org/software/guix/blog/t

Re: OpenBLAS and performance

For what it's worth, I get 37000 Mflops from the dgemm.goto benchmark using the current Guix openblas and OPENBLAS_NUM_THREADS=1 at a size of 7000 on a laptop with "i5-6200U CPU @ 2.30GHz" (avx2). That looks about right, and it should more-or-less plateau at that size. For comparison, I get 44000

Re: OpenBLAS and performance

Hi, Dave Love skribis: > Ludovic Courtès writes: > >> Hello, >> >> Dave Love skribis: >> >>> Fedora sensibly builds separately-named libraries for different flavours >>> , but I'd >>> argue also for threaded versions being available wi

Re: Porting GuixSD to ARM article.

Hello, On Fri, Dec 22, 2017 at 2:12 PM, Mathieu Othacehe wrote: > https://www.gnu.org/software/guix/blog/2017/porting-guixsd-to-armv7/ > > Feel free to ask any question or propose follow-up actions here! > Many thanks to Ludo, Danny and Ricardo for the early review :) I think there are typoes:

Re: Porting GuixSD to ARM article.

On Fri, Dec 22, 2017 at 02:12:02PM +0100, Mathieu Othacehe wrote: > > Hi Guix! > > A new article is available on Guix's website. It summarizes recent > progress on ARM porting topic. > > https://www.gnu.org/software/guix/blog/2017/porting-guixsd-to-armv7/ > > Feel free to ask any question or pr

Re: OpenBLAS and performance

On Fri, Dec 22, 2017 at 04:10:39PM +0100, Ludovic Courtès wrote: > Static binding has a cost, as you write, but it gives us control over > the environment, and the ability to capture and replicate the software > environment. As a user, that’s something I value a lot. > I’d also argue that this is

Packaging LyX

Hi all, I'm planning to switch a dozen or so machines to GuixSD. The only major package my users are missing is LyX (a LaTeX editor, see https://www.lyx.org/) so I packaged it, and it works fine. See code below. I would appreciate some help wrapping python. I'm familiar how to do this in Nix, bu

license naming

I've just read this link: https://www.fsf.org/blogs/rms/rms-article-for-claritys-sake-please-dont-say-licensed-under-gnu-gpl-2 Full Quote: > In this article, For Clarity's Sake, Please Don't Say "Licensed under GNU GPL > 2"!, Free Software Foundation president Richard Stallman (RMS) explains ho

Re: Packaging LyX

Hi, Gammel Holte transcribed 5.8K bytes: > Hi all, > > I'm planning to switch a dozen or so machines to GuixSD. > > The only major package my users are missing is LyX (a LaTeX editor, see > https://www.lyx.org/) so I packaged it, and it works fine. See code below. > > I would appreciate some he

Re: license naming

ng0 writes: > I've just read this link: > https://www.fsf.org/blogs/rms/rms-article-for-claritys-sake-please-dont-say-licensed-under-gnu-gpl-2 > > Full Quote: > >> In this article, For Clarity's Sake, Please Don't Say "Licensed under GNU >> GPL 2"!, Free Software Foundation president Richard S

Re: license naming

Jelle Licht transcribed 2.3K bytes: > > ng0 writes: > > > I've just read this link: > > https://www.fsf.org/blogs/rms/rms-article-for-claritys-sake-please-dont-say-licensed-under-gnu-gpl-2 > > > > Full Quote: > > > >> In this article, For Clarity's Sake, Please Don't Say "Licensed under GNU >

Re: Packaging LyX

Hmm, do the tests work for you? Back when I tried this was the blocker for me...

Re: OpenBLAS and performance

Pjotr Prins writes: >> > If I compile for a target it >> > makes a large difference. >> >> The FAQ document[1] says this: >> >> The environment variable which control the kernel selection is >> OPENBLAS_CORETYPE (see driver/others/dynamic.c) e.g. export >> OPENBLAS_CORETYPE=Haswell. And

Re: license naming

ng0 skribis: > My "problem", or rather the question I pose is: Does it make sense to > adjust how the license is displayed? Like instead of "GPL 2" We'd display > "GPL 2.0 only" and instead of "GPL 2+" (no example at hand to test if this > is the current display) we'd display "GPL 2 or later". S

Re: Packaging LyX

Danny Milosavljevic wrote: > Hmm, do the tests work for you? Back when I tried this was the blocker for > me... > Yes, they work fine. Aside, I've tested LyX for a few days and everything has worked as expected so far. After looking into all documentation, packages from other distros, and testi

Re: Porting GuixSD to ARM article.

> Very cool! Thanks Pjotr! Mathieu

Re: Porting GuixSD to ARM article.

Hi Vicent, > The definition on an installation image for the BeagleBone Black. > s/on an/of an/ Thanks for pointing it out. > In "Preparing a dedicated system configuration", I'm not sure, > but you have a "tty-O-0" in the system configuration: > > (tty "ttyO0") > > Isn't that a typo also ? N

Re: Packaging LyX

On Fri, Dec 22, 2017 at 7:42 PM, ng0 wrote: Thanks for your comments. I will address those before I circulate a patch. > Is this python-2 only? If not, could you explain why you picked 2 and not 3 > (2 is on its way out in 20 months). LyX is sadly not ready for Python 3 yet. It will be soon, bu

Re: Building from a local source code checkout

Konrad Hinsen skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> I agree the matching-name constraint can be annoying. The alternative >> would be allow the user to (optionally?) specify the name of the package >> whose source is being changed, as in: >> >> guix build python-activepapers \