public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Buddy Lott" <buddy_lott@hotmail.com>
To: <gcc-help@gcc.gnu.org>
Subject: Cross-compiling ....
Date: Mon, 19 Aug 2002 11:25:00 -0000	[thread overview]
Message-ID: <583E84A77A2FCB4F967E6CD9B0CA4AF71BD265@nt-server.kreuter> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2969 bytes --]

At the risk of being flamed out of existence ..

 

I am trying to build a cross-compiler that goes from a pc running
windows 2000 to an embedded Motorola 68360 processor. I have failed in
so many ways so far that I am about ready to give up.

 

Here are things I have tried:

 

1)       Dos configure/compile .. Did not work . this was expected.

2)       Dos compile using bash shell.. Did not work (out of memory)
this was expected

3)       Cygwin compile . DID not work . this was NOT expected .. I hit
several problems ..

a.       Most recently compile errors with function.c

 

gcc -c -DCROSS_COMPILE -DIN_GCC   -DDONT_HAVE_STDIO -DDONT_HAVE_SETJMP
-Dinhibi

t_libc  -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes

 -Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H    -I. -I. -I.
-I./. -I

./config -I./../include function.c -o function.o

function.c: In function `instantiate_decls':

function.c:3581: warning: comparison between signed and unsigned

function.c: In function `expand_function_end':

function.c:6982: `USE_RETURN_INSN' undeclared (first use in this
function)

function.c:6982: (Each undeclared identifier is reported only once

function.c:6982: for each function it appears in.)

function.c: In function `thread_prologue_and_epilogue_insns':

function.c:7225: `USE_RETURN_INSN' undeclared (first use in this
function)

make[1]: *** [function.o] Error 1

make[1]: Leaving directory `/home/Administrator/gcc-3.0.4/gcc'

make: *** [all-gcc] Error 2

 

b.       Precious bad option

 

/home/Administrator/gcc-3.0.4/gcc/xgcc
-B/home/Administrator/gcc-3.0.4/gcc/ -B/u

sr/local/m68k-elf/bin/ -B/usr/local/m68k-elf/lib/ -isystem
/usr/local/m68k-elf/i

nclude -DCROSS_COMPILE -DIN_GCC    -W -Wall -Wwrite-strings
-Wstrict-prototypes

-Wmissing-prototypes -isystem ./include  -I. -I. -I. -I./. -I./config
-I./../inc

lude  -g0 \

  -finhibit-size-directive -fno-inline-functions \

  -fno-exceptions  -Dinhibit_libc \

  -c ./crtstuff.c -DCRT_BEGIN -o crtbegin.o

as: unrecognized option `-mc68020'

make[1]: *** [crtbegin.o] Error 1

make[1]: Leaving directory `/home/Administrator/gcc-3.0.4/gcc'

make: *** [all-gcc] Error 2

 

 

 

I have tried various "targets" (m68k-coff, m68k-elf, mcore-elf).  I am
working on getting a linux box going to see if I have any better luck
there  (I don't expect to).

 

So here are my questions/goals:

 

1)       Where is some good upto date documentation (either online or in
book) on how to use the Gnu compiler suite in an embedded system or at
least as a cross-compiler? I need to be able to build the compiler
(hopefully for many different targets) and do all the other fun things
like specifying the memory layout.

2)       If there is not an answer to #1, then can anyone tell me how to
solve the problems I am having above. I have looked (probably in all the
wrong places) and tried to find the information I need to no avail. 

 

Thanks,

 

 

 

Buddy Lott

 


[-- Attachment #1.2: Type: text/html, Size: 14231 bytes --]

[-- Attachment #2: Buddy Lott.vcf --]
[-- Type: text/x-vcard, Size: 129 bytes --]

BEGIN:VCARD
VERSION:2.1
N:Lott;Buddy
FN:Buddy Lott
EMAIL;PREF;INTERNET:BuddyLott@kmc-controls.com
REV:20020613T135616Z
END:VCARD

             reply	other threads:[~2002-08-19 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19 11:25 Buddy Lott [this message]
2002-08-19 15:52 ` Cross-compiling Andrea Bocci
2002-08-21  7:18   ` Cross-compiling Buddy Lott

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=583E84A77A2FCB4F967E6CD9B0CA4AF71BD265@nt-server.kreuter \
    --to=buddy_lott@hotmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).