From: Johannes Stezenbach <js@convergence.de>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Adrian.Hulse@taec.toshiba.com, linux-mips@oss.sgi.com
Subject: Re: Tools issue
Date: Fri, 15 Feb 2002 16:27:37 +0100 [thread overview]
Message-ID: <20020215152737.GA8809@convergence.de> (raw)
In-Reply-To: <20020215034958.C21011@dea.linux-mips.net>
On Fri, Feb 15, 2002 at 03:49:58AM +0100, Ralf Baechle wrote:
> On Thu, Feb 14, 2002 at 01:42:31PM -0800, Adrian.Hulse@taec.toshiba.com wrote:
>
> > int-handler.s:59: Error: missing ')'
> > int-handler.s:59: Error: illegal operands `lui'
> > int-handler.s:60: Error: missing ')'
> > int-handler.s:60: Error: illegal operands `sb'
> > make[1]: *** [ int-handler.o ] Error 1
...
> > int-handler.S
> > <l59> lui t1, %hi(TSDB_LED_ADDR)
> > <l60> sb t0, %lo(TSDB_LDE_ADDR)(t1)
> >
> > Failed define :
> > #define TSDB_LED_ADDR (KSEG1 + TSDB_LB_PCU_APERTURE + 0x05100020)
> >
> > Compilable define :
> > #define TSDB_LED_ADDR KSEG1 + TSDB_LB_PCU_APERTURE + 0x05100020
...
> > Anyone else seen anything like this and know of a solution to the problem ?
> > Or to paraphrase Dominic Sweetman, maybe i should just stay with the "pick
> > your own version folklore" method of picking tools :).
I had a similar problem with binutils-2.11.92.0.12.3, but
Thiemo Seufer posted a patch on the binutils mailing list.
Should be fixed in binutils CVS.
It seems that it worked with the binutils-2.10.91.0.2 recommended
here: http://www.junsun.net/linux/porting-howto/
> I hope that for binutils we can solve that problem when 2.9.12 gets
> released; as for gcc it seems Maciej's 2.95.3 version is already pretty
> close to what we want. C++ users may disagree ;-) Somewhat longer term
> Algorithmics's toolchain should resolve the situation.
;-)
Regards,
Johannes
prev parent reply other threads:[~2002-02-15 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 21:42 Tools issue Adrian.Hulse
2002-02-15 2:49 ` Ralf Baechle
2002-02-15 15:27 ` Johannes Stezenbach [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=20020215152737.GA8809@convergence.de \
--to=js@convergence.de \
--cc=Adrian.Hulse@taec.toshiba.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.