Compiling binutils -- can you spot the error?
.. lots of waffle, then:
Making all in po
make: Entering directory
file=../.././opcodes/po/`echo pt_BR | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH no -o $file pt_BR.po
/bin/sh: line 1: no: command not found
make: *** [pt_BR.gmo] Error 127
Now, picking on the "no" that throws up the error, can anyone with their
knowledge of bash check the following analysis:
1:- The pt_BR I believe to be some sort of language profile. When I
grepped for it in the binutils source code the hits returned were of
opcodes/config.log:configure:8027: result: fr sv tr es da de id pt_BR ro nl
2:- This: /home/lfs/toolset/sandbox/binutils-2.16.1/
is the directory into which I've put all the binutils source code.
is a subdirectory holding some of the code.
3:- `echo pt_BR | sed 's,.*/,,'`
strips any prefix of the form /directory1/directory2/etc/ from pt_BR
to leave just the filename. Not actually needed in this instance.
4:- As for the .gmo suffix that is then appended, I don't know what that is
but: the opcodes/po/ directory listing is:
Make-in POTFILES da.po es.gmo fr.po
nl.gmo pt_BR.po sv.gmo tr.po Makefile
POTFILES.in de.gmo es.po id.gmo nl.po
ro.gmo sv.po Makefile.in da.gmo
de.po fr.gmo id.po opcodes.pot
So suffixes include .gmo amongst others. Curiously, for every other
language prefix there seems to be both a .po and a .gmo but not for
4:- rm -f $file
Here's code that would remove our .gmo!
5:- PATH=../src:$PATH no -o $file pt_BR.po
here I get lost. What is it doing and why is it breaking at the no?
I feel slightly tempted to think that "no" is the result of a variable
that normally returns an executable such as gcc (but not that). Who
wrote the code? Can they help me?
This is binutils, a core package, so getting the compilation right is
pretty essential, so your help is appreciated!