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] |
On Wed, 27 Oct 2004, Peter Barada wrote: > checking version of ld... 2.11.93.0.2, bad > checking for pwd... /bin/pwd > checking for m68k-unknown-linux-gnu-gcc... (cached) gcc > checking version of gcc... 3.3, ok > checking for gnumake... no > checking for gmake... gmake > checking version of gmake... 3.79.1, ok > checking for gnumsgfmt... no > checking for gmsgfmt... no > checking for msgfmt... msgfmt > checking version of msgfmt... 0.11.1, ok > checking for makeinfo... makeinfo > checking version of makeinfo... 4.1, ok > checking for sed... sed > checking version of sed... 3.02, ok > checking for autoconf... autoconf > checking whether autoconf works... no > configure: error: > *** These critical programs are missing or too old: as ld > *** Check the INSTALL file for required versions. > > > Any suggestions on how to proceed get around this error? > > I'm wondering if I need to create a new native binutils and put that > in my path(as well as the compiler), and *then* attempt to run > crosstool... When you build binutils for a cross-platform, you get two copies of the binaries, such as m68k-elf-as and as. Set your path to look at the m68k version of as before it gets to the native version. $prefix/m68k-elf/bin:...:/usr/bin This is the quickest way around this issue. Regards, Faisal ------ 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] |