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: MkII in standalone distribution broken?
Date: Thu, 24 May 2012 11:50:28 +0200	[thread overview]
Message-ID: <CAG5iGsCoSJKKu_=ZeicDtcKgeH1+j4LxUV8U6Vnh1s-zM3FMUQ@mail.gmail.com> (raw)
In-Reply-To: <CALBOmsZ6Ehb1pha8M2up8gtiABS-Djinm+5PW1LSwacHiYpM_Q@mail.gmail.com>

On Thu, May 24, 2012 at 9:51 AM, Mojca Miklavec
<mojca.miklavec.lists@gmail.com> wrote:
> On Thu, May 24, 2012 at 9:19 AM, luigi scarso wrote:
>> On Thu, May 24, 2012 at 8:21 AM, Henning Hraban Ramm wrote:
>>> Just a short notice, can’t debug ATM:
>>> Since yesterday evening, ConTeXt doesn’t seem to be able to build MkII
>>> formats (via the first-setup script on OSX 10.5.8 Intel), it claims,
>>> cont-nl.mkii, cont-en.mkii, metafun would be missing.
>>> As far as I saw, MkIV builds.
>>
>> I think that  the problem is
>> warning: kpathsea: configuration file texmf.cnf not found
>
> If you avoid --make in ./first-setup.sh, then formats can normally be
> generated later. It is only that the script fails to generate formats
> for some reason.
>
> 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
> ___________________________________________________________________________________

mtxrun,  around line 16819:
It seems something wrong in
resolvers.luacnfspec =
"{selfautoloc:,selfautodir:,selfautoparent:}{,/texmf{-local,}/web2c}"
The line
   resolvers.luacnfspec =
"{selfautodir:,selfautoparent:}{,/texmf{-local,}/web2c}"
is ok, but still I suspect some syntax error


if environment.default_texmfcnf then
    -- unfortunately we now have quite some overkill in the spec (not
so nice on a network)
    resolvers.luacnfspec = environment.default_texmfcnf
else
 -- resolvers.luacnfspec = "selfautoparent:texmf{-local,-context,}/web2c"
-- the next line was the original one
 --   resolvers.luacnfspec =
"{selfautoloc:,selfautodir:,selfautoparent:}{,/texmf{-local,}/web2c}"
   resolvers.luacnfspec =
"{selfautodir:,selfautoparent:}{,/texmf{-local,}/web2c}"

end

-- 
luigi
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2012-05-24  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  6:21 Henning Hraban Ramm
2012-05-24  7:19 ` luigi scarso
2012-05-24  7:51   ` Mojca Miklavec
2012-05-24  9:50     ` luigi scarso [this message]
2012-05-24 10:05       ` Hans Hagen
2012-05-24 10:17         ` luigi scarso

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='CAG5iGsCoSJKKu_=ZeicDtcKgeH1+j4LxUV8U6Vnh1s-zM3FMUQ@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).