Yes, I tried adding CXXFLAGS to the environment before running configure. Can't remember if it worked, but I think it should. However, with the solution I used it should work "out of the box" (just run configure and make install) for everyone (weird setup or not). But does anyone have any idea about the last problem I have? Did anyone try the build and hit this issue (or not)?
Appreciate the help, mihai On Tue, 2007-10-09 at 18:22 +1000, Mark Wright wrote: > Instead of modifying configure.in, an approach that works is > to configure tntnet like: > > export CPPFLAGS='-I/home/mdragan/Applications/tnt/include' > export LDFLAGS='-L/home/mdragan/Applications/tnt/lib > -R/home/mdragan/Applications/tnt/lib' > ./configure --prefix=/home/mdragan/Applications/tnt > > I'm not really sure about whether the LDFLAGS -R option > should be used or not on Linux. On Solaris, the -R > ld option is used to place the pathname of the dependent > shared libraries in shared libraries, which avoids having > to set LD_LIBRARY_PATH. > > Regards, Mark > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
