From: Stefan Jeglinski <jeglin@4pi.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.6 hoses 2.4 on old-world?
Date: Sun, 22 Aug 2004 20:54:07 -0400 [thread overview]
Message-ID: <p06100201bd4eeaa40658@[192.168.0.23]> (raw)
In-Reply-To: <20040821225118.GB18858@suse.de>
Olaf Hering:
>the binutils check (?) will remove /dev/null
Well, I found your earlier thread on binutils and the discussion of
the -many switch, but I'm not clear as to what this is all about. It
looks like my problem is two-fold:
1. To build 2.6.x, I need a newer binutils than my 2.13.90.0.18-6 (YDL 301)
2. The as check fails to tell me my binutils is too old (?)
Is this correct? Since I don't see the error, what version of
binutils do I need? Just the "latest?" Not having done so yet, will I
have to upgrade various other things as well? (gcc, etc).
Sam Ravnborg:
>Yep - Tom Rini already notified me about this issue.
>Problem is the way as handle output files.
I think this is the same thread I was talking about. What I'm really
unclear on is the "correct" way to handle this. It seems like the
discussion about changing AFLAGS is still alive? Also from the
earlier thread, it seems like maybe the latest binutils will not
necessarily fix the issue, as something has changed in binutils?
Sorry to be such a newbie on this. I'm obviously 2-3 months behind
the discussion, just now delving into 2.6...
Stefan Jeglinski
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-08-23 0:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 1:04 2.6 hoses 2.4 on old-world? Stefan Jeglinski
2004-08-21 1:41 ` CaT
2004-08-21 2:05 ` Stefan Jeglinski
2004-08-21 2:18 ` Stefan Jeglinski
2004-08-21 22:51 ` Olaf Hering
2004-08-22 8:57 ` Sam Ravnborg
2004-08-23 0:54 ` Stefan Jeglinski [this message]
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='p06100201bd4eeaa40658@[192.168.0.23]' \
--to=jeglin@4pi.com \
--cc=linuxppc-dev@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).