public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Kai Ruottu <karuottu@freenet.hut.fi>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: "Alexey S. Fadeyev" <alexey@vocord.com>, insight@sourceware.cygnus.com
Subject: Re: Problem with building insight 19991222 Linux RedHat-6.1 -> mips64orionel
Date: Tue, 15 Feb 2000 11:12:00 -0000	[thread overview]
Message-ID: <38A9B748.6A5A5670@freenet.hut.fi> (raw)
In-Reply-To: <38A7E504.E562549E@cygnus.com>

Andrew Cagney wrote:
> 
> "Alexey S. Fadeyev" wrote:
> >
> > Faild to build!
> > make[2] *** No rule to make target `m16.igen' , needed by `tmp-igen'.
> > Stop.
> 
> That's an interesting looking target name - its new on me and know most
> of them :-)

 The 'mips64orionel' is quite ok, a little-endian 'mips64orion' goes
with
that name, like 'mips64orionel-elf'.
 
> It looks like the sim/mips configury is getting confused and thinks it
> needs to build 64 bit MIPS16 target!

 The NEC 'mips64vr4100' target has the MIPS16 capability (VR4111, VR4121
VR4122, VR4181), so a 64 bit MIPS16 target isn't unexpected...

 Ok, back to the original problem, the missing 'm16.igen' can be the
result
of running 'make distclean'... I remember quite well there being a bug
sometimes, the 'sim/mips/Makefile.in' having a row :

	rm -f m32* m16* itable*

instead of the current :

	rm -f m32* itable*

in the file end...

 Fortunately I had a backup for the 'm16.igen' then... Now I couldn't
find any incarnation of that bug anywhere, neither the 'ChangeLog'
mentioned anything about somebody removing it, but perhaps the
insight-19991222 had this bug... although I remember it being there
long time ago...

 But now there is another problem... All my 'mips64*-elf' Insights
built after November 11, 1999 now freeze when the 'src+asm' will be
clicked.  I have a 'mips64vr5000-elf' target one built at Nov. 11, 1999
and it works ok in this respect, but my 'mips64vr4300-elf' (01/05,
2000),
'mips64vr4100-elf' (01/17, 2000) and 'mips64orion-elf' (01/31, 2000)
have
this bug... It happens both in Linux and Win32 hosts and only with the
mips64 targets...

 So the bug was added to the Insight sources sometime between Nov.11,
1999
- Jan. 05, 2000... I will hunt the bug soon, but perhaps someone else
will
succeed earlier...

Cheers, Kai


      reply	other threads:[~2000-02-15 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-19  7:18 Alexey S. Fadeyev
2000-02-14  3:22 ` Andrew Cagney
2000-02-15 11:12   ` Kai Ruottu [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=38A9B748.6A5A5670@freenet.hut.fi \
    --to=karuottu@freenet.hut.fi \
    --cc=ac131313@cygnus.com \
    --cc=alexey@vocord.com \
    --cc=insight@sourceware.cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).