Opened 8 years ago

Closed 7 years ago

Last modified 7 years ago

#3563 closed task (wontfix)

gcc build instructions have syntax error

Reported by: miland Owned by: lfs-book@…
Priority: normal Milestone: 7.6
Component: Book Version: SVN
Severity: normal Keywords:


on page:

an option is given like --disable-libstdc++v3

it should be --disable-libstdcxx

Change History (5)

comment:1 by bdubbs@…, 8 years ago

You are right, but it doesn't seem to hurt anything and we build gcc again 4 packages later. Will fix in svn though.

comment:2 by Pierre Labastie, 8 years ago

Please test before changing it: last time I tried to use --disable-libstdcxx, I got an error when running make. --disable-libstdc++v3 gives no error. Will investigate more so that we know what to answer to this ticket...

comment:3 by Pierre Labastie, 8 years ago

I think there is an error in configure:

# Check whether --enable-libstdcxx was given.
if test "${enable_libstdcxx+set}" = set; then :
  enableval=$enable_libstdcxx; ENABLE_LIBSTDCXX=$enableval

if test "${ENABLE_LIBSTDCXX}" = "no" ; then
  noconfigdirs="$noconfigdirs libstdc++-v3"

but everywhere else, the configdir is referenced as target-libstdc++-v3.

Applying the sed:

sed -i -e 's/\(dirs\) \(libstdc\)/\1 target-\2/' configure

and changing --disable-libstdc++-v3 to disable-libstdcxx generates exactly the same Makefiles (apart from the configargs variables) as when using --disable-libstdc++-v3 and no sed.

Will report upstream. Meanwhile, I guess it is OK to use the current switches for gcc-pass1.

comment:4 by bdubbs@…, 7 years ago

Resolution: wontfix
Status: newclosed

We could do:

sed -i -r 's/(disable-libstdc)xx/\1++-v3/' configure

as that just changes the --help output, but we won't do that. We'll just leave things as they are.

comment:5 by Pierre Labastie, 7 years ago

Note: See TracTickets for help on using tickets.