bash build with configure options to replace edit Makefile

[brandon_peirce@…]

Ch 6.37.1. Installation of Bash uses sed to hack a htmldir into Makefile.in. Rather just use htmldir=... on the configure command like so: ./configure htmldir=/usr/share/doc/bash-3.0 --prefix=/usr --bindir=/bin \

--without-bash-malloc --with-installed-readline

This correctly sets htmldir in Makefile and doc/Makefile (have verified).

It would be a big help to those of us building with read-only sources who patch the sources only when essential and unavoidable...

[ken@…]

I'll test this in my current svn build, and I can see that this is more elegant

than using a sed.

But, if you mean that the sources are already extracted on a r/o filesystem,

that sounds like a major variation from the book, so I suspect you have to alter a lot more than just this one instruction.

[brandon_peirce@…]

(In reply to comment #1)

that sounds like a major variation from the book, so I suspect you have to alter a lot more than just this one instruction.

Your suspicions are correct, but I submitted believing the approach was nevertheless valid and useful to current LFS. Obviously it should be tested on a standard build setup. BTW, whenever LFS goes that way, the same approach works for bash 3.1

[ken@…]

Yes, I'm testing with 3.1 in svn. I can't imagine we would ever apply this to

6.1.1 as an errata. I've got to retest (for other reasons) with yesterday's utf8 changes, then I'll put this into svn.

[ken@…]

Sorry, I'm not going to do this. The wording in the book is quite clear that

installing the documentation is optional. Building with ./configure htmldir=/usr/share/doc/bash-3.1 --prefix... will work even if the documentation hasn't been extracted, BUT in that case it will create an empty /usr/share/doc/bash-3.1 directory - I regard that as a bad thing.

We really don't want to get into alternative sets of configure instructions,

nor into something which could facilitate people who downloaded the docs NOT installing them. The sed works.