This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
>> Well, it's good to know I'm not the only person having trouble with >> this. Someone "helpfully" added a mis-feature to the linker for MIPS >> that says the architectures have to match - mips1 and mips2 can be >> linked together, and mips3 and mips4, but not other combinations. >> This is IMHO complete nonsense in an architecture where the >> binary code is upwards compatible. I'm not sure exactly when this got >> added, but it was somewhere in between 2.6 (my old version, where it >> did not complain) and 2.9.1, which I use now. Luckily I still have >> the old ld program around, and I use it whenever I have to explicitly >> mix architectures. Thanks for the input. My real problem is before I get to ld. Something in gas or bfd causes the object file to either be wrong or have the wrong header info. At least I think this is what is happening. If the object file were ok then objdump would tell me the architecture was mips:4000. What I ended up doing (on a lark) was going back to binutils-2.8.1 and happily it works the way it used too. I guess the important thing to note here is keep those old binutils around. You never know when you might need them. Thanks again, - Joel _______________________________________________ New CrossGCC FAQ: http://www.objsw.com/CrossGCC _______________________________________________ To remove yourself from the crossgcc list, send mail to crossgcc-request@cygnus.com with the text 'unsubscribe' (without the quotes) in the body of the message.