On Thu, Apr 30, 2015 at 07:32:32AM -0300, Fernando de Oliveira wrote:
> Re: r15900 and r15901.
> 
> Ken, thanks for the fixes.
> 
> Forgot the libraries in the commands (nettle), I had changed in my
> script and was going to change in the page:
> 
> CONFIGURE="./configure --prefix=/usr" &&
> INSTALLCOMMAND="make install &&
>                 chmod   -v   755 /usr/lib/lib{hogweed,nettle}.so &&
>                 install -v -m755 -d /usr/share/doc/${PACKAGE}    &&
>                 install -v -m644 nettle.html /usr/share/doc/${PACKAGE}"
> 
> This is better, because is version independent and does the job. That
> day I tested it both in DESTDIR and after actual install. I will change
> that in the book, to avoid future such problems. That was the initial
> intention and I forgot.
> 

Happens to all of us.  But does that chmod do the same thing ?  A
symlink is normally 777, what we need is to change its target (from
what I recall, the targets get installed as 644).
> About gnutls, I use the sed between configure and make in my script:
> 
> 
> #            lib/gnutls_privkey.c &&
> 
>       $CONFIGURE &&
> 
>       sed -e '/FUNCS=/ s/-d/&|uniq/'    \
>           -e '/get_x509_crt/ {n;d}'     \
>           -e '/get_x509_key/ {n;d}'     \
>           -e '/get_verify_flags/ {n;d}' \
>           -i doc/manpages/Makefile      &&
> 
>       time make -j${MKFLGS} &&
> 
> But when editing, IIRC, noticed that configure and make where in one
> block, and didn't want to to modify that. So, forgot the missing
> Makefile and put in the beginning.
> 
> Apologies for two big mistakes.

I haven't actually confirmed that applying the sed to configure.in
does the same thing, but it did let me build it.
> 
> Thanks for fixing.
> 
> About the recommended dependency and the grammar, I don't have excuse, I
> really commit these mistakes, and I will be always much thankful, when
> fixed.

English grammar changes, and what was there could be understood.  If
I hadn't been adding a paragraph just below it I would not have
bothered to alter it.

For recommended - when a dependency used to be optional, and we
already have it installed, it becomes much harder to find out that
a package now wants it.  Because I was building on a new system
without p11-kit, I found it.  At least the error message from
configure told me how to work around it.

ĸen
-- 
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to