On Wed, Apr 27, 2011 at 5:00 PM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: > Note that as I mentioned earlier combined builds using standard releases > are hard to get right. Subtle errors are possible, though I would not > expect this sort of problem. I personally do not recommend doing a > combined build with anything except a check out of the development > sources. Yes, you are right, my problem was related to that and is solved now after fixing the binutils usage. Thanks again for your quick and great help! (the following details just for the list archives in case someone else has a similar problem) > > ../../../../gcc-4.6.0/libgcc/../gcc/config/arm/lib1funcs.asm: > > Assembler messages: > > ../../../../gcc-4.6.0/libgcc/../gcc/config/arm/lib1funcs.asm:1725: > > Error: unknown pseudo-op: `.syntax' > > ../../../../gcc-4.6.0/libgcc/../gcc/config/arm/lib1funcs.asm:1729: > > Error: bad instruction `lsrs r1,r1,#1' Surely the errors came from wrong building/using binutils in same directory as gcc. I had binutils-2.21 symlinked to gcc-4.6.0 (instead of symlinking all subdirectories from binutils-2.21), which you told me in the reply to my other problem. I think what I actually did is close to "binutils in a separate directory" with the speciality that it is a subdirectory of gcc-4.6.0; recursive configure seems to accept and build it (as it would usually build the subdirectory binutils of the binutils component), because I symlinked binutils-2.21 to binutils (so it build the binutils distribution toplevel instead of the binutils subpackage); the same name may have added a bit to my confusion. I guess the errors were caused because trying a wrong assembler due to my wrong directory structure and configure picking a wrong assembler (however the details looked like, I did not dig into). oki, Steffen
