[EMAIL PROTECTED] wrote: > My Makefiles have: > > COPY = install > COPY_FILE= $(COPY) > COPY_DIR = $(COPY) -r > INSTALL_FILE= $(COPY_FILE) > INSTALL_DIR = $(COPY_DIR) > > This is due to line 1 of the sed which we apply to mkspecs/linux*/qmake.conf. > You *were* testing this on a *Linux* system, right? ;-)
"I see" said the blind man... It seems we are the one who broke the install. Is the change to install really necessary? I have not tested the Method 1 procedures. I don't personally like them, but they are there for those who do. It seems that we are changing cp to install in qmake.conf for the sake of those using qt (kde) while they installing a new version. It doesn't sound very safe to me. There are a couple of solutions that I can see: 1. Exit KDE when doing the 'make install'. With the exports in the procedure, it would probably be best to do the entire build wihout KDE running. 2. Change qmake.conf to use install, fix all the problems that causes, and then change it back. For those of you installing qt via Method 1, what are your preferences? Example scripts that have been tested are appreciated. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
