hi all,
does anyone knows any issue compiling an XFS kernel with gcc 3.2 ?
This is what i got on my Slackware:
make[4]: Entering directory `/usr/src/2.4.19-xfs/fs/xfs/pagebuf'
gcc -D__KERNEL__ -I/usr/src/2.4.19-xfs/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O3 -mcpu=i686
-fexpensive-optimizations -funroll-loops -frerun-cse-after-loop
-frerun-loop-opt -fno-strict-aliasing -fno-common -fomit-frame-pointer
-pipe -mpreferred-stack-boundary=2 -march=i686 -I.. -nostdinc -I
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/include
-DKBUILD_BASENAME=page_buf -DEXPORT_SYMTAB -c page_buf.c
gcc -D__KERNEL__ -I/usr/src/2.4.19-xfs/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O3 -mcpu=i686 -march=i686
-fexpensive-optimizations -funroll-loops -frerun-cse-after-loop
-frerun-loop-opt -fno-strict-aliasing -fno-common -fomit-frame-pointer
-pipe -mpreferred-stack-boundary=2 -march=i686 -I.. -nostdinc -I
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/include
-DKBUILD_BASENAME=page_buf_io -c -o page_buf_io.o page_buf_io.c
gcc -D__KERNEL__ -I/usr/src/2.4.19-xfs/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O3 -mcpu=i686 -march=i686
-fexpensive-optimizations -funroll-loops -frerun-cse-after-loop
-frerun-loop-opt -fno-strict-aliasing -fno-common -fomit-frame-pointer
-pipe -mpreferred-stack-boundary=2 -march=i686 -I.. -nostdinc -I
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/include
-DKBUILD_BASENAME=page_buf_locking -c -o page_buf_locking.o
page_buf_locking.c
{standard input}: Assembler messages:
{standard input}:148: Error: suffix or operands invalid for `bsf'
make[4]: *** [page_buf_locking.o] Error 1
make[4]: Leaving directory `/usr/src/2.4.19-xfs/fs/xfs/pagebuf'
make[3]: *** [first_rule] Error 2
make[3]: Leaving directory `/usr/src/2.4.19-xfs/fs/xfs/pagebuf'
make[2]: *** [_subdir_pagebuf] Error 2
make[2]: Leaving directory `/usr/src/2.4.19-xfs/fs/xfs'
make[1]: *** [_subdir_xfs] Error 2
make[1]: Leaving directory `/usr/src/2.4.19-xfs/fs'
make: *** [_dir_fs] Error 2
Compiling back with the 2.95.3 gcc gave no problem...
Is a compiler issue?
Stefano Sartini.
|