From: Alan BRASLAU <alan.braslau@cea.fr>
To: ntg-context@ntg.nl
Subject: Re: obscure luatex error
Date: Thu, 15 Oct 2009 17:08:01 +0200 [thread overview]
Message-ID: <200910151708.01876.alan.braslau@cea.fr> (raw)
In-Reply-To: <fe8d59da0910150736yf5a9fect283dab7e213ba046@mail.gmail.com>
On Thursday 15 October 2009 16:36:01 luigi scarso wrote:
> On Thu, Oct 15, 2009 at 4:32 PM, Matthijs Kooijman <matthijs@stdin.nl>
wrote:
> > Hi luigi,
> >
> >> > Do you think you could compile luatex with CFLAGS=-g, and run it in
> >> > gdb to get a backtrace? That might help to see where this comes
> >> > from...
> >>
> >> changing
> >> STRIP_LUATEX=TRUE
> >> in
> >> STRIP_LUATEX=FALSE
> >> in build.sh isn't enough ?
> >
> > I don't know the luatex build system, I just posted general instructions
> > :-)
>
> pretty simple, on linux:
> download source,uncompress and
> $>./build.sh
>
Not so easy: I have never compiled luatex before!
$ svn checkout http://foundry.supelec.fr/svn/luatex
(downloads 3.9G, including all beta versions in tag/)
$ cd trunk
$ ./build.sh --nostrip
...
libtool: link: gcc lib/lib.a
/home/local/src/luatex/trunk/build/texk/kpathsea/.libs/libkpathsea.a -lm
lib/lib.a(main.o): In function `main':
/home/local/src/luatex/trunk/build/texk/web2c/lib/../../../../source/texk/web2c/lib/main.c:26:
undefined reference to `mainbody'
collect2: ld returned 1 exit status
make[5]: *** [tangleboot] Error 1
make[5]: Leaving directory `/home/local/src/luatex/trunk/build/texk/web2c'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/local/src/luatex/trunk/build/texk/web2c'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/local/src/luatex/trunk/build/texk/web2c'
make[2]: *** [subtexk] Error 1
make[2]: Leaving directory `/home/local/src/luatex/trunk/build/texk'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/local/src/luatex/trunk/build/texk'
make: *** [all-recursive] Error 1
luatex binary not stripped
ls: cannot access build/texk/web2c/luatex: No such file or directory
$
So I do not yet have a compiled, unstripped version of luatex.
Alan
___________________________________________________________________________________
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:[~2009-10-15 15:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 19:37 virtual fonts in luatex? Thomas A. Schmitz
2009-10-01 7:48 ` Taco Hoekwater
2009-10-01 8:22 ` Thomas A. Schmitz
2009-10-01 17:55 ` Hans Hagen
2009-10-01 18:18 ` Thomas A. Schmitz
2009-10-01 18:23 ` Hans Hagen
2009-10-15 13:56 ` obscure luatex error Alan BRASLAU
2009-10-15 14:09 ` Matthijs Kooijman
2009-10-15 14:18 ` Taco Hoekwater
2009-10-15 14:27 ` luigi scarso
2009-10-15 14:28 ` Taco Hoekwater
2009-10-15 14:32 ` Matthijs Kooijman
2009-10-15 14:36 ` luigi scarso
2009-10-15 15:08 ` Alan BRASLAU [this message]
2009-10-15 15:13 ` luigi scarso
[not found] ` <200910160955.19746.alan.braslau@cea.fr>
[not found] ` <4AD86411.6040005@elvenkind.com>
2009-10-17 11:50 ` obscure luatex error (fixed!) Alan BRASLAU
2009-10-17 12:02 ` 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=200910151708.01876.alan.braslau@cea.fr \
--to=alan.braslau@cea.fr \
--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).