Niels Mller wrote... > Bryan Loniewski <[EMAIL PROTECTED]> writes: > > > That was indeed the case! Thanks Pete. I needed to > > > > ./configure LDFLAGS= CPPFLAGS= > > > > and all worked... using --with-lib-path and --with-include-path did > > not seem to work, > > Are you saying you used --with-lib-path and --with-include-path with no > arg? That's not how they're supposed to be used, if it works at all, > it should just be a nop.
In my case, I used those options to configure to give the preprocessor and linker the relevant paths - I didn't leave them blank. For some reason, this always failed with the linker being unable to find liboop during one of the configure tests - basically exactly where Brian struck trouble. > If you mail me the config.log, I can have a look at it. --with-*-path > works for me, on Solaris. Niels, I wonder where your libraries and includes are installed on your Solaris system? If they're all installed under /usr/local then it may be that GCC is finding them there regardless of your configure options - GCC's default path to look for those things is /usr/local. In my case, I install each such library under its own package directory in /opt. For example, /opt/liboop. I am wondering if this only fails for people who use a path for those things outside of the GCC default of /usr/local. _______________________________________________ lsh-bugs mailing list [EMAIL PROTECTED] http://lists.lysator.liu.se/mailman/listinfo/lsh-bugs
