ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: weird bug updating minimals
Date: Sat, 17 Jan 2009 18:20:57 +0100	[thread overview]
Message-ID: <6faad9f00901170920n4d0c71e6p915589cb4198d7d2@mail.gmail.com> (raw)
In-Reply-To: <DC17B391-BC8F-4E4B-B08D-BBDEB53406A5@uni-bonn.de>

On Sat, Jan 17, 2009 at 6:02 PM, Thomas A. Schmitz wrote:
> Hi all, Mojca,
>
> after Taco resolved one issue with the latest luatex, I was trying to update
> on my osx-ppc box, and I am encountering a strange bug: when I run the
> ./first-setup.sh script, the rsync processes fail with this message:
>
> MtxRun | using script: ./bin/mtx-update.lua
>
> dyld: Library not loaded: /usr/lib/libiconv.2.dylib
>  Referenced from: /bin/sh
>  Reason: Incompatible library version: sh requires version 7.0.0 or later,
> but libiconv.2.dylib provides version 5.0.0
>
> 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
listed on this computer seem to be:

> otool -L luatex
luatex:
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 88.3.11)
        /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0,
current version 7.4.0)
        /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0,
current version 1.0.0)

I have (cross-)compiled the binaries on 10.4.something, so ... I'm
confused. Is your library too old or is the required library too old
(older than the one you have)?

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


  reply	other threads:[~2009-01-17 17:20 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 [this message]
2009-01-17 18:59   ` Thomas A. Schmitz
2009-01-17 19:52   ` Taco Hoekwater
2009-01-18 16:17     ` Thomas A. Schmitz
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=6faad9f00901170920n4d0c71e6p915589cb4198d7d2@mail.gmail.com \
    --to=mojca.miklavec.lists@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).