ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug updating the ConTeXt Suite?
Date: Mon, 6 Nov 2017 22:18:26 +0100	[thread overview]
Message-ID: <CAG5iGsC7djgbsjZnB0c3cKsKwobjDquoHBFdhkpoYSac6cd68w@mail.gmail.com> (raw)
In-Reply-To: <CAG5iGsAp9X5Y+qy0jysDtSf9fyixFCnLxciHS99DfFRRnG63SQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 843 bytes --]

Il 6 nov 2017 22:13, "Mojca Miklavec" <mojca.miklavec.lists@gmail.com> ha
scritto:

On 6 November 2017 at 20:07, Pablo Rodriguez <oinos@gmx.es> wrote:
> On 11/06/2017 07:04 PM, Floris van Manen wrote:
>> so is the error related to an incompatible luatex?
>
> Florian,
>
> I know that correlation isn’t causation, so I can only guess ;-).
>
> It might be that ConTeXt Standalone should have the binaries updated in
> all platforms.

I manually updated linux, but all other platforms are still outdated
from trunk. The tagged version doesn't compile at all (maybe it
requires C++11?).

There were some architectural changes and I'm not able to access some
build machines, including an old Mac VM (I can create a new one
locally, just not today).


Yes , poppler needs c++11 (and the new lua 5.3 gcc 7.2.0)

--
luigi

[-- Attachment #1.2: Type: text/html, Size: 1672 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 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
___________________________________________________________________________________

  parent reply	other threads:[~2017-11-06 21:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05 12:43 Pablo Rodriguez
2017-11-05 22:02 ` Joseph Canedo
2017-11-06 17:55   ` Pablo Rodriguez
2017-11-06 18:04     ` Floris van Manen
2017-11-06 19:07       ` Pablo Rodriguez
2017-11-06 21:13         ` Mojca Miklavec
     [not found]           ` <CAG5iGsA=gXdVbH0miNuckm5zSRMCYDHrmKNsGhyfVNqB81zUzA@mail.gmail.com>
     [not found]             ` <CAG5iGsAp9X5Y+qy0jysDtSf9fyixFCnLxciHS99DfFRRnG63SQ@mail.gmail.com>
2017-11-06 21:18               ` luigi scarso [this message]
2017-11-06 21:37           ` Pablo Rodriguez
2017-11-06 20:56     ` Joseph Canedo
2017-11-06  8:56 ` Henning Hraban Ramm
2017-11-06  9:31   ` Floris van Manen
2017-11-06 17:58     ` Pablo Rodriguez
2017-11-06 18:15       ` Floris van Manen
2017-11-06 17:56   ` Pablo Rodriguez

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=CAG5iGsC7djgbsjZnB0c3cKsKwobjDquoHBFdhkpoYSac6cd68w@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).