On 01/26/2013 05:11 AM, Randy McMurchy wrote: > Hi all, > > Earlier there was/is a discussion on why BLFS is adamant about describing > the various commands/descriptions/parameters/options used in the instructions > for BLFS packages. I would like to present a really good example why these > trivial (to us Editors) blurbs in the book are important. > > Installing the Obexd package today I noticed: > > 1) There is a sed command that adds a header file to one of the .c files in > the tarball before configure is run, there is no description of what it does > in the "Command Explanations", and without the sed command the package builds > and installs with no problems. Shouldn't readers be advised to why they must > run this command that apparently does nothing to help the build? >
My bad. It fixes building with Glibc 2.17. Doesn't throw an error if you use 2.16 or earlier. gcc -DHAVE_CONFIG_H -I. -I./src -I./src -I./plugins -I./gdbus -I./btio -I./gobex -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DOBEX_PLUGIN_BUILTIN -DPLUGINDIR=\""/usr/lib/obex/plugins"\" -D_FILE_OFFSET_BITS=64 -Wall -O2 -D_FORTIFY_SOURCE=2 -MT plugins/mas.o -MD -MP -MF $depbase.Tpo -c -o plugins/mas.o plugins/mas.c &&\ mv -f $depbase.Tpo $depbase.Po In file included from plugins/mas.c:40:0: ./src/obex.h:37:1: error: unknown type name ‘ssize_t’ ./src/obex.h:45:1: error: unknown type name ‘ssize_t’ ./src/obex.h:46:1: error: unknown type name ‘ssize_t’ In file included from plugins/mas.c:42:0: ./src/mimetype.h:36:2: error: expected specifier-qualifier-list before ‘ssize_t’ In file included from plugins/mas.c:43:0: plugins/filesystem.h:24:1: error: unknown type name ‘ssize_t’ plugins/mas.c: In function ‘get_params’: plugins/mas.c:131:2: error: unknown type name ‘ssize_t’ plugins/mas.c: At top level: plugins/mas.c:699:1: error: unknown type name ‘ssize_t’ plugins/mas.c:728:1: error: unknown type name ‘ssize_t’ plugins/mas.c:735:1: error: unknown type name ‘ssize_t’ > 2) There is a --sysconfdir=/etc switch to configure, yet there are no files > installed to /etc and no explanation why this must be passed during the > configure phase of the build. It seems as though the original editor who > installed the package used it 'just in case' there may be configuration files > in /etc. We cannot guess about this. We must be certain when we put stuff in > the book. Otherwise, we look like we are guessing at configuration options. > > 3) The --libexecdir= switch points to a non-standard location. libexecdir > location has always been /usr/lib/packagename, yet in the Obexd instructions, > the location varies from this. Is this because other packages expect it to > be where the libexecdir switch points to it, or simply because the Editor > who originally put the package in BLFS decided to go against the standards > that we have created? > You can see in gcc command I posted earlier that there is a define that points to /usr/lib/obex for plugins. I didn't want two directories to be used. Also, I wasn't aware of that standard. As for --sysconfdir, I thought that I saw same define that points to /usr/etc, but apparently I was wrong. > 4) The packages is a simple CMMI installation that varies from the standards > that BLFS has been using for years and years. Shouldn't there be some sort > of explanation why the instructions vary from the standards? > > Sorry for the rant, it got longer than I wanted, but I wanted to point out > that (as Bruce said) BLFS is not a linear installation process. We do not > know where a reader will start his/her BLFS adventure. So, because of this, > we must realize that a reader needs information as much as possible, as > mundane and redundant that it may seem to us Editors. > -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
