Miscellaneous small problems with BLFS 'live'

Bernard Leak thisisnotapipe at hotmail.com
Thu Aug 31 18:31:55 PDT 2006

>From: Bernard Leak <bernard at brenda-arkle.demon.co.uk>
>To: thisisnotapipe at hotmail.com
>Subject: Miscellaneous small problems with BLFS 'live'
>Date: Fri, 01 Sep 2006 02:23:31 +0100
>Dear List,
>                  these are problems seen in svn-20060809 and still there 
>svn-20060830 (which I've just checked).  There are miscellaneous
>problems (typos, bad links...), and several cases in which apparently
>inconsistent link targets for various dependencies not themselves in
>BLFS were spotted.
>[Bad annotation]
>The a2ps page
>annotates the 'sed' tweak
>sed -i -e "s|char \*malloc ();|/* & */|" lib/path-concat.c
>by saying 'This command fixes a build problem with GCC-3.4.x' .
>This is still current, and it's a library-headers problem rather
>than a gcc problem (though before 3.4 gcc may not have been
>fussy enough to complain about it).
>[Missing punctuation]
>Optional (To Build Experimental passdb Libraries
>(adding a closing parenthesis would be good)
>[Spelling errors]
>Dependency on vim calls it 6.4 (correct, but not caught up with *stable*
>'AMR naarrowband (fixed point)' for 'AMR narrowband' occurs in anchor
>text in
>under the 'Optional CODECs' header
>and in
>under the 'Optional' header
>The MIT krb5 and Heimdal pages have 'principle' for 'principal' throughout
>The Xbitmaps and MesaLib pages both have 'Xorg Utilitites' in anchor
>text under the heading 'Required'
>[A minor capitalisation inconsistency]
>has 'Jasper' as anchor text under the heading 'Optional Graphics Utilities'
>(the author seems to prefer JasPer, which is the form
>found at
>as anchor text under the heading 'Optional' (in both cases)
>[Minor URL discrepancy]
>Possibly someone may care about these discrepancies:
>Two different source URLs:
>electric-fence http://perens.com/FreeSoftware/
>electric-fence http://www.perens.com/FreeSoftware/ElectricFence/
>Currently perens.com and www.perens.com are the same
>All these are 'Optional': the ImageMagick page has it classified
>more specifically under 'Optional System Utilities'
>http://www.linuxfromscratch.org/blfs/view/svn/general/graphviz.html has
>long form
>These have the short form:
>[Pointless link target inconsistencies]
>The URL for Mono is in two places given as 'http://go-mono.org',
>which is a bit pointless, as it merely redirects at once to the
>other URL given, which is 'http://www.mono-project.com/Main_Page'.
>... and more of the same, this time for Valgrind:
>http://valgrind.kde.org/ simply redirects to http://valgrind.org/
>while the other links are to http://www.valgrind.org/
>www.valgrind.org and valgrind.org are currently the same
>valgrind.kde.org @
>Shouldn't 'CURL' be 'cURL'?
>[Bad links as well as inconsistencies]
>Rather suspiciously, in the GMime page
>the link from 'Mono' is to 'http://www.mono-project.com/Main_Page',
>but the 'Optional' anchor 'Gtk#' is linked to 
>which is a bad link.  I suggest the following replacement:
>'http://www.mono-project.com/GtkSharp' .
>Better and better, the link to that exact page in
>has a different anchor text ('GtkSharp-1.0.x').
>the link given for the download link is to 'http://go-mono.com/sources/',
>with the URL as anchor text, and that's bad too (not very surprisingly).
>I suggest the following replacement:
>And more (yet more) of the same: 'Optional' dependencies on 'Jikes'
>(with that as the text of the anchor) include a bad link.
>The link on the Subversion page at
>is to
>which is is now redirected to
>Following this up shows that a good link, apparently current, is to
>which is correctly used in the Libidn page
>[Inconsistencies with no very obvious 'correct' resolution]
>These pages contain links with anchor text 'VCDimager', all for
>'Optional' dependencies:
>link to http://www.gnu.org/software/vcdimager/
>link to http://www.vcdimager.org/
>Both link destinations are valid, but the latter appears to be the
>canonical home-page, and it has a slightly more useful set of links.
>The only reason I can think of for preferring the former is that it
>tells users to pick a local mirror for downloads, with a link to a
>list, rather than leading them to a specific download site.
>Now a startling raft of variants, some rather important, for libgpg-error.
>Anchor text 'Libgpg-error'
>Link target 'http://www.gnupg.org/download/index.html#libgpg-error'
>Anchor text 'libgpg-error'
>(a) ftp Link target 'ftp://ftp.gnupg.org/gcrypt/alpha/libgpg-error/'
>(These are old versions, up to 0.7 inclusive: surely this is a mistake?)
>(b) http targets
>The two variant targets are not clearly distinct, and may well represent 
>same original file.  The file has links to the latest versions of several
>packages in the gnupg suite, with a link at the top (by-passed by the
>#libgpg-error) to a list of gnupg-specific mirrors.  This is probably the
>link to prefer, but it's a little unfortunate that the links provided
>can become out of sync. with the BLFS versions.
>(c) a confused target
>xsoft/gaim.html        http://ftp.gnupg.org/gcrypt/libgpg-error/
>n.b.: replacing the protocol with 'ftp:' is actually better
>even in a Web browser, as it gives date information rather than stream
>type information!  If you really want an ftp URL, this is probably the
>one to use: it goes straight to the download directory.
>[Too fussy to live dept.: trivial target differences]
>Trivially different URLs for external references:
>to 'libid3tag', used as anchor text in two places:
>URL http://sourceforge.net/projects/mad
>(under heading 'Optional', as an accompaniment to 'libmad')
>URL http://sourceforge.net/projects/mad/
>(under heading 'Optional')
>to 'MMX Jpeg', used as anchor text in two places:
>URL http://sourceforge.net/projects/mjpeg
>URL http://sourceforge.net/projects/mjpeg/
>(under heading 'Optional' in both cases)
>*phew*.  Enough for today...
>                                                     Bernard Leak

Windows Live™ Messenger has arrived. Click here to download it for free! 

More information about the blfs-dev mailing list