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] |
Mark Palmerino wrote: > > Thanks, Kai, for the suggestions. Here is the result of one of your > suggestions: You are welcome. > > Why the 'm68k-coff-gcc' alone didn't work will be solved using the command > > > > m68k-coff-gcc -print-search-dirs > > > > Ok, here is what I get with the above command: > > m68k-coff-gcc -print-search-dirs > install: /usr/local/lib/gcc-lib/m68k-unknown-coff/2.8.1/ > programs: > /usr/local/lib/gcc-lib/m68k-unknown-coff/2.8.1/ > <snip> > /usr/local/m68k-unknown-coff/bin/ > libraries: > /usr/local/lib/gcc-lib/m68k-unknown-coff/2.8.1/ > <snip> > /usr/local/m68k-unknown-coff/lib/ > > It looks to me like the problem is that the program is looking for > "m68k-unknown-coff" rather than "m68k-coff" - am I reading the above > correctly? Yes... > If so, does this suggest a recompile? And, if so, why did > '--target=m68k-coff' get transformed into 'm68k-unknown-coff' and what > should I do about it? This seems to be some kind of bug. The $target in '--target=$target' should appear as 'target_alias' in the resulted Makefile, not the 'full name' generated by 'config.sub' or something. Anyway this bug hasn't been seen in the recent GCCs... Ok, you can edit the Makefile, remove the '-unknown' from the 'target' and 'target_alias' definitions, then remove the 'cccp.o', 'gcc.o', 'g++.o', '*protoize.o', 'prefix.o' and 'toplev.o', I think these could be influenced by the 'target_alias' or 'target' name. The 'make' and 'make install' again and remove all the old installed 'm68k-unknown-coff' stuff... Weird is also that the 'm68k-coff-*' executables were with the right prefix, not with the 'm68k-unknown-coff-*' names... > I suppose an alternative is to rename all the 'm68k-coff' directories to > 'm68k-unknown-coff', but this feels like a kludge to me. > > Any suggestions? There are only two used, shown in the 'snipped' output from '-print-search-dirs', and the binutils and newlib installs use only the second so perhaps just making a symlink from the '/usr/local/m68k-coff to the '/usr/local/m68k-unknown-coff', will solve the missing binutils, libs and headers problem. The binutils and newlib installs used the right target name quite surely... Cheers, Kai ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |