Red Hat Buildsystem wrote:> Package: kernel-2.6.20-1.3010.fc7 > Tag: dist-fc7 > Status: failed > Built by: davej > ID: 58684 > Started: Thu, 22 Mar 2007 01:48:43 EDT > Finished: Thu, 22 Mar 2007 02:11:24 EDT > Changelog: > * Thu Mar 22 2007 Dave Jones <davej@redhat.com> > - Check source with sparse during build.Very cool. Jon.
On Thu, Mar 22, 2007 at 02:15:17AM -0400, Jon Masters wrote: > Red Hat Buildsystem wrote: > > > Package: kernel-2.6.20-1.3010.fc7 > > Tag: dist-fc7 > > Status: failed > > Built by: davej > > ID: 58684 > > Started: Thu, 22 Mar 2007 01:48:43 EDT > > Finished: Thu, 22 Mar 2007 02:11:24 EDT > > Changelog: > > * Thu Mar 22 2007 Dave Jones <davej@redhat.com> > > - Check source with sparse during build. > > Very cool. Still fighting it. As luck would have it, it''s shaking out bugs in sparse. Seems to blow up horribly on ppc64. Dave -- http://www.codemonkey.org.uk
Dave Jones wrote:> Still fighting it. As luck would have it, it''s shaking out > bugs in sparse. Seems to blow up horribly on ppc64.Why am I not surprised? :-) Maybe I''ll finally get around to posting some kABI build fixes too (one of the guys on an internal list is looking at this and has promised to send fixes, so I haven''t yet) and in the process take a look at this. I don''t use sparse enough. Jon.
On 22.03.2007 07:18, Dave Jones wrote:> On Thu, Mar 22, 2007 at 02:15:17AM -0400, Jon Masters wrote: > > Red Hat Buildsystem wrote: > > > > > Package: kernel-2.6.20-1.3010.fc7 > > > Tag: dist-fc7 > > > Status: failed > > > Built by: davej > > > ID: 58684 > > > Started: Thu, 22 Mar 2007 01:48:43 EDT > > > Finished: Thu, 22 Mar 2007 02:11:24 EDT > > > Changelog: > > > * Thu Mar 22 2007 Dave Jones <davej@redhat.com> > > > - Check source with sparse during build. > > > > Very cool. > > Still fighting it. As luck would have it, it''s shaking out > bugs in sparse. Seems to blow up horribly on ppc64.Just wondering -- why are you downloading sparse in the spec file? Isn''t there a better way to use it? http://cvs.fedora.redhat.com/viewcvs/rpms/kernel/devel/kernel-2.6.spec?view=markup [...] # Download and unpack sparse. %define sparsever 0.2 curl -O http://www.kernel.org/pub/software/devel/sparse/dist/sparse-%{sparsever}.tar.bz2 tar jxf sparse-%{sparsever}.tar.bz2 [...] CU thö
On Thu, Mar 22, 2007 at 07:24:54AM +0100, Thorsten Leemhuis wrote: > Just wondering -- why are you downloading sparse in the spec file? Isn''t > there a better way to use it? fixed in a later commit. After the core+extras merge, it''ll just be a builddep. For now, as extras packages can''t be builddeps in core packages, I''ve included sparse-0.2 in the lookaside cache, just like all the other tarballs. Dave -- http://www.codemonkey.org.uk
On 22.03.2007 07:26, Dave Jones wrote:> On Thu, Mar 22, 2007 at 07:24:54AM +0100, Thorsten Leemhuis wrote: > > > Just wondering -- why are you downloading sparse in the spec file? Isn''t > > there a better way to use it? > fixed in a later commit.Sorry -- I actually looked at the external CVS to make sure it''s still there before posting, but it seems it lags a bit behind the real cvs server. CU thl
Thorsten Leemhuis wrote:> > On 22.03.2007 07:26, Dave Jones wrote: >> On Thu, Mar 22, 2007 at 07:24:54AM +0100, Thorsten Leemhuis wrote: >> >> > Just wondering -- why are you downloading sparse in the spec file? Isn''t >> > there a better way to use it? >> fixed in a later commit. > > Sorry -- I actually looked at the external CVS to make sure it''s still > there before posting, but it seems it lags a bit behind the real cvs server.Yeah, it''s currently (I think) a 1 hour cycle or something on syncing. Jon.
On Thu, Mar 22, 2007 at 07:31:10AM +0100, Thorsten Leemhuis wrote: > > > On 22.03.2007 07:26, Dave Jones wrote: > > On Thu, Mar 22, 2007 at 07:24:54AM +0100, Thorsten Leemhuis wrote: > > > > > Just wondering -- why are you downloading sparse in the spec file? Isn''t > > > there a better way to use it? > > fixed in a later commit. > > Sorry -- I actually looked at the external CVS to make sure it''s still > there before posting, but it seems it lags a bit behind the real cvs server. Yeah, sometimes it''s near instant, other times it seems to take forever to mirror out. One more reason to look forward to a new SCM :) Dave -- http://www.codemonkey.org.uk
On Thu, 2007-03-22 at 02:18 -0400, Dave Jones wrote:> On Thu, Mar 22, 2007 at 02:15:17AM -0400, Jon Masters wrote: > > Red Hat Buildsystem wrote: > > > > > Package: kernel-2.6.20-1.3010.fc7 > > > Tag: dist-fc7 > > > Status: failed > > > Built by: davej > > > ID: 58684 > > > Started: Thu, 22 Mar 2007 01:48:43 EDT > > > Finished: Thu, 22 Mar 2007 02:11:24 EDT > > > Changelog: > > > * Thu Mar 22 2007 Dave Jones <davej@redhat.com> > > > - Check source with sparse during build. > > > > Very cool. > > Still fighting it. As luck would have it, it''s shaking out > bugs in sparse. Seems to blow up horribly on ppc64.Are these logs put anywhere the public can see them? Sounds like it would be handy to pass on to the kernel janitors, etc. josh
On Thu, Mar 22, 2007 at 05:54:42AM -0500, Josh Boyer wrote: > > Still fighting it. As luck would have it, it''s shaking out > > bugs in sparse. Seems to blow up horribly on ppc64. > > Are these logs put anywhere the public can see them? Sounds like it > would be handy to pass on to the kernel janitors, etc. That''s the second part of the plan. Eventually, I want to get these logs hooked up to Al Viro''s remapper, so that it only reports ''new'' warnings too. Pre-brew, I used to rsync the build logs to me people.redhat.com page in a cronjob. Brew moved where files are stored, and I never got around to fixing it up. I''ll get it hooked up again after I''ve got this in order. After the extras/core merge, and we use an external buildsys, it''s possible they''ll have to go somewhere else, but we''ll deal with that hurdle when we come to it. Dave -- http://www.codemonkey.org.uk