Error when tuning the toolchain

Chris Staub chris at
Mon Oct 26 09:13:44 PDT 2009

On 10/26/2009 12:00 PM, Simone Dalmasso wrote:
> Ok, thank you. I've rebuilt all but at the same point when I type:
> gcc -dumpspecs | sed 's@^/lib/' \
>  > `dirname $(gcc -print-libgcc-file-name)`/specs
> I get no such file or directoy.

Usually this means that you've forgotten to type the ">" in the command.

  If I create an empty file called 'specs'
> it doesn't raises errors yet but the specs file remains empty and the ne
> next command:
> GCC_INCLUDEDIR=`dirname $(gcc -print-libgcc-file-name)`/include &&
> find ${GCC_INCLUDEDIR}/* -maxdepth 0 -xtype d -exec rm -rvf '{}' \; &&
> rm -vf `grep -l "DO NOT EDIT THIS FILE" ${GCC_INCLUDEDIR}/*` &&
> gcc: unrecognized option '-mtune=pentiumpro'
> and a list of removed...

Yeah, that's simply a result of the previous specs file problem.
> Testing the cc with the dummy. c file I don't get nothing, the prompt
> remains blinking and I nedd to interrupt it.

...and there's no point in testing dummy.c if the specs file is blank.

More information about the lfs-support mailing list