From: Tom Rini <trini@kernel.crashing.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Makefile check for older binutils broken?
Date: Fri, 28 Oct 2005 09:10:54 -0700 [thread overview]
Message-ID: <20051028161054.GB22245@smtp.west.cox.net> (raw)
In-Reply-To: <20051028085224.GA17520@logos.cnet>
On Fri, Oct 28, 2005 at 06:52:24AM -0200, Marcelo Tosatti wrote:
> On Wed, Oct 26, 2005 at 03:02:05PM -0700, Tom Rini wrote:
> > On Wed, Oct 26, 2005 at 11:36:48AM -0200, Marcelo Tosatti wrote:
> > >
> > > Hi,
> > >
> > > While trying to compile 2.6.14-rc4 on my Pegasos (running Debian unstable):
> > >
> > > make[2]: Entering directory `/home/marcelo/8xx/linux-2.6.14-rc4'
> > > *** 2.6 kernels no longer build correctly with old versions of binutils.
> > > *** Please upgrade your binutils to 2.12.1 or newer
> > > make[2]: *** [checkbin] Error 1
> >
> > What's your CONFIG_SHELL set to?
>
> bash
>
> >
> > [snip]
> > > marcelo@pegasos:~$ /bin/echo dssall | as -many -o /tmp/output.as >/dev/null 2>&1
> > > marcelo@pegasos:~$ echo $?
> >
> > What about if you run the whole test on shell (if ...), does it work there?
> > What shell are you running?
>
> Yep, that does the trick. Is it good now?
Er, that's odd. I was using writing parens, not shell parens :) Can
you test the failure case here by changing dssall to garbage? Also,
that's not a clean patch, but vs your last one that wasn't valid.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-10-28 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 13:36 Makefile check for older binutils broken? Marcelo Tosatti
2005-10-26 19:59 ` Andreas Schwab
2005-10-26 16:08 ` Marcelo Tosatti
2005-10-26 22:02 ` Tom Rini
2005-10-28 8:52 ` Marcelo Tosatti
2005-10-28 16:10 ` Tom Rini [this message]
2005-10-28 13:14 ` Marcelo Tosatti
2005-11-01 16:33 ` Marcelo Tosatti
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=20051028161054.GB22245@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=marcelo.tosatti@cyclades.com \
/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).