From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: unbounded variable from `FATAL: kernel too old` ?
Date: Thu, 31 May 2018 11:59:50 +0200 [thread overview]
Message-ID: <CAJ3okZ1-y2tq-w9Y=2e1sRTGSv1zA3cOtL4Due8Z6fv1rCu2Jw@mail.gmail.com> (raw)
In-Reply-To: <87r2lsq514.fsf@elephly.net>
Hi,
>> I am installing the rnaseq Pigx pipeline from
>> https://github.com/BIMSBbioinfo/pigx/tree/master/pipelines/rnaseq
>
> Oh, nice!
Thank you to share !!
And nice paper ! :-)
Do you plan to implement a version with the GWL ?
> These variables are defined in Guix since quite some time, so you are
> probably using a rather old version of Guix. (The first two are defined
> in (gnu packages bioinformatics), the latter two in (gnu packages
> haskell).)
`guix --version` reports 0.14.0.
Weird ?
But if the kernel is too old, then somehow the install is not really
complete. Right ?
> 3.0 is just a tad too old for the C library. What system is this? Is
> this SLES from mid 2013? Are you able to upgrade to at least Linux 3.10
> or install the RHEL 6 kernel, which is known to work?
Yes, it is an old Suse.
My ideas was to be able to fetch up-to-date softwares without
modifying the current configuration (lazy sysadmin's work ;-)
> I’m afraid there’s no easy way to convince the C library that your
> kernel is compatible, because it’s very likely that it isn’t if it
> wasn’t heavily patched.
If I understand well, the shortest path seems to install a new system
from scratch, as GuixSD or Debian.
Thank you for all your explanations.
You save me some time.
All the best,
simon
next prev parent reply other threads:[~2018-05-31 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 18:47 unbounded variable from `FATAL: kernel too old` ? zimoun
2018-05-30 20:09 ` Ricardo Wurmus
2018-05-31 9:59 ` zimoun [this message]
2018-05-31 11:57 ` Ricardo Wurmus
2018-05-31 16:39 ` zimoun
2018-05-31 17:30 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ1-y2tq-w9Y=2e1sRTGSv1zA3cOtL4Due8Z6fv1rCu2Jw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).