http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55915
--- Comment #6 from Yves Caniou <yves.can...@ens-lyon.fr> --- (In reply to Yves Caniou from comment #5) > Le mardi 19 novembre 2013 02:36:30 pinskia at gcc dot gnu.org a écrit : > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55915 > > > > Andrew Pinski <pinskia at gcc dot gnu.org> changed: > > > > What |Removed |Added > > ---------------------------------------------------------------------------- > > Status|UNCONFIRMED |WAITING > > Last reconfirmed| |2013-11-19 > > Ever confirmed|0 |1 > > > > --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- > > (In reply to Yves Caniou from comment #3) > > > > > I have the same problem when compiling gcc-4.8.2 with gcc version 4.6.3 > > > (Ubuntu/Linaro 4.6.3-1ubuntu5) on Xeon(R) CPU W3670 @ 3.20GHz > > > Note that with the exact same process, I have been able to compile > > > gcc-4.8.2 with gcc 4.7.2 (debian). > > > > Do you have a zlib.h installed? > > For the original issue here, I think you need to use BOOT_CFLAGS and maybe > > BOOT_CXXFLAGS. > > Indeed: /usr/include/zlib.h > And as I said, I could compile gcc-4.8.2 from 4.7.2 without any problem in > the > first place. Problems only appear when compiling gcc-4.8.2 with the new > installation and all environment variables configured (at least as I > thought: > why would I use BOOT_FLAGS and how?) > > .Y Ok. Wrong machine, I apologize. I have a /usr/lib/syslinux/com32/include/zlib.h from syslinux-common package, not /usr/include/zlib.h from zlib1g-dev. Installing zlib1g-dev does the trick..
