On Wed, Jan 14, 2015 at 4:53 AM, Fernando de Oliveira <[email protected]> wrote:
> On 14-01-2015 00:17, alex lupu wrote: > > On Tue, Jan 13, 2015 at 7:08 PM, Fernando de Oliveira < > [email protected]> > > wrote: > > > >> On 13-01-2015 18:30, alex lupu wrote: > >>> BLFS Book version 2015-01-12, PHP-5.6.4 > >>> > >>> 1. I do not understand this move: > >>> > >>> mv -v /etc/php-fpm.conf{.default,} > >> > >> It is using brace expansion. It is an excellent form to decrease the > >> size of commands, by writing only once the common part. > >> > >> Try: > >> > >> $ echo /etc/php-fpm.conf{.default,} > >> /etc/php-fpm.conf.default /etc/php-fpm.conf > >> > >> This means that > >> > >> mv -v /etc/php-fpm.conf{.default,} > >> > >> is equivalent to > >> > >> mv -v /etc/php-fpm.conf.default /etc/php-fpm.conf > >> > >> See, e.g. "Bash Brace Expansion Tutorial: 6 Examples of Expanding > >> Expressions within Braces": > >> > >> http://www.thegeekstuff.com/2010/06/bash-shell-brace-expansion/ > > > > > > Hi Fernando, > > > > My problem was I never found a file 'php-fpm.conf.default' in '/etc' or > > anywhere else, so the mv command would _fail_, from my standpoint > {whether > > I had any idea about those braces or not :}. > > > > The mystery (i.e., the apparent _missing_ 'php-fpm.conf.default' file - > to > > be later renamed to 'php-fpm.conf' by the mv command) is two-fold:I > have: > > $ xzgrep php-fpm.conf.default php-5.6.4-2014.12.21-08h28m52s.log.xz > “/etc/php-fpm.conf.default” -> “/etc/php-fpm.conf” > > So, it works for me. I was going to write that i does work for me before > grepping a log, because my script would stop if this move failed. > > Is there a possibility that > > --with-config-file-path=/etc is missing in > your config command? > > I did use --with-config-file-path=/etc during configure. I suggest let's have a cooling-off period on this (it may just be I had renamed the file somehow (automatically, instinctively, etc.) before your move command: thus my mv failure). When I get a little time (a few days) I'll redo the whole PHP build on a clean system with a sharp eye toward what I get on /etc after 'make install' but _before_ your "bracket" move and report the results. By the way, how did you get such a detailed log on 'make install'? I normally do something along these lines: make install 2>&1 | tee install.txt ; echo $PIPESTATUS (i.e., I'm of the old (B)LFS school) Based on the above I got that succinct (an unusual) log from PHP (normally most packages describe in gory details like: /bin/mkdir -p '/etc/...' /usr/bin/install -c -m 644 ... '/etc/...' what they do every step of the way!). Also, while I'm at questions, what do you say about that funny "gz" doc file I keep getting? Thanks, cheers and patience, -- Alex PS As an aside, and LOW priority IMHO. For "Gimp-2.8.15" build documentation. I'd suggest a configure with optional --without-wmf libwmf is external to BLFS, listed as "Optional" (for good reason, here at Gimp). WMF files are not that critical for survival; thus people might not be up-to-date with 'libwmf', if at all. Gimp fails miserably on 'make' if you have an older version of the library hanging around.
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
