On Tue, Feb 26, 2013 at 05:52:36PM +0100, Andrey Gursky wrote: > Hi James, > > >The kbuild NMU, which migrated on Jan. 12th, seems to have exposed a bug > >in kmk_sed which is affecting the virtualbox build. I've tried > >rebuilding kbuild with Wheezy's gcc-4.6, since upstream indicates this > >is a gcc-4.7-specific problem, but that didn't make a difference. > > > >Reassigning to kbuild. > > How did you specify the 4.6? Doing that a straightforward way fails > for some reason. Would be nice if it could be also investigated.
If I recall correctly, I used sbuild. Something along the line of
$ echo '$build_environment = { CC => 'gcc-4.6' };' >> ~/.sbuildrc
$ sbuild --add-depends gcc-4.6 -sA -c wheezy -d wheezy
kbuild_0.1.9998svn2543+dfsg-0.1.dsc
with the appropriate chroot already setup.
> Global switching gcc to gcc-4.6 with attached scripts did the job
> well. kbuild can be compiled even with -O3 and it works. Do you know,
> whether this bug with a kbuild/virtualbox as test case is already
> reported to gcc?
According to upstream sed, this isn't a GCC problem. kBuild just hasn't
updated to a more recent version of sed which already fixed this
problem.
Cheers,
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <james...@debian.org>
signature.asc
Description: Digital signature
