On 10/30/13 2:06 PM, Thomas Grant wrote: > > On Wed, Oct 30, 2013 at 3:53 PM, Alexander Hansen > <[email protected] <mailto:[email protected]>> wrote: > > nm /usr/lib/system/libsystem_c.__dylib | grep waitpid > > > It appears that I do. I get the following: > > $ nm /usr/lib/system/libsystem_c.dylib | grep waitpid > 000000000009e736 T _waitpid > 000000000006f56a T _waitpid$NOCANCEL > > and DYLD_LIBRARY_PATH is set to /usr/lib64 > > Should there be other directories in that path? > > > -- > Thomas D. Grant, Ph.D. > Post-doctoral Scholar > Hauptman-Woodward Medical Research Institute > 700 Ellicott St. > Buffalo, NY 14203 > >
I'm not sure why you have that set, but it's somewhat risky to use DYLD_LIBRARY_PATH. What's going on here is that the linker is _only_ searching in /usr/lib64. To add additional library paths, it's often preferable to use DYLD_FALLBACK_LIBRARY_PATH, since items there get added to the system's link path. -- Alexander Hansen, Ph.D. Fink User Liaison My package updates: http://finkakh.wordpress.com/ ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Fink-users mailing list [email protected] List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
