ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: weird bug updating minimals
Date: Sun, 18 Jan 2009 17:17:07 +0100	[thread overview]
Message-ID: <5C5F5191-D186-44FC-9981-A2D5BC35774B@uni-bonn.de> (raw)
In-Reply-To: <497236ED.2070701@elvenkind.com>


On Jan 17, 2009, at 8:52 PM, Taco Hoekwater wrote:

> Mojca Miklavec wrote:
>>>
>>> and so on. Now this box has several more or less abandoned  
>>> installations of
>>> darwinports and fink, but this looks like it's trying to link to  
>>> the library
>>> provided by the system (OS X 10.5.6) and complaining it's too old.  
>>> Any
>>> pointers to this one?
>> Hmmm ... libiconv? Is that comming from luatex? The only dependencies
>
> The immediate message comes from /bin/sh, probably from a nested call
> with a modified library path (rsync sounds like a likely candidate to
> me, but that is just guessing). luatex should not depend on libiconv  
> on
> any platform, and it doesn't alter the library search path (not that I
> know of, in any case).
>
> Best wishes,
> Taco

I just logged into this box as another user, and I'm still getting the  
same errors, so it's not simply an environment setting or wrong binary  
being called, and seems to be a real problem on the system level. Is  
anyone else using minimals on osx-ppc and could report if it's working  
for them?

Thomas
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2009-01-18 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17 17:02 Thomas A. Schmitz
2009-01-17 17:20 ` Mojca Miklavec
2009-01-17 18:59   ` Thomas A. Schmitz
2009-01-17 19:52   ` Taco Hoekwater
2009-01-18 16:17     ` Thomas A. Schmitz [this message]
2009-01-18 18:52 ` Mojca Miklavec
2009-01-18 19:01   ` Thomas A. Schmitz
     [not found]     ` <6faad9f00901190126v458db0c9ub2b0dfa070490e16@mail.gmail.com>
     [not found]       ` <372F9339-9A3D-4177-8A74-538AEBA424E5@uni-bonn.de>
     [not found]         ` <6faad9f00901190205n6558c687pbede6751fb27e916@mail.gmail.com>
     [not found]           ` <1A150475-139A-4572-8474-5D0A0A2F0560@uni-bonn.de>
2009-01-19 11:47             ` 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=5C5F5191-D186-44FC-9981-A2D5BC35774B@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --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).