public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Devaughn, Hans" <hans.devaughn@siemens.com>
To: "'Nick Garnett'" <nickg@ecoscentric.com>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] MIPS 5KC Target
Date: Tue, 24 Aug 2004 17:24:00 -0000	[thread overview]
Message-ID: <EA78B62757AF1E4799828249310AC4CA060A44EC@stca206a.bus.sc.rolm.com> (raw)

Nick,

I tried to duplicate your build for both the Atlas and Malta MIPS32 4KCs and
they failed with an error in platform.s. I had just discovered that building
on a NEW directory doesn't cause this error. Using NEW directories I have
successfully built the Atlas and Malta MIPS32 and the Malta MIPS64.
Obviously, as you indicated, there must be residue left on the old directory
that the configtool doesn't clean up.

Thanks
Hans

-----Original Message-----
From: nickg@xl5.calivar.com [mailto:nickg@xl5.calivar.com] On Behalf Of Nick
Garnett
Sent: Tuesday, August 24, 2004 1:17 PM
To: Devaughn, Hans
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] MIPS 5KC Target



Please CC replies to the ecos-discuss list. Direct messages may be ignored.


"Devaughn, Hans" <hans.devaughn@siemens.com> writes:

> Nick,
> 
> Thanks for your speedy reply. I can build both the Atlas and Malta 4KC 
> images and get them to link. Could you look at the makefile for the 
> 5KC from your build. This is what I have for the cache support
> 
> headers: mlt_headers $(PREFIX)/include/cyg/hal/variant.inc
> $(PREFIX)/include/cyg/hal/var_arch.h 
> $(PREFIX)/include/cyg/hal/var_cache.h
> $(PREFIX)/include/cyg/hal/var_intr.h
> 
> and
> 
> $(PREFIX)/include/cyg/hal/var_cache.h:
> $(REPOSITORY)/$(PACKAGE)/include/var_cache.h
> ifeq ($(HOST),CYGWIN)
> 	@mkdir -p `cygpath -w "$(dir $@)" | sed "s@\\\\\\\\@/@g"` else
> 	@mkdir -p $(dir $@)
> endif
> 	@cp $< $@
> 	@chmod u+w $@
>

There doesn't seem to be anything wrong here.


> It is the $(PREFIX)/include/cyg/hal/var_cache.h header file that kicks 
> the error out. The $(REPOSITORY)/$(PACKAGE)/include/var_cache.h file 
> is the one that supports the MIPS64.

So, let me get this right. Although
$(REPOSITORY)/$(PACKAGE)/include/var_cache.h
points to the correct file, somehow you are getting the mips32 version of
the file instead? That does not make any sense.

What does the $(PACKAGE) variable contain? It should be
"hal/mips/mips64/current".

Are you configuring in a fresh directory? Trying to move an existing
configuration from one target to another sometimes leaves remnants of the
old configuration around.

> 
> I am using John's latest version of configtool (version 2.net, June 
> 23, 2004 which I downloaded from the Ecoscentric web site). I am using 
> the mipsisa-32 gnutools, version 3.2.1, prebuilt. I have not used 
> ecosconfig, but have the John's latest version also.

Try using ecosconfig. The following commands are what I used to test with:

$ mkdir atlas5kc.ram.kernel
$ cd atlas5kc.ram.kernel
$ ecosconfig new atlas_mips64_5kc kernel
$ ecosconfig tree
$ make

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2004-08-24 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 17:24 Devaughn, Hans [this message]
     [not found] <EA78B62757AF1E4799828249310AC4CA060A44EB@stca206a.bus.sc.rolm.com>
2004-08-24 17:16 ` Nick Garnett
  -- strict thread matches above, loose matches on Subject: below --
2004-08-24 14:32 Devaughn, Hans
2004-08-24 16:07 ` Nick Garnett

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=EA78B62757AF1E4799828249310AC4CA060A44EC@stca206a.bus.sc.rolm.com \
    --to=hans.devaughn@siemens.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=nickg@ecoscentric.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).