Gary, et al. Thanks for the response. I should preface that I was compiling from source on Haiku, where as on other Unix-like systems I have had no issues and it is all "black and white" when it comes to installation/compiling as I have been a long time vim user (and am happy to be a contributor as of late).
What I found misleading - to me - was no note that /bin is appended to a specified installation prefix. Keyword that "prefix" is what I took for granted. I suppose in hindsight I was half expecting it to say: By default, `make install' will install the package's files (and executable binaries, Jesse) in `/usr/local/bin', `/usr/local/man', etc. You can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. Remember, Jesse, that prefix means just that: we will add /bin to the prefix path (even if it doesn't exist, Jesse) to place compiled binaries in. If you add /bin to the end of your specified prefix, Jesse, such as `/boot/common/bin`, you will find vim inside `/boot/common/bin/bin/vim`. :-) In short, this was a 2 minute "scratch the head moment" and I was up using VIM with the compiled binary in the correct location for my OS. I just had to simply remove my own "/bin" addition to --prefix=/boot/common/bin (--prefix=/boot/common was the correct use). Finally, I just wanted to make that I hadn't lost my marbles, but looks like I did! I hope that answers your question to myself and to all, happy VIM'ing. -Jess On Mon, May 23, 2011 at 1:46 AM, Christian Brabandt <[email protected]>wrote: > Hi Gary! > > On So, 22 Mai 2011, Gary Johnson wrote: > > > On 2011-05-22, Jesse Benedict wrote: > > > I downloaded the latest vim73 bzip2 package for local compilation. > > > > > > Specifying ./configure --prefix=/boot/common/bin I find that upon > > > make/make install that the prefix has a secondary /bin attached to it. > > > > > > The result is the vim binaries are in /boot/common/bin/bin/ > > > > > > While I have this sorted out, is this a documentation issue for > > > INSTALL or has no one else encounter issues with pre-flight > > > configuration options and post-installation checks? > > > > What did you find confusing or misleading in INSTALL? It says > > > > By default, `make install' will install the package's files in > > `/usr/local/bin', `/usr/local/man', etc. You can specify an > > installation prefix other than `/usr/local' by giving `configure' > > the option `--prefix=PATH'. > > > > It also suggests running `configure --help', which contains > > > > --prefix=PREFIX install architecture-independent files in > PREFIX > > [/usr/local] > > > > I read both as saying that '--prefix' specifies the directory above > > bin. > > And this is quite common. At least, all software projects I worked on > behaved like this. > > regards, > Christian > -- > Oh! Seine Hochzeitsreise ganz allein machen! > -- Jules Renard > > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > -- ---- Jesse Benedict cp. 678.367.7030 em. [email protected] -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
