xfs
[Top] [All Lists]

Re: gcc 3.2

To: stefano sartini <stefano.sartini@xxxxxxxxx>
Subject: Re: gcc 3.2
From: Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Date: 01 Sep 2002 16:46:56 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <3D6E233B.4090209@inwind.it>
Organization: Coremetrics, Inc.
References: <3D6E233B.4090209@inwind.it>
Sender: linux-xfs-bounce@xxxxxxxxxxx
I used 3.2 recently to compile 2.4.19-RC5-aa1. No problems there.

On Thu, 2002-08-29 at 08:35, stefano sartini wrote:
> 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.
> 
-- 
Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Coremetrics, Inc.

-- Attached file included as plaintext by Ecartis --
-- File: signature.asc
-- Desc: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA9corQ94g6ZVmFMoIRAlzBAJ9WpBVG/8gIT75QgivfEY2dMvD5TwCgyHoR
u7zrQaKaCM4pjXgzMmkT6/c=
=j5/s
-----END PGP SIGNATURE-----



<Prev in Thread] Current Thread [Next in Thread>
  • Re: gcc 3.2, Austin Gonyou <=