Opened 21 years ago

Closed 21 years ago

Last modified 21 years ago

#473 closed defect (invalid)

Chapter 5: Textutils, Findutils, Gawk, Patch, Sed, Textutils Configure Command

Reported by: isaac_j@… Owned by: lfs-book@…
Priority: high Milestone:
Component: Book Version: CVS
Severity: normal Keywords:
Cc:

Description

In chapter 5 Textutils, Findutils, Gawk, Patch, Textutils and Sed produce the error LDFLAGS="-static": Unknown Command, when using the configure command provided in the latest online cvs (www.linuxfromscratch.org/view/cvs) instead of using this method to get it to compile you have to include the LDFLAGS in the make command as in version 4 of the book or rewrite the configure command. Minor but would be annoying for a linux newbie who might not know how to fix it.

Change History (4)

comment:1 by jbrown@…, 21 years ago

works fine here using the commands from the book.

comment:2 by isaac_j@…, 21 years ago

I don't claim to be a linux guru but the following is true to a word, maybe I am doing something wrong?

This is the exact command used in the online cvs to make Gawk-3.1.1:

"CPPFLAGS=-Dre_max_failures=re_max_failures2 \LDFLAGS="-static" ./configure -- prefix=$LFS/static --disable-nls && make && make install"

On Redhat 6.1, Redhat 8 and a Knoppix 3.1 bootable CD this produces the following output:

"bash: LDFLAGS=-static: command not found" - This is the exact output, initial comment said unknown command as I was working from memory at the time opps!

Using the following fixes this for me:

"CPPFLAGS=-Dre_max_failures=re_max_failures2 \./configure -- prefix=$LFS/static --disable-nls && make LDFLAGS="-static" && make install"

comment:3 by tushar@…, 21 years ago

Did you cut and paste from the book or did you type out the commands? if you did type out, the \ at the end of the line indicates that the command continues in the next line.

BTW, for future reference, it would good to post to the lfs-support list/group to figure out whether it really is a bug. You will get more responses there.

comment:4 by gerard@…, 21 years ago

Resolution: invalid
Status: newclosed

I'm marking this as INVALID. This problem rarely shows up, and when it does it's been attributed to user error. Maybe the odd very old distribution can't work with the construction (bash-1.x might be a likely candidate) but such old distributions are rarely used anymore.

Note: See TracTickets for help on using tickets.