WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
82216
[GTK] jhbuild wrongly tricked into clean-up
https://bugs.webkit.org/show_bug.cgi?id=82216
Summary
[GTK] jhbuild wrongly tricked into clean-up
Philippe Normand
Reported
2012-03-26 08:52:42 PDT
Patch
http://trac.webkit.org/changeset/111929
badly broke setups where the build directory is the git branch name, at least. Here my build directory is /home/phil/gst/jhbuild/build/WebKit/WebKitBuild/branchName/Release jhbuild clean is triggered... and fails: /bin/sh /home/phil/gst/jhbuild/build/WebKit/WebKitBuild/Dependencies/Root/share/jhbuild/triggers/glib.trigger *** the following modules were not built *** [16/16] fonts Cleaning jhbuild modules failed! at /home/phil/gst/jhbuild/build/WebKit/Tools/Scripts/webkitdirs.pm line 1951. It seems the jhbuild.modules md5sum test always fails in that setup. Also, I don't think storing the jhbuildrc.md5sum and jhbuild.modules.md5sum in the build directory is a very good idea... Why not storing it in Dependencies or in Tools/ somewhere and ignore it from the VCS POV?
Attachments
Patch
(3.14 KB, patch)
2012-03-26 09:09 PDT
,
Philippe Normand
gustavo
: review+
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Philippe Normand
Comment 1
2012-03-26 09:09:28 PDT
Created
attachment 133825
[details]
Patch
Philippe Normand
Comment 2
2012-03-26 09:11:15 PDT
Someone should also check the fonts cleaning error but not me, I spent too much time doing perl today.
Mustafizur Rahaman( :rahaman)
Comment 3
2012-03-27 01:34:37 PDT
Today I got an weird build issue while building webkit-gtk & I am using 112046. I got my release build working, but then when I am building webkit for debug option, I see that all my dependent packages e.g. glib, cairo, gtk+ are being compiled again, which I think it should not do. I talked to philn-tp in #webkit-gtk & I am suggested this bug might be the reason for the issue, so sharing my observation. Can someone please look into this?
Martin Robinson
Comment 4
2012-03-27 07:01:35 PDT
(In reply to
comment #3
)
> Today I got an weird build issue while building webkit-gtk & I am using 112046. > > I got my release build working, but then when I am building webkit for debug option, I see that all my dependent packages e.g. glib, cairo, gtk+ are being compiled again, which I think it should not do. > > I talked to philn-tp in #webkit-gtk & I am suggested this bug might be the reason for the issue, so sharing my observation. Can someone please look into this?
Did you update your checkout between builds? Do packages rebuild every time you build?
Mustafizur Rahaman( :rahaman)
Comment 5
2012-03-27 08:41:13 PDT
(In reply to
comment #4
)
> (In reply to
comment #3
) > > Today I got an weird build issue while building webkit-gtk & I am using 112046. > > > > I got my release build working, but then when I am building webkit for debug option, I see that all my dependent packages e.g. glib, cairo, gtk+ are being compiled again, which I think it should not do. > > > > I talked to philn-tp in #webkit-gtk & I am suggested this bug might be the reason for the issue, so sharing my observation. Can someone please look into this? > > Did you update your checkout between builds? Do packages rebuild every time you build?
I did not update the packages in between. I first build release build & then when I was building debug build, still I saw the packages being built. I did not try to build the release/debug build after that..
Gustavo Noronha (kov)
Comment 6
2012-03-27 10:57:37 PDT
Comment on
attachment 133825
[details]
Patch Makes sense, thanks Philippe! The only worry I have is that autogen might not be run in some cases it should, when building more than one build type, but that's easily fixable by a human and not a problem on bots =)
Philippe Normand
Comment 7
2012-03-28 01:23:06 PDT
Committed
r112372
: <
http://trac.webkit.org/changeset/112372
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug