This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
David Korn wrote: > > >-----Original Message----- > >From: Kai Ruottu [mailto:kai.ruottu@luukku.com] > >Sent: 07 February 2002 08:15 > > > The 'm68k-coff/elf' don't have a default target board, so the 'specs' and > > maybe the linker script for the added default target board must be > > edited... The link, lib, endfile, startfile and libgcc specs must be > > edited to be sane... Then the 'compiler' should work and the > > 'libiberty'-configure can succeed... > > Ah, so it's the same situation as the ppc-eabi build suffers. Is there > not a single -m flag that can be added to solve this? In Bill's build > script it uses CFLAGS+=-myellowknife (more-or-less) to make this stage > succeed; could it do the same but with some other -m name for the m68k-elf > combination? No, but of course using the '--with-newlib' in configure should tell that scanning the C-library for libiberty is vain -- newlib is a known entity and it is known what is missing from it. I remember this letting all the parts to be built. But knowing what a linker script is, what are startups and so on, must be learned at some time... Just like a car builder should know what parts are needed and to know somehow how a car works ;-) So the practice with 'specs' and the provided linker script for some supported board may be useful... Regards, Kai ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |