chthon at chthon-uk.com
Mon Jun 16 18:23:43 PDT 2003
Jack Brown wrote:
> <Ryan.Oliver at pha.com.au> wrote in message
news:OF76DC605D.D8A3B8D0-ONCA256D47.002B9884-CA256D47.002B9982 at pha.com.au...
>> > in the src/INSTALL file it mentions using "make VIMRCLOC=/etc
>> > VIMRUNTIMEDIR=/usr/share/vim", here's a qote :
>> > Unix: PUTTING vimrc IN /etc
>> > Some Linux distributions prefer to put the global vimrc file in /etc,
>> > the
>> > Vim runtime files in /usr. This can be done with:
>> > ./configure --prefix=/usr
>> > make VIMRCLOC=/etc VIMRUNTIMEDIR=/usr/share/vim MAKE="make -e"
>> I looked at this some time ago... only thing that makes me a little wary
>> this method is the "make -e"
>> MSB pointed out a while ago that "make -e" = bad
>> Unsubscribe: send email to listar at linuxfromscratch.org
>> and put 'unsubscribe lfs-dev' in the subject header of the message
> I just didn't bother with the MAKE="make -e" part and just used make
> VIMRCLOC=/etc VIMRUNTIMEDIR=/usr/share/vim, worked fine as far as I can
> tell, is there some reason to
> think that the MAKE="make -e" part of it is necessary for the other
> settings to work?
> Jack Brown
ive tried it without make -e and the vimrc stuff didnt actually make it into
the final executable, so yes there is a VERY good reason for the make -e
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message
More information about the lfs-dev