|Message: Re: DYLD_LIBRARY_PATH causes crashing on Mac (dyld: Symbol not found: __cg_jpeg_resync_to_restart)||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
On Sat, 28 Jul 2012 12:26:24 GMT, Mojca Miklavec wrote: > The problem is that DYLD_LIBRARY_PATH variable spoils the game. Namely, > I end up with another crash: > > dyld: Symbol not found: __cg_jpeg_resync_to_restart > Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO > Expected in: /opt/local/lib/libJPEG.dylib > in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO > Trace/BPT trap: 5 > > After unsetting DYLD_LIBRARY_PATH the examples start working properly. > Is there any generic remedy for that?
I think it'll depends how you want to set up the portfile and applications. The easiest thing to do is probably to wrap your application in a script which sets up the data library paths before running the application. That's a little hacky I admit, but would get it working. The other option is to add a patch to the portfile to remove the setting of the PATH and DYLD_LIBRARY_PATH - though here you'd still need to source the script before running the programs.
|Inline Depth:||Outline Depth:||Add message:|