On Wed, Jan 19, 2011 at 02:50:29PM -0500, Ken Raeburn wrote: > > I think the right answer for that is not to tell people that they > have to set environment variables in order to run Guile programs, > but to tell developers how to link programs properly so that they > find the library at run time. This tends to be somewhat > platform-dependent, but often arguments like "-R" or "-rpath" are > needed; libtool should just Do The Right Thing, if it's used. I'm > less familiar with pkg-config, but expect it should be have > similarly. In fact, the man page for pkg-config on my system (Mac > OS X with MacPorts installed) says the "--libs-only-L" option > "prints the -L/-R part" of the link options, which suggests to me > that pkg-config is indeed supposed to be printing options to set the > run-time load path. If it's not doing that for you, then we should > figure out why not. > > In short, don't document how to work around a bug, if you can just > fix the bug. :-) >
OK. Whichever approach is taken, readers of the Guile Reference Manual should be able to follow the steps described and have those steps work, that is, the generated program should run. My aim is to help get Guile 2.0 have as few defects as possible before it is released so that when new users try it, they have an error-free first pass.
