On Fri, Dec 14, 2001 at 09:53:02AM -0800, Aaron Bannert wrote: > On Fri, Dec 14, 2001 at 09:44:23AM -0800, Justin Erenkrantz wrote: > > On Fri, Dec 14, 2001 at 09:29:54AM -0800, Aaron Bannert wrote: > > > The -R flag shouldn't need to be solaris specific. Libtool interprets -R > > > and -rpath in the same way, and it turns it into whatever is appropriate > > > for the local linker. So just add -rpath (or -R if you prefer) always > > > for all platforms. > > > > The problem is at this point in the configure test, we don't > > have libtool up. =) I thought about that. But, I'm afraid > > that if we don't put the platform specific option there and we > > do an AC_TRY_RUN with the -R flag, we'll die due to a bad > > runtime search path. Am I wrong? -- justin > > Maybe I'm missing something, but I don't see how the library runtime > path would have any bearing on an AC test. It either links or it fails, > right?
Okay, say we do that. Remember that AC_TRY_RUN will compile, link, and run. By that time we've done the following: LDFLAGS="-Lpath/to/efence/lib -Rpath/to/efence/lib" LIBS="-lefence" The autoconf tests are handled by $CC *not* libtool. A linker that doesn't understand -R will die. We don't use libtool until the make process begins. Which means we need the platform-specific runtime linker flag at configure time. When we do make, we can rely on libtool handling the -R though. However, say we don't add the platform specific link flag, then all runs will fail on -R needing platforms since we linked against efence, but didn't specify where its runtime path was. -- justin
