From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: 'core-updates' spring 2018
Date: Tue, 27 Mar 2018 14:03:35 +0200 [thread overview]
Message-ID: <CAE4v=pi5Sv5ZCp3sa7Y5ORO25WKi3vWG+=dXW4rKUxabd3Ta_Q@mail.gmail.com> (raw)
In-Reply-To: <87a7uuhejf.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]
2018-03-26 20:34 GMT+02:00 Ricardo Wurmus <rekado@elephly.net>:
>
> Hi Marius,
>
> > 'core-updates' has seen a lot of changes recently. Some of the goodies
> > include […] glibc 2.27 […]
> >
> > Are there other things that should go in?
>
> I would really like to see a patch applied to glibc that ensures that
> the “prlimit64” syscall is not used when running on the RHEL 6 kernel
> (2.6.32). The lack of this syscall on that kernel means that getrlimits
> fails, which makes it impossible to start the JVM.
>
>
Hello!
We already talked about this on #guix, and the patch removing code to
check for prlimit64 not implemented is a quite self contained commit on
the glibc tree. It is not a trivial one, and I did not try to revert that
yet, but
it might worth looking at.
> This problem appeared with the upgrade to glibc 2.26 already, and ever
> since I’ve been trying to minimize the damage for RHEL 6 systems where
> Guix is used as a package manager (such as the MDC).
>
> A work-around for glibc 2.27 that makes things work fine with the RHEL 6
> kernel would be very welcome! I’ve started a branch “rhel6” where the
> default glibc has been bumped back to version 2.25 but I really don’t
> want it to be a long-lived branch; one of the reasons is that building
> all packages for this old glibc version (even just on x86_64) puts our
> build farms under extra stress that I would like to avoid.
>
> Another thing that could go in is the new Guile wrapper for wrapped
> scripts that I proposed a few months ago. It requires a change in
> build-side code to provide a “wrap-script” procedure (it wouldn’t be
> used just yet).
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
> https://elephly.net
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2505 bytes --]
next prev parent reply other threads:[~2018-03-27 12:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 10:29 'core-updates' spring 2018 Marius Bakke
2018-03-26 14:09 ` Ludovic Courtès
2018-03-26 18:34 ` Ricardo Wurmus
2018-03-27 12:03 ` Gábor Boskovits [this message]
2018-03-28 19:46 ` Ricardo Wurmus
2018-03-27 17:43 ` Marius Bakke
2018-03-28 13:32 ` Ricardo Wurmus
2018-03-29 11:29 ` Ludovic Courtès
2018-03-30 9:26 ` glibc fallback code when ‘prlimit64’ is missing Ludovic Courtès
2018-04-01 10:37 ` Ludovic Courtès
2018-03-27 20:28 ` 'core-updates' spring 2018 Mark H Weaver
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=pi5Sv5ZCp3sa7Y5ORO25WKi3vWG+=dXW4rKUxabd3Ta_Q@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.