On Mon, Sep 6, 2010 at 2:54 AM, Cheng Rk <crq...@ymail.com> wrote: > --- On Mon, 6/9/10, Justin P. Mattock <justinmatt...@gmail.com> wrote: >> From: Justin P. Mattock <justinmatt...@gmail.com> >> Subject: Re: on how to compile gcc-4.6 correctly? >> To: "Dennis" <crq...@fedoraproject.org> >> Cc: gcc@gcc.gnu.org, crq...@ymail.com >> Date: Monday, 6 September, 2010, 9:18 AM >> On 09/05/2010 08:17 PM, Dennis > [...] >> hm... an obvious question would be if you have your >> toolchain correct? > > Yes, I think the binutils/gmp/mpfr/mpc all dependencies are correct, > otherwise why I can compile all gcc-4.5.x version correctly? > On the same system, gcc-4.5.x (4.5.0 and 4.5.1 and 4.5-20100902/... multiple > snapshots) all can compile correctly, I install them into separate > directories, and have verified those compilers can compile many source > packages correctly; > >> (but you probably do..(I used this to build >> 4.6.0..:http://cross-lfs.org/view/svn/x86_64-64/)) > > but this still didn't explain what's the "ggc_alloc_cleared_lang_type" macro? > all through gcc source it's only used by gcc/c-decl.c file, but it has no > definition under gcc source header files, nor under /usr/include; > >> >> in your case I see something with lang... maybe your CFLAGS >> are set >> wrong to the wrong machine?! over here my CFLAGS look like >> this: >> CFLAGS="-m64 -mtune=core2 -march=core2 -O2 -pipe >> -fomit-frame-pointer >> -fstack-protector -w" CXXFLAGS="${CFLAGS}" >> MAKEOPTS="{-j3}" > > I didn't use any special CFLAGS, when I try to compile gcc-4.5.x or this > gcc-4.6 snapshot, I just use "../gcc-4.6-20100905/configure > --with-arch-64=athlon64 --with-arch-32=i386", I tried to get a multilib > compiler that could generate default athlon64 optimized code for 64bit and > i386 code for 32bit; > > The same "--with-arch-64=athlon64 --with-arch-32=i386" works well during > compiling gcc-4.5.x but why not work on gcc-4.6 ??? > >> >> keep in mind this is for a intel iMac... your system could >> be diff.. >> >> Justin P. Mattock >> > > Thanks a lot~ > > >
ah... if gcc 4.5.0 builds right, but 4.6.0 does not then everything is good(toolchain).. sounds like your going to have to file a bug with gcc since 4.6.0 is so new.. (keep in mind it's late here so I might have left a few things out..). -- Justin P. Mattock
