Replace backsticks (`) with $().

[William]

I would like to rise this issue again since some users tends to read it as single quote (') instead. To make the book clearer, I suggest replace those backsticks with $().

This issue exists in LFS/BLFS too.

William

[jim]

Could you provide some examples of the necessary changes for the team to evaluate.

[William]

Two examples:

1. LFS toolchain adjusting.

SPECFILE=dirname $(gcc -print-libgcc-file-name)/specs && gcc -dumpspecs > $SPECFILE

can be written as

SPECFILE=$(dirname $(gcc -print-libgcc-file-name))/specs && gcc -dumpspecs > $SPECFILE

Why do we use both syntax at the same time?

2. BLFS X.Org.

sed -i -e "s@^{#include <linux/config.h>@/* & */@" \}

grep -lr linux/config.h *

can be changed to sed -i -e "s@^{#include <linux/config.h>@/* & */@" \}

$(grep -lr linux/config.h .)

For the sake of clarity.

[jim]

Will assign a couple of people to look at this to see what it would affect. Matt, can you see what changes would be needed to support this.

[chris@…]

The only places in the book where backticks are used are the "variables" section (for setting the LFS_HOST, as well as LFS_TARGET for mips64) and the toolchain adjustment.

[chris@…]

Fixed in r2015.