On Mon, Jan 19, 2009 at 12:04 PM, Thomas A. Schmitz wrote:

On Jan 19, 2009, at 11:05 AM, Mojca Miklavec wrote:

...

Just start with a clean script. For example, replace the whole file with something like this:

(If luatex binary works well ... then nothing else in minimals that could "crash" at that moment is system-dependent, so I really suspect some mix up of local system libraries on your computer.)

if not modules then modules = { } end modules ['mtx-update'] = { version = 1.002, comment = "companion to mtxrun.lua", author = "Hans Hagen, PRAGMA-ADE, Hasselt NL", copyright = "PRAGMA ADE / ConTeXt Development Team", license = "see context related readme files" }

os.execute("rsync -av rsync://contextgarden.net/minimals/current/bin/luatex/osx-ppc/ tex/texmf-osx-ppc/")

OK. If I run this minimal version of mtx-update.lua, I get the same error. If I call the rsync ... command directly, it completes...

What does locate libiconv.2.dylib return you? Do you have any other version apart from the one in /usr/lib? otool -L /usr/lib/libiconv.2.dylib probably gives you 7.0.0, right? My only explanation is that luatex shields some system libraries. I have this for example ...

otool -L /Developer/SDKs/MacOSX10.3.9.sdk/usr/lib/libiconv.2.dylib /Developer/SDKs/MacOSX10.3.9.sdk/usr/lib/libiconv.2.dylib: /usr/lib/libiconv.2.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.0.0)

Maybe, maybe, maybe ... the cross-compiled luatex binary includes /Developer/SDKs/MacOSX10[whatever]/usr/lib/ into library search path with bigger precedence and then luatex sees that library before the one in /usr/lib when rsync requests it? Taco - would that be possible? How could one check if that might be the case? Mojca