ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jannik Voges <researchjavo@icloud.com>
To: ntg-context@ntg.nl
Subject: Re: compilation error in LMTX
Date: Fri, 14 Aug 2020 14:56:14 +0200	[thread overview]
Message-ID: <93fb0f20-5074-1d16-e626-dca9d5bf6d1f@icloud.com> (raw)
In-Reply-To: <A518226B-3577-46FA-8E55-FADF287ABE37@toppkieker.info>

[-- Attachment #1: Type: text/plain, Size: 3211 bytes --]

Hello Lutz,


I can confirm this. Compiling luametafun.tex (see luametafun.zip; I
included the log-file, but the log-file doesn't include all the output I
can see on the console (therefore I included the file output_console.txt
with a copy of my console-output). I used linux aarch64.
Yes, commenting things out in my own tex-documents might result in a
successful compilation, but I had a document (which compiles normaly
now, but not two days before) where I got the same error at another
position in the file (after deleting all chapters after the one where
the error occurred including the one with the error).


Greetings

Jannik

Am 14.08.20 um 13:38 schrieb Lutz Haseloff:
> Hi all
> 
> I have a similar problem compiling luametafun.tex in the doc sources.
> It fails with different errorcodes on win64 and linux aarch64. On linux
> aarch64 i get a bonus "Segmentation fault".
> I append the console outputs of the context runs.
> 
> If i comment out the input of luametafun-axis and luametafun-followtext
> i get a readeable pdf.
> 
> So perhaps only the code is changing too rapidly.
> 
> Greetings Lutz
> 
> Am 14. August 2020 13:04:52 MESZ schrieb Hans Hagen <j.hagen@xs4all.nl>:
> 
>     On 8/14/2020 11:41 AM, Jannik Voges wrote:
> 
>         Hello Pablo,
> 
> 
>         thank you for your suggestions, but I don't use LMTX
>         productively, so I
>         have no problem with a broken LMTX-version. I only use it to check
>         whether there are breaking changes in LMTX by typesetting all of my
>         documents with the newest LMTX-version (to see if I need to
>         change them
>         in the future). And by doing so I recognized this error, which
>         seemed to
>         happen randomly.
> 
>     you can try to run with
> 
>     \tracingall
> 
>     and/or
> 
>     \enabletrackers[*]
> 
>     and see where it crashes
> 
>     Hans
>     ------------------------------------------------------------------------
>                                                Hans Hagen | PRAGMA ADE
>                    Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>             tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
>     ------------------------------------------------------------------------
>     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://context.aanhet.net
>     archive  : https://bitbucket.org/phg/context-mirror/commits/
>     wiki     : http://contextgarden.net
>     ------------------------------------------------------------------------
> 
> 
> ___________________________________________________________________________________
> 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://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
> 

[-- Attachment #2: luametafun.zip --]
[-- Type: application/zip, Size: 41771 bytes --]

[-- Attachment #3: 0x805A4918E8698418.asc --]
[-- Type: application/pgp-keys, Size: 664 bytes --]

[-- Attachment #4: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-08-14 12:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 10:49 Pablo Rodriguez
2020-08-14  0:38 ` Jannik Voges
2020-08-14  6:47   ` Hans Hagen
2020-08-14  7:26     ` Pablo Rodriguez
2020-08-14  7:47       ` Hans Hagen
2020-08-15 15:25         ` Pablo Rodriguez
2020-08-15 17:23           ` Hans Hagen
2020-08-15 18:14             ` Pablo Rodriguez
2020-08-15 21:54               ` Pablo Rodriguez
2020-08-15 18:51             ` Pablo Rodriguez
2020-08-14  9:40       ` Jannik Voges
2020-08-14  9:41       ` Jannik Voges
2020-08-14 11:04         ` Hans Hagen
2020-08-14 11:38           ` Lutz Haseloff
2020-08-14 12:56             ` Jannik Voges [this message]
2020-08-14 14:11             ` Hans Hagen
2020-08-14  9:29     ` Jannik Voges
2020-08-14  9:33       ` Wolfgang Schuster
2020-08-14  9:59         ` Jannik Voges

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=93fb0f20-5074-1d16-e626-dca9d5bf6d1f@icloud.com \
    --to=researchjavo@icloud.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).