On Thu, 6 Jan 2011, Donn Washburn wrote: > On 01/06/2011 12:11 PM, Christopher Sean Morrison wrote: >> On Jan 6, 2011, at 12:53 PM, Donn Washburn wrote: >> >>> I give all of the variables to configure as a script so it can be >>> redone >>> if needed or a new version comes out. >>> I took a look on the net for "DESTDIR Linux" and found a GNU site >>> worth >>> viewing >>> " http://www.gnu.org/prep/standards/html_node/DESTDIR.html"; >> That doesn't change anything I said other to given the rationale >> behind it. DESTDIR shouldn't be set for normal builds (unless you're >> doing staged installs). Staged installs aren't really useful outside >> of package management systems or build testing. Moreover, specifying >> parameters to configure is only have the picture -- the values set in >> the Makefile are what ultimately get used. What does your Makefile >> have set for the bindir, prefix, and exec_prefix variables? >> >> If any of them are empty, that would indicate a problem. >> >> Sean > Well I have followed your request to try exec-prefix=${prefix} and completely > reloaded a fresh cvs source. And have used nothing but autogen.sh and > ./configure. After it built it I did "make -n install" and it is /bin still. > I used my brlcad-conf-it script (which I can send you if you wish). I still > think it is a autoconf version headache. > > > Also this time it did build the src/options/tk and tcl Makefiles . ./misc/ > > Here is a short output of make -n install and my config file. > > I feel it is a autoconfig new version problem.
I recently compiled brlcad-7.18.0. Usually when I compile (BRLCAD or anything else), I do something like this: ./configure --help (and examine the options) echo "./configure --with-gnu-ld --with-x --enable-jove --enable-optimized">CONFIG And to configure, I just commandline `cat CONFIG` and hit return. The default has been to install BRLCAD to /usr/brlcad and I'm not sure why anyone would want to put it anyplace else, unless perhaps they wanted to specify --prefix=/usr/brlcad-x.xx.x or perhaps --prefix=/usr/brlcad-y.yy.y which gives good version control, and also keeps the BRLCAD libraries and executables (and shares etc) out of main paths. This also helps avoid versioning incompatibilities from creeping in. For example, the BRLCAD tcl/tk etc is meant to be very helpful with BRLCAD but it might bork anything else on your system which is expecting a somewhat different set of capabilities or specific versions of tcl/tk. Just an example. So you might as well just go with the defaults. Maybe write a little script to run right before each use, something like ----> #! /bin/bash export MANPATH="$MANPATH:/usr/brlcad/man" # or /usr/brlcad-x.xx.x/man export FB_FILE="/dev/Xl" # that "l" is a lower-case "L" export LD_LIBRARY_PRELOAD="$LD_LIBRARY_PRELOAD:/usr/brlcad/lib" export PATH="$PATH:/usr/brlcad/bin" # or /usr/brlcad-x.xx.x/bin whatever" If you want to go to the extreme effort of specifying --exec-prefix and that sort of thing, errors creep in rapidly and generally you're better off just specifying --prefix. Even if some distributions (Debian, Ubuntu etc) prefer to put everything under --prefix=/usr --sysconfdir=/etc/packagename --localstatedir=/var etc etc that's all very good for things that are designed to play well together, such as GNOME or a basic OS package load. But for "specialty" items such as BRLCAD you might want to just go mostly with the defaults. Note that sometimes you need to specify --exec-prefix to be the same as --prefix or you'll get the present problem of new executables going into /bin rather than into #prefix/bin. Regards, ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ BRL-CAD Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-users
