<wiping egg off my face> I stand corrected. I was giving the configure a prefix of /tmp/cfngeine while spending the better part of today checking in /temp/cfengine for the resulting files. <D'Oh! Smack on the head> In addition to the wrong directory, cfengine was misspelled. Crap!
Thanks for the helpful words of encouragement. Ironically enough, the reason I'm building my own package is that I can't get to bolthole, and the package at sunfreeware (2.1.13) coredumps on every single one of my machines. Paul On Fri, 2006-01-13 at 10:24 -0500, PAUL WILLIAMSON wrote: > In attempting to build a custom package for all my solaris > machines, I discovered that --prefix doesn't work for ./configure. > Is there another option that replaces this, or do I need to > modify the configure file? Or, do I add the exec_prefix and > prefix when I make install cfengine? > > I don't want to make any assumptions, but I'm also new > to building packages. I'm just tired of compiling my apps > on the individual boxes. I figure if I really want to get > into cfengine, I should use it to distribute itself... > > Thanks, > Paul > > > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@gnu.org > http://lists.gnu.org/mailman/listinfo/help-cfengine _______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine
