On 30 July 2015 at 17:42, Russell Almond wrote: | Thanks for the suggestion. I do have a configure script (that is what | is reading the --with-netica arg) but I didn't think about searching the | standard install locations. I can probably use that to work around this | problem. | | However, that doesn't completely solve the problem. If I want to force | the configure script to use a non-standard location (say to use an | experimental version of the library), I still need to be able to pass | configure args to INSTALL and check. I admit the need for doing this | with build is a little bit less clear, although it is also unclear why | build (which is making a source tarball) needs to compile the C code.
Do not forget that you could also use an environment variable for truly non-standard location -- just like Windoze does for its configure-lacking existence. Standards are important, so by all means try to make it work via configure. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
