From: Erik Christiansen <erik@dd.nec.com.au>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Is it binutils-2.13.90.0.4 or is it me?
Date: Wed, 2 Oct 2002 11:03:21 +1000 [thread overview]
Message-ID: <20021002010320.GA601@dd.nec.com.au> (raw)
Following the mini-howto on penguinppc.org, I started with compilation
of binutils.
./configure --target=powerpc-linux finished in a happy frame of mind,
but make spat the dummy, flagging errors on some rather elusive
scripting:
cd .. \
&& CONFIG_FILES=po/Makefile.in:po/Make-in \
CONFIG_HEADERS= /bin/sh ./config.status
creating po/Makefile.in
make[3]: Leaving directory `/usr/local/src/binutils-2.13.90.0.4/bfd/po'
make[3]: Entering directory `/usr/local/src/binutils-2.13.90.0.4/bfd/po'
file=./`echo sv | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH no -o $file sv.po
/bin/sh: no: command not found
make[3]: *** [sv.gmo] Error 127
make[3]: Leaving directory `/usr/local/src/binutils-2.13.90.0.4/bfd/po'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/local/src/binutils-2.13.90.0.4/bfd'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/usr/local/src/binutils-2.13.90.0.4/bfd'
make: *** [all-bfd] Error 2
Now, grep -r 'no -o' /usr/local/src/binutils-2.13.90.0.4/bfd/po draws
a blank, so before looking further for where it could be fixed, I
thought I'd ask whether going back a version or two might provide
smoother sailing?
Regards,
Erik
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-10-02 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 1:03 Erik Christiansen [this message]
2002-10-02 6:02 ` Is it binutils-2.13.90.0.4 or is it me? Erik Christiansen
2002-10-02 14:54 ` Hollis Blanchard
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 9:09 Milton D. Miller II
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021002010320.GA601@dd.nec.com.au \
--to=erik@dd.nec.com.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).