From: Erik Christiansen <erik@dd.nec.com.au>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Is it binutils-2.13.90.0.4 or is it me?
Date: Wed, 2 Oct 2002 16:02:58 +1000 [thread overview]
Message-ID: <20021002060258.GD601@dd.nec.com.au> (raw)
In-Reply-To: <20021002010320.GA601@dd.nec.com.au>
binutils from: ftp://ftp.kernel.org/pub/linux/devel/binutils/.
compiling with gcc 2.95.4 on debian woody.
Oh - Oh, looks like ./config/acinclude.m4 is generating dud makefiles
in the versions: binutils-2.11.93.0.2, binutils-2.12.90.0.9, and
binutils-2.13.90.0.4. (The m4 macro substitution is broken in the same
way in each version.)
I'll send off a bug report, but would meanwhile be grateful if some
wise soul has any hints on sourcing working ingredients for an intel/ppc
cross compiler.
Regards,
Erik
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-02 6:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 1:03 Is it binutils-2.13.90.0.4 or is it me? Erik Christiansen
2002-10-02 6:02 ` Erik Christiansen [this message]
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=20021002060258.GD601@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).