public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Atsumi Hirose <atsumi99@yahoo.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] building gcc-2.95.1 for eCos 1.2.1
Date: Tue, 02 Nov 1999 04:02:00 -0000	[thread overview]
Message-ID: <19991102120207.12684.rocketmail@web1701.mail.yahoo.com> (raw)

Hi all,

I want to use gcj with ecos on an ARM processor and it
is turning out to be MUCH more difficult than
anticipated.  I though that all I would have to do is
build gcc-2.95.1 as an arm-linux cross compiler and
then configure/build the compiler for java and build
the java library.  After that I thought I could just
copy the java libraries into the kernel and then play
around with some headers and include files.  I have
thus learned that I was wrong and was wondering if
somebody could tell me just what is involved when
trying to get gcj to run with eCos.  Has anybody been
able to do this?

For starters let me say that I cannot even get the
gcc-2.95.1 arm-linux cross compiler that I built to
run on my ARM board with eCos (C or C++).  Of course
the arm-linux cross compiler that comes with eCos
works just fine.  I can compile a file with my new
2.95.1 toolchain.  It just won't run on the board.  I
can give a bunch of details on some "errors" that I
get but that might not even be relavant.  I have tried
many different methods (ie swithing eCos's and
gcc-2.95.1's header files etc.) but nothing works.

As you can tell, I am not to experienced at developing
GNU tools.  I just imagined that if a file was
compiled successfully for my ARM board, I could use
the other tools in eCos, gdb, the libs and header
files, etc. . . to load the file into the board. 
Ofcourse I would obviously have to change out some
headers and libarary files.  I guess I am just
learning the hard way what it means to "port"
something to eCos.  Just what does that mean?

Anyway, I am grateful for any comments or suggestions.

Atsumi


=====

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

             reply	other threads:[~1999-11-02  4:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-02  4:02 Atsumi Hirose [this message]
1999-11-02  5:48 ` Grant Edwards
1999-11-03 18:58 Atsumi Hirose
1999-11-04  6:44 ` Grant Edwards
1999-11-04 10:21   ` Grant Edwards
1999-11-04 20:57 Atsumi Hirose
1999-11-05  5:42 ` Jonathan Larmour
1999-11-05  6:08 ` Grant Edwards

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=19991102120207.12684.rocketmail@web1701.mail.yahoo.com \
    --to=atsumi99@yahoo.com \
    --cc=ecos-discuss@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).