From mboxrd@z Thu Jan 1 00:00:00 1970 From: Atsumi Hirose 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 Message-id: <19991102120207.12684.rocketmail@web1701.mail.yahoo.com> X-SW-Source: 1999-11/msg00004.html 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