From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Builders of TeX binaries <binary-builders@contextgarden.net>
Subject: Re: GLIBC 2.7 requirement for Standalone ConTeXt
Date: Thu, 23 May 2013 15:51:50 +0200 [thread overview]
Message-ID: <CALBOmsZ_8vt+-dfq7dJ8pP_cK60q=ap2CTq3aygPkvinJU5rRw@mail.gmail.com> (raw)
In-Reply-To: <3210340001.20130523152227@gmx.de>
On Thu, May 23, 2013 at 3:22 PM, Andreas Schneider wrote:
> On Thursday, May 23, 2013, at 14:43 Mojca Miklavec wrote:
>> On Thu, May 23, 2013 at 1:46 PM, Andreas Schneider wrote:
>>>
>>> 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)
>
>> Is this about the 32-bit or 64-bit linux?
>
> 32bit.
Thank you. Feel free to blame Alan then.
I kept compiling LuaTeX binaries on an old SuSE virtual machine
(version 8.x) until recently. Then the need came for a newer compiler
(to be able to compile cairo) and Luigi installed a new compiler to
the box. Then we started compiling XeTeX which needed a newer
fontconfig at which point I "gave up" with maintenance (I felt that
installing fontconfig was relatively non-trivial, even though it
should be doable) and outsourced the task to Alan who compiled the
first luatex binary on 5th April and this was the first complaint
since then.
> As per Luigi's hint/question I built Luatex from SVN (apparently
> ./build.sh was all there was to it :-))
True.
> If you tell me what the needed steps are to get you the binaries build
> in a way that could be distributed, I would be willing to do that as
> long as my/our CentOS 5 installation is still up and running :-)
svn co http://svn.contextgarden.net/suite/build-binaries
./do_all.sh
(you also need the credentials to be able to submit binaries).
> (Depending on how often that needs to be done, since it's a machine on
> my workplace, so I can't access it anytime I like ...)
This needs to be done for every new release of LuaTeX. It's not that
often, but when it gets released, it's nice if the binaries are
committed soon(ish), particularly for the most common platforms
(i386-linux, x86_64-linux, *-darwin).
Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2013-05-23 13:51 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
2013-05-23 12:43 ` Mojca Miklavec
2013-05-23 13:22 ` Andreas Schneider
2013-05-23 13:51 ` Mojca Miklavec [this message]
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='CALBOmsZ_8vt+-dfq7dJ8pP_cK60q=ap2CTq3aygPkvinJU5rRw@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.com \
--cc=binary-builders@contextgarden.net \
--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).