From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: GLIBC 2.7 requirement for Standalone ConTeXt
Date: Thu, 23 May 2013 14:01:23 +0200 [thread overview]
Message-ID: <CAG5iGsBHaqL14mjKK_4WrZbGciJo3-EznDKWSvDjjbh2yujQTw@mail.gmail.com> (raw)
In-Reply-To: <1803592832.20130523134630@gmx.de>
[-- Attachment #1.1: Type: text/plain, Size: 662 bytes --]
On Thu, May 23, 2013 at 1:46 PM, Andreas Schneider <aksdb@gmx.de> wrote:
> Hello,
>
> I'm running a build server on an older box with CentOS 5. I didn't
> update ConTeXt Standalone in quite some time. Now I did since I had
> some problems with the dated version in use, and now I face the
> following problem:
>
> texlua: /lib/libc.so.6: version `GLIBC_2.7' not found (required by texlua)
> texlua: /lib/libc.so.6: version `GLIBC_2.11' not found (required by texlua)
>
> CentOS 5 still ships GLIBC 2.5. What can I do from here? Any chance on
> running ConTeXt without upgrading the whole system?
>
> can you build luatex on CentOS 5 ?
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1142 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-05-23 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 11:46 Andreas Schneider
2013-05-23 12:01 ` luigi scarso [this message]
2013-05-23 12:43 ` Mojca Miklavec
2013-05-23 13:22 ` Andreas Schneider
2013-05-23 13:51 ` Mojca Miklavec
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=CAG5iGsBHaqL14mjKK_4WrZbGciJo3-EznDKWSvDjjbh2yujQTw@mail.gmail.com \
--to=luigi.scarso@gmail.com \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).