|
|
Created:
4 years, 5 months ago by Tom (Use chromium acct) Modified:
4 years, 3 months ago CC:
chromium-reviews, grt+watch_chromium.org, wfh+watch_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionLinux: Build with xcb
BUG=634085
Committed: https://crrev.com/f05e88ae004f438fcd8fb2023b51ba19a7903e48
Cr-Commit-Position: refs/heads/master@{#414882}
Patch Set 1 #Patch Set 2 : Updated sysroot install script #Patch Set 3 : Call xcb_disconnect #Patch Set 4 : Revert x11_types.cc #
Total comments: 2
Patch Set 5 : Added symbol references from ui/gfx/x #
Total comments: 6
Patch Set 6 : Remove dbus from expected_deps and move install-build-deps to separate CL #Patch Set 7 : Revert all expected_deps* #
Total comments: 1
Patch Set 8 : Remove x11-xcb and xcb configs #Patch Set 9 : Revert gyp configs :D #Patch Set 10 : Revert install-sysroot.py #Messages
Total messages: 90 (55 generated)
The CQ bit was checked by thomasanderson@google.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: cast_shell_linux on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/cast_shell_linu...)
dpranke@chromium.org changed reviewers: + dpranke@chromium.org, mmoss@chromium.org, thestig@chromium.org
The CQ bit was checked by thomasanderson@google.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
This doesn't work as is. You need multiple CLs: - One CL to update the sysroot [upload the new sysroot tarballs] - Second CL to switch to the sysroot - Third CL to start using features from the new sysroot. (This can be part of the previous CL, but it might be better to take things one step at a time)
The CQ bit was checked by thomasanderson@google.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by thomasanderson@google.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
Description was changed from ========== Try adding xcb ========== to ========== Linux: Build with xcb ==========
lgtm. When this lands, you'll probably need to have the labs folks re-run build/install-build-deps.sh on all of the linux machines ...
On 2016/08/03 00:12:34, Dirk Pranke wrote: > lgtm. > > When this lands, you'll probably need to have the labs folks re-run > build/install-build-deps.sh on all of the linux machines ... How about landing the install-build-deps changes separately first, re-run it on all the machines, and land the rest? Also, BUG= ?
https://codereview.chromium.org/2163623003/diff/60001/build/install-build-dep... File build/install-build-deps.sh (right): https://codereview.chromium.org/2163623003/diff/60001/build/install-build-dep... build/install-build-deps.sh:131: zlib1g $chromeos_lib_list libx11-xcb1" alphabetical order, ditto below.
Description was changed from ========== Linux: Build with xcb ========== to ========== Linux: Build with xcb BUG=634085 ==========
On 2016/08/03 19:08:07, Lei Zhang wrote: > On 2016/08/03 00:12:34, Dirk Pranke wrote: > > lgtm. > > > > When this lands, you'll probably need to have the labs folks re-run > > build/install-build-deps.sh on all of the linux machines ... > > How about landing the install-build-deps changes separately first, re-run it on > all the machines, and land the rest? I think the linux machines already have the necessary dependencies installed. I picked a try server and it has these packages already: libxcb1:amd64 1.10-2ubuntu1 libx11-xcb1:amd64 2:1.6.2-1ubuntu2 > > Also, BUG= ? Added BUG.
thomasanderson@google.com changed reviewers: + sadrul@chromium.org - mmoss@chromium.org
+sadrul for ui/gfx/x https://codereview.chromium.org/2163623003/diff/60001/build/install-build-dep... File build/install-build-deps.sh (right): https://codereview.chromium.org/2163623003/diff/60001/build/install-build-dep... build/install-build-deps.sh:131: zlib1g $chromeos_lib_list libx11-xcb1" On 2016/08/03 19:08:52, Lei Zhang wrote: > alphabetical order, ditto below. Done. https://codereview.chromium.org/2163623003/diff/80001/ui/gfx/x/x11_types.cc File ui/gfx/x/x11_types.cc (left): https://codereview.chromium.org/2163623003/diff/80001/ui/gfx/x/x11_types.cc#o... ui/gfx/x/x11_types.cc:176: emacs auto-saves the file like this https://codereview.chromium.org/2163623003/diff/80001/ui/gfx/x/x11_types.cc File ui/gfx/x/x11_types.cc (right): https://codereview.chromium.org/2163623003/diff/80001/ui/gfx/x/x11_types.cc#n... ui/gfx/x/x11_types.cc:21: asm volatile("" ::"r"(xcb_connect)); Couldn't figure out a better way to do this
The CQ bit was checked by thomasanderson@google.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
https://codereview.chromium.org/2163623003/diff/80001/ui/gfx/x/x11_types.cc File ui/gfx/x/x11_types.cc (right): https://codereview.chromium.org/2163623003/diff/80001/ui/gfx/x/x11_types.cc#n... ui/gfx/x/x11_types.cc:21: asm volatile("" ::"r"(xcb_connect)); On 2016/08/03 19:42:16, Tom Anderson wrote: > Couldn't figure out a better way to do this What does this do?
https://codereview.chromium.org/2163623003/diff/80001/ui/gfx/x/x11_types.cc File ui/gfx/x/x11_types.cc (right): https://codereview.chromium.org/2163623003/diff/80001/ui/gfx/x/x11_types.cc#n... ui/gfx/x/x11_types.cc:21: asm volatile("" ::"r"(xcb_connect)); On 2016/08/04 15:45:29, sadrul wrote: > On 2016/08/03 19:42:16, Tom Anderson wrote: > > Couldn't figure out a better way to do this > > What does this do? References symbols so we link against the shared libraries and the dependencies show up in expected_build_deps. I wanted all of the build stuff to go in one cl, but maybe the expected_build_deps stuff should just go in the next one that actually uses xcb?
https://codereview.chromium.org/2163623003/diff/80001/chrome/installer/linux/... File chrome/installer/linux/debian/expected_deps_x64 (right): https://codereview.chromium.org/2163623003/diff/80001/chrome/installer/linux/... chrome/installer/linux/debian/expected_deps_x64:7: libdbus-1-3 (>= 1.2.14) Did you build with "allow_posix_link_time_opt = false" in your official build? I think that might be why this value is different for you.
Patchset #8 (id:140001) has been deleted
https://codereview.chromium.org/2163623003/diff/80001/chrome/installer/linux/... File chrome/installer/linux/debian/expected_deps_x64 (right): https://codereview.chromium.org/2163623003/diff/80001/chrome/installer/linux/... chrome/installer/linux/debian/expected_deps_x64:7: libdbus-1-3 (>= 1.2.14) On 2016/08/04 22:08:06, Lei Zhang wrote: > Did you build with "allow_posix_link_time_opt = false" in your official build? I > think that might be why this value is different for you. Yes I did. Removed! Also reverted all of the expected_deps files so we can just update them when we actually start using xcb and need to link against it.
If this works, then go for it.
The CQ bit was checked by thomasanderson@google.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
On 2016/08/04 22:59:13, Lei Zhang wrote: > If this works, then go for it. install-build-deps.sh has been rerun on the build slaves https://bugs.chromium.org/p/chromium/issues/detail?id=635014 sadrul@ + thestig@ I still need your OWNERS approval
lgtm
The CQ bit was checked by thomasanderson@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org Link to the patchset: https://codereview.chromium.org/2163623003/#ps120001 (title: "Revert all expected_deps*")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
https://codereview.chromium.org/2163623003/diff/120001/ui/base/x/BUILD.gn File ui/base/x/BUILD.gn (right): https://codereview.chromium.org/2163623003/diff/120001/ui/base/x/BUILD.gn#new... ui/base/x/BUILD.gn:22: "//build/config/linux:xcb", Do you actually need the new configs?
On 2016/08/09 16:12:30, sadrul wrote: > https://codereview.chromium.org/2163623003/diff/120001/ui/base/x/BUILD.gn > File ui/base/x/BUILD.gn (right): > > https://codereview.chromium.org/2163623003/diff/120001/ui/base/x/BUILD.gn#new... > ui/base/x/BUILD.gn:22: "//build/config/linux:xcb", > Do you actually need the new configs? I need them for a future patch set. Should I just move the ui/base/x/ one to the other patch? Haha, if you look at patch set 1, you'll see that this change is slowly turning into nothing because everything is getting split off :P
On 2016/08/09 16:43:45, Tom Anderson wrote: > On 2016/08/09 16:12:30, sadrul wrote: > > https://codereview.chromium.org/2163623003/diff/120001/ui/base/x/BUILD.gn > > File ui/base/x/BUILD.gn (right): > > > > > https://codereview.chromium.org/2163623003/diff/120001/ui/base/x/BUILD.gn#new... > > ui/base/x/BUILD.gn:22: "//build/config/linux:xcb", > > Do you actually need the new configs? > > I need them for a future patch set. Should I just move the ui/base/x/ one to > the other patch? > Haha, if you look at patch set 1, you'll see that this change is slowly turning > into nothing because everything is getting split off :P What I mean is, you have updated the X11 config to already pull in X11-xcb and xcb. In that case, do we need the separate x11-xcb and xcb configs?
On 2016/08/09 16:47:35, sadrul wrote: > On 2016/08/09 16:43:45, Tom Anderson wrote: > > On 2016/08/09 16:12:30, sadrul wrote: > > > https://codereview.chromium.org/2163623003/diff/120001/ui/base/x/BUILD.gn > > > File ui/base/x/BUILD.gn (right): > > > > > > > > > https://codereview.chromium.org/2163623003/diff/120001/ui/base/x/BUILD.gn#new... > > > ui/base/x/BUILD.gn:22: "//build/config/linux:xcb", > > > Do you actually need the new configs? > > > > I need them for a future patch set. Should I just move the ui/base/x/ one to > > the other patch? > > Haha, if you look at patch set 1, you'll see that this change is slowly > turning > > into nothing because everything is getting split off :P > > What I mean is, you have updated the X11 config to already pull in X11-xcb and > xcb. In that case, do we need the separate x11-xcb and xcb configs? Done. Thanks for catching that
The CQ bit was checked by thomasanderson@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from thestig@chromium.org, dpranke@chromium.org Link to the patchset: https://codereview.chromium.org/2163623003/#ps180001 (title: "Revert gyp configs :D")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Linux: Build with xcb BUG=634085 ========== to ========== Linux: Build with xcb BUG=634085 ==========
Message was sent while issue was closed.
Committed patchset #9 (id:180001)
Message was sent while issue was closed.
Description was changed from ========== Linux: Build with xcb BUG=634085 ========== to ========== Linux: Build with xcb BUG=634085 Committed: https://crrev.com/83b8989c96b207efd9123cd25073b32edfe5a275 Cr-Commit-Position: refs/heads/master@{#410806} ==========
Message was sent while issue was closed.
Patchset 9 (id:??) landed as https://crrev.com/83b8989c96b207efd9123cd25073b32edfe5a275 Cr-Commit-Position: refs/heads/master@{#410806}
Message was sent while issue was closed.
A revert of this CL (patchset #9 id:180001) has been created in https://codereview.chromium.org/2229663006/ by thomasanderson@google.com. The reason for reverting is: Causing build failure https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%... ../../third_party/binutils/Linux_x64/Release/bin/ld.gold: error: cannot find -lX11-xcb.
Message was sent while issue was closed.
Description was changed from ========== Linux: Build with xcb BUG=634085 Committed: https://crrev.com/83b8989c96b207efd9123cd25073b32edfe5a275 Cr-Commit-Position: refs/heads/master@{#410806} ========== to ========== Linux: Build with xcb BUG=634085 Committed: https://crrev.com/83b8989c96b207efd9123cd25073b32edfe5a275 Cr-Commit-Position: refs/heads/master@{#410806} ==========
On 2016/08/09 21:05:07, Tom Anderson wrote: > A revert of this CL (patchset #9 id:180001) has been created in > https://codereview.chromium.org/2229663006/ by mailto:thomasanderson@google.com. > > The reason for reverting is: Causing build failure > > https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%... > ../../third_party/binutils/Linux_x64/Release/bin/ld.gold: error: cannot find > -lX11-xcb. Going to try to reland this. Reason for failure: couldn't link xdisplaycheck on ChromeOS https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%... The log indicates xdisplaycheck didn't link against the sysroot, but was using the system libraries. However, xdisplaycheck linked on the ChromeOS try bots, and I see that it does use the sysroot if I try to build locally.
The CQ bit was checked by thomasanderson@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
The CQ bit was checked by thomasanderson@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by thomasanderson@google.com
sadrul@chromium.org changed reviewers: - sadrul@chromium.org
Removing myself from the reviewer list since my review is no longer needed.
Description was changed from ========== Linux: Build with xcb BUG=634085 Committed: https://crrev.com/83b8989c96b207efd9123cd25073b32edfe5a275 Cr-Commit-Position: refs/heads/master@{#410806} ========== to ========== Linux: Build with xcb BUG=634085 ==========
The CQ bit was checked by thomasanderson@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from thestig@chromium.org, dpranke@chromium.org Link to the patchset: https://codereview.chromium.org/2163623003/#ps200001 (title: "Revert install-sysroot.py")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by thomasanderson@google.com
The CQ bit was checked by thomasanderson@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
The CQ bit was checked by thomasanderson@google.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by thomasanderson@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Linux: Build with xcb BUG=634085 ========== to ========== Linux: Build with xcb BUG=634085 ==========
Message was sent while issue was closed.
Committed patchset #10 (id:200001)
Message was sent while issue was closed.
Description was changed from ========== Linux: Build with xcb BUG=634085 ========== to ========== Linux: Build with xcb BUG=634085 Committed: https://crrev.com/f05e88ae004f438fcd8fb2023b51ba19a7903e48 Cr-Commit-Position: refs/heads/master@{#414882} ==========
Message was sent while issue was closed.
Patchset 10 (id:??) landed as https://crrev.com/f05e88ae004f438fcd8fb2023b51ba19a7903e48 Cr-Commit-Position: refs/heads/master@{#414882} |