This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
> -----Original Message----- > From: Hans - Dulimarta [SMTP:dulimart@egr.msu.edu] > Sent: Thursday, February 10, 2000 10:27 AM > To: Freier, Rodney J @ CSW-SLC > Cc: crossgcc@sourceware.cygnus.com > Subject: Re: GCC 2.8.1 and binutils for i960-wrs-vxworks > > On Thu, 10 Feb 2000 rfreier@csw.L-3com.com wrote: > > > Date: Thu, 10 Feb 2000 08:23:01 -0700 > > From: rfreier@csw.L-3com.com > > To: crossgcc@sourceware.cygnus.com > > Subject: GCC 2.8.1 and binutils for i960-wrs-vxworks > > > > > > I've been trying to build GCC 2.8.1 for > > X-wrs-vxworks, where X = {powerpc,m68k,i386,mips,i960}. > > > > I used binutils 2.9.5.0.24, and so far, the ppc, m68k, and i386 > > compilers are working. However, I couldn't get the > > 2.9.5.0.24 binutils to build for i960-wrs-vxworks. So, > > I tried 2.9.1. Although the resulting i960 compiler > > seems to compile lots of code correctly, it has consitently > > given me the following error on a specific C++ library: > > > > /var/tmp/ccKkaybm.s: Assembler messages: > > /var/tmp/ccKkaybm.s:3837: Error: Unknown pseudo-op: `.section' > > /var/tmp/ccKkaybm.s:3851: Error: Unknown pseudo-op: `.section' > > > > Am I correct in assuming that the 2.8.1 compiler is simply producing > > instructions that the 2.9.1 assembler doesn't understand? I've > > tried binutils versions 2.6, 2.9.1, 2.9.5.0.24, and 2.9.5.0.27, and > > the first two produce the above error, and the last two won't > > build for this target. (The build process dies because, for this > target, > > the code is logically broken: someone replaced a macro with > > a function and invalidated some of the code which used the macro.) > > > > Any ideas? > > > > From what I learned in the past, usually this happens when the HOST > assembler was accidentally called to assemble the TARGET assembly files. A > quick fix [which works for me :-)] is to make sure that the TARGET > assembler (the cross assembler) is reachable from your PATH. And maybe you > have to rerun the configure script afterwards. > > > [Freier, Rodney J @ CSW-SLC] > No, I made sure the binutils were in the path. > I also used -v in the compile. It gave me the > exact path to the assembler it was using, and it was correct. > I also checked as --version, and it gave the correct target > (i.e. i960-wrs-vxworks). > > -- > Hans Dulimarta, Ph.D. dulimart@[egr.msu.edu, computer.org] > http://www.egr.msu.edu/~dulimart > Visiting Research Associate, Electrical & Computer Engineering > Michigan State University, East Lansing, MI 48824, (517) 432-7589 ------ 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] |