On Mon, 31 Jan 2005, Dan Williams wrote: > On Mon, 31 Jan 2005, Eric Hoch wrote: > > > tcsh: dylib-link-list: Command not found. > > > > > > while various modules get build they all break with this error > > > message. Modules currently not building cause of this error are: > > > pspring, bridges and shell. > > > > > > Strange error because I use bash for building and not tcsh. > > > I used: > > > source MacosxEnv.Set.sh > > > > > > and I reset my PKG_CONFIG Path as adivced by Pavel. > > > > > > Switching to tcsh brought didn't solve the problem. > > > > > > Any ideas? > > > > No ideas? I am still stuck with this error and I can't go further > > in my buildings now that Mozilla is build. > > Eric, > > This particular script is one I had written a long while back. It > traverses the list of dylibs to be linked into one particular dylib (via > arguments to the link command) and adds the necessary Mac OS X glue. For > example, you have to list each dylib that you intend to link into the > final dylib on the link-line, _and_ the dylibs that are linked into those, > etc. For each library you need: > > "-dylib_file @executable_path/<lib>.dylib:/path/to/<lib>.dylib" > > otherwise you'll get unresolved symbol errors at link-time and run-time. > At least, you had to do this with Mac OS X up to 10.3 as far as I know. > > It should be in solenv/unxmacxp/bin/dylib-link-list. If its not, someone > needs to get it back and make sure its still called (which it looks like > it is since you're getting this error).
This file still appears to exist in CVS on HEAD, though its been removed in the src680_gnomepkg tag (which it probably shouldn't be). It also seems to be tagged for src680_m71s1, so it should be in your checkout. http://tools.openoffice.org/source/browse/tools/solenv/unxmacxp/bin/dylib-link-list More than likely the current PATH that the scripts set up doesn't include solevn/unxmacxp/bin or something like that. However, looking at: http://tools.openoffice.org/source/browse/tools/config_office/set_soenv.in?r1=1.31&r2=1.32 it seems to indicate that the correct path (solenv/unxmacxp/bin) which should be provided by the "$ps.'$SOLARENV'.$ds.'$OUTPATH'.$BIN." line. I'm not sure what's going on here. dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
