How to generate the LIBGCC.A for mc68000

[Peter Barada]

>I do not know what is to have a "clear understanding of the linux
>environment" .
>What I know is that I am used to configure and recompile the Linux kernel on
>i386 systems for several years.

I should have been more clear.  What I meant is that you need a better
understanding of building embedded linux kerenels and environments.
If you had that, you would have built a m68k-elf compiler instead of
trying to build a m68k-coff compiler, and would have known that you
needed a libc for the 68000 that would link with your test application.

>Since our current hardware is based on mc68LC302 I want to be more familiar
>with embedded Linux by building a kernel for this base. This is only a step.
>This processor has no MMU ( it is derived from mc68000) so I am using for
>this step the ucLinux distribution that I found on the related site.
>This distribution included several ports and on one them is for a mc68EN302
>witch is very near our processor.
>There are also all the tools needed to compile the kernel and build an image
>for this
>target but it is not what I want : I want to control all the steps required
>to build
>an embedded system and not to blindy use a "make" file that produce the
>result without
>understanding what happen during all the steps.

I'm glad that you have found a kernel and toolchain that very closely
matches what you want.  I also understand that you want to 'control'
all the steps necessary to build the toolchain necessary to build the
toolchain.

If you look in
http://www.uclinux.org/pub/uClinux/m68k-elf-tools/gcc-3/ You'll find
all the source(and patches) necessary to build a complete m68k
toolchain that can build uclinux kernels and userland applications for
m68000.  Also from that page, you can find "build-uclinux-tools.sh"
which is a fairly well documented shell script that goes through the
*many* steps necessary to build the toolchain.

>I do not known if it is clear: I appologise I would not want to
>disturb you or be some one rude. My questions were only related on my
>comprehension on the steps required for that.  Now, with the gnu good
>support, I think that the compiler is compliant this the goal I have
>fixed: to be abble to compile the ucLinux kernel with a self-produced
>cross compiler chain.  After that we will check all the points related
>on the bootstrap process but we have already do a lot of thing for the
>other RTOS and we are confident on it.

As I indicated before, these questions are better directed at the
cross-gcc mailing list where you'll find a group of people(myself
included) that use gcc as a cross-compiler for various embedded
targets, some of which have linux on them.

As for 'self-produced cross compiler chain', I suggest you read an
understand the tool building script pointed at above.  You'll be
duplicating those steps to get a toolchain that will do what you want.

Good Luck!

-- 
Peter Barada
peter@the-baradas.com