Error: unknown pseudo-op: `.section'

[LLeweLLyn Reese]

Robert Millan <zeratul2@wanadoo.es> writes:

> hi!
> 
> I'm getting this error when compiling GCC 3.2.1 under NetBSD. Note that
> this only happens when crosscompiling, otherwise the build works fine.
> I'm not sure if the problem is in GAS or in GCC's CRT stuff, so i'm posting
> to both bug-binutils and gcc-help.

You might have better luck on the crossgcc mailing list:
http://sources.redhat.com/ml/crossgcc/

> 
> The host system has GCC 3.2.1 either, and a recent binutils CVS snapshot
> (20030607).
> 
> Error log follows:
> 
> /home/rmh/toolchain/build-gcc/gcc/xgcc -B/home/rmh/toolchain/build-gcc/gcc/ -B/gnu/toolchain//i386-netbsd-gnu/bin/ -B/gnu/toolchain//i386-netbsd-gnu/lib/ -isystem /gnu/toolchain//i386-netbsd-gnu/include -O2 -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include
> -I. -I. -I../../gcc-3.2.1/gcc -I../../gcc-3.2.1/gcc/. -I../../gcc-3.2.1/gcc/config -I../../gcc-3.2.1/gcc/../include  -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions  \
>   -Dinhibit_libc -c ../../gcc-3.2.1/gcc/crtstuff.c -DCRT_BEGIN \
>   -o crtbegin.o
> /var/tmp//ccd9VWeZ.s: Assembler messages:
> /var/tmp//ccd9VWeZ.s:2: Error: unknown pseudo-op: `.section'
> /var/tmp//ccd9VWeZ.s:7: Error: unknown pseudo-op: `.section'
> /var/tmp//ccd9VWeZ.s:12: Error: unknown pseudo-op: `.section'
> /var/tmp//ccd9VWeZ.s:16: Error: unknown pseudo-op: `.section'
> /var/tmp//ccd9VWeZ.s:30: Error: unknown pseudo-op: `.local'
> /var/tmp//ccd9VWeZ.s:31: Warning: rest of line ignored; first ignored character
> is `,'
> /var/tmp//ccd9VWeZ.s:68: Error: unknown pseudo-op: `.section'
> /var/tmp//ccd9VWeZ.s:72: Error: unknown pseudo-op: `.local'
> /var/tmp//ccd9VWeZ.s:73: Warning: rest of line ignored; first ignored character
> is `,'
> /var/tmp//ccd9VWeZ.s:103: Error: unknown pseudo-op: `.section'
> make[1]: *** [crtbegin.o] Error 1
> make[1]: Leaving directory `/home/rmh/toolchain/build-gcc/gcc'
> make: *** [all-gcc] Error 2
> 
> 
> Doing some search i found this message [1] which seems to indicate there
> was a bug in binutils that could cause this, but that's suposed to be
> fixed now as the bug dates on 23 Mar 1998.
> 
> [1] http://sources.redhat.com/ml/bfd/1998/msg00024.html
[snip]