1. 13 Nov, 2017 1 commit
    • Tom Anderson's avatar
      Switch to Debian Stretch sysroot · 97f5f9df
      Tom Anderson authored
      This CL switches the default sysroot from Jessie to Stretch.
      There are no deps changes.  The libstdc++ requirement is not
      affected because we do an in-tree build of libc++ instead.
      The glibc requirement is also not changed because we don't
      currently use any of the symbols from the newer version.
      Change-Id: I89da578852fe0f7bfd27ffc08fda99e3b4df239e
      Reviewed-on: https://chromium-review.googlesource.com/598737Reviewed-by: default avatarDirk Pranke <dpranke@chromium.org>
      Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#516093}
  2. 09 Nov, 2017 1 commit
  3. 01 Aug, 2017 1 commit
    • Scott Graham's avatar
      fuchsia: Roll SDK to 2bebd264dfe3bec89469a4179a8292b416cdf2fa · 131568b8
      Scott Graham authored
      Not the normal simple update-the-hash SDK update. Changes:
      - Use our own libunwind (as it's been removed from the Fuchsia SDK);
      - Use the toolchain hash as a version #define instead of the .stamp in
        sysroot (which has been removed). The Fuchsia team builds with -MD to
        cause rebuilds after ABI changes, Chromium builds with -MMD. The
        global define ensures we rebuild on SDK updates;
      - Update clang version to '6.0.0' to get correct builtins lib;
      - Update docs for pulling SDK from prebuilt package, rather than doing
        local builds.
      - Don't include libc++ and libunwind .so into the runner disk image, as
        we link to them statically now.
      Bug: 707030, 750392
      Change-Id: I6702ce208e23288107db00d80f4bed7f875820ae
      Reviewed-on: https://chromium-review.googlesource.com/594270
      Commit-Queue: Scott Graham <scottmg@chromium.org>
      Reviewed-by: default avatarNico Weber <thakis@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#491035}
  4. 19 Jul, 2017 1 commit
    • Tom Anderson's avatar
      Update condition to use sysroot · bea2d1fe
      Tom Anderson authored
      This CL updates use_sysroot to reflect which versions of the Jessie
      sysroot are actually available.  It just changes the list from a
      subtractive one to an additive one, and there should be no functional
      Change-Id: I19497823bb968a37b24a97240a107fdbbdeeab37
      Reviewed-on: https://chromium-review.googlesource.com/576855Reviewed-by: default avatarDirk Pranke <dpranke@chromium.org>
      Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#487735}
  5. 30 May, 2017 1 commit
  6. 12 May, 2017 1 commit
    • scottmg's avatar
      Config changes to support target_os="fuchsia" · 2f97ee12
      scottmg authored
      Fuchsia support has been upstreamed into Clang, so the existing
      Linux-hosted Clang toolchain binaries in third_party with the correct
      --target are sufficient.  Fuchsia is POSIXy so a lot of things will just
      work, but some places will require different implementations, so this CL
      adds support for is_fuchsia as well as a basic implementation of the
      toolchain config.
      The SDK (headers, sysroot, etc.) is currently available at
      go/fuchsia-sdk until a standard location for it is decided upon.
      The near term goal behind this CL is to bring up base/ and net/ on an
      fyi bot running Fuchsia.
      Review-Url: https://codereview.chromium.org/2784063002
      Cr-Commit-Position: refs/heads/master@{#471360}
  7. 10 May, 2017 1 commit
  8. 10 Apr, 2017 1 commit
  9. 06 Apr, 2017 1 commit
  10. 31 Mar, 2017 1 commit
  11. 30 Mar, 2017 1 commit
  12. 28 Mar, 2017 1 commit
  13. 24 Mar, 2017 3 commits
  14. 23 Mar, 2017 2 commits
    • wittman's avatar
      Revert of Update linux sysroot from Wheezy to Jessie (patchset #3 id:40001 of... · 2365c833
      wittman authored
      Revert of Update linux sysroot from Wheezy to Jessie (patchset #3 id:40001 of https://codereview.chromium.org/2748183005/ )
      Reason for revert:
      Breaks the Official Linux build. Expected deps aren't matching up:
      [30924/30936] ACTION //chrome/installer/linux:stable_rpm(//build/toolchain/linux:clang_x64)
      FAILED: google-chrome-stable_59.0.3050.0-1.x86_64.rpm
      python ../../chrome/installer/linux/flock_make_package.py linux_package.lock installer/rpm/build.sh -o . -b . -a x64 -c stable -d google_chrome
      Staging common install files in '/tmp/rpm.build.PQ88Wk'...
      Staging RPM install files in '/tmp/rpm.build.PQ88Wk'...
      Packaging x86_64...
      --- /b/c/b/Google_Chrome_Linux_x64/src/out/Release/installer/rpm/expected_deps_x86_64	2017-03-23 06:48:22.885425473 -0700
      +++ /dev/fd/63	2017-03-23 08:04:33.320136041 -0700
      @@ -15,7 +15,9 @@
      ERROR: Shared library dependencies changed!
      If this is intentional, please update:
      [30925/30936] ACTION //chrome/installer/linux:unstable_deb(//build/toolchain/linux:clang_x64)
      FAILED: google-chrome-unstable_59.0.3050.0-1_amd64.deb
      python ../../chrome/installer/linux/flock_make_package.py linux_package.lock installer/debian/build.sh -o . -b . -a x64 -c unstable -d google_chrome -s /b/c/b/Google_Chrome_Linux_x64/src/build/linux/debian_jessie_amd64-sysroot
      dpkg-shlibdeps: warning: binaries to analyze should already be installed in their package's directory
      --- /b/c/b/Google_Chrome_Linux_x64/src/out/Release/installer/debian/expected_deps_x64_jessie	2017-03-23 06:48:22.885425473 -0700
      +++ actual	2017-03-23 08:04:37.504250895 -0700
      @@ -1,17 +1,17 @@
       libasound2 (>= 1.0.16)
       libatk1.0-0 (>= 1.12.4)
      -libc6 (>= 2.14)
      +libc6 (>= 2.15)
       libcairo2 (>= 1.6.0)
       libcups2 (>= 1.4.0)
      -libdbus-1-3 (>= 1.2.14)
      +libdbus-1-3 (>= 1.1.4)
       libexpat1 (>= 2.0.1)
       libfontconfig1 (>= 2.11)
      -libfreetype6 (>= 2.4.2)
      +libfreetype6 (>= 2.3.9)
       libgcc1 (>= 1:4.1.1)
       libgconf-2-4 (>= 3.2.5)
       libgdk-pixbuf2.0-0 (>= 2.22.0)
      -libglib2.0-0 (>= 2.31.8)
      +libglib2.0-0 (>= 2.28.0)
       libgtk-3-0 (>= 3.3.16)
       libnspr4 (>= 2:4.9-2~)
       libnss3 (>= 2:3.13.4-2~)
      ERROR: Shared library dependencies changed!
      If this is intentional, please update:
      Original issue's description:
      > Update linux sysroot from Wheezy to Jessie
      > This is an attempt to reland a change that was attempted
      > several times already.  It now includes changes to the
      > linux packaging expectations which previously caused
      > failed on the official bots.
      > TESTED=ninja linux_packages_all
      > BUG=701894
      > Review-Url: https://codereview.chromium.org/2748183005
      > Cr-Commit-Position: refs/heads/master@{#459062}
      > Committed: https://chromium.googlesource.com/chromium/src/+/94c4fa81c45284d0fe1e5616f52fcad56745077b
      # Skipping CQ checks because original CL landed less than 1 days ago.
      Review-Url: https://codereview.chromium.org/2776503002
      Cr-Commit-Position: refs/heads/master@{#459128}
    • sbc's avatar
      Update linux sysroot from Wheezy to Jessie · 94c4fa81
      sbc authored
      This is an attempt to reland a change that was attempted
      several times already.  It now includes changes to the
      linux packaging expectations which previously caused
      failed on the official bots.
      TESTED=ninja linux_packages_all
      Review-Url: https://codereview.chromium.org/2748183005
      Cr-Commit-Position: refs/heads/master@{#459062}
  15. 14 Mar, 2017 2 commits
  16. 13 Mar, 2017 2 commits
  17. 10 Feb, 2017 1 commit
    • dpranke's avatar
      Add a build arg to control whether to use a jessie sysroot. · 657454d7
      dpranke authored
      We're working on a class of changes in the Linux desktop UI
      that won't work on Precise; they need newer Linux versions
      that basically amount to needing to link against the Debian
      Jessie sysroot instead of the Debian Wheezy sysroot. Previously
      we were working around this by checking whether we were building
      with ozone + use_kbdcommon, but that caused a dependency inversion
      by making //build depend on //ui.
      This changes adds a dedicated GN build arg, use_jessie_sysroot,
      that we'll explicitly set instead, and that way we can avoid
      the dependency inversion.
      R=thomasanderson@chromium.org, tonikitoo@igalia.com
      Review-Url: https://codereview.chromium.org/2687203002
      Cr-Commit-Position: refs/heads/master@{#449505}
  18. 07 Feb, 2017 1 commit
  19. 25 Jan, 2017 1 commit
  20. 26 Aug, 2016 2 commits
  21. 25 Aug, 2016 1 commit
  22. 29 Jun, 2016 1 commit
    • ckulakowski's avatar
      Fix for cross compiling 32bit linux on 64bit host machine · 16c10601
      ckulakowski authored
      Right now when custom sysroot is provided as gn parameter (target_sysroot)
      only 32 bit custom sysroot will be used. 64 bit sysroot (which is also needed
      by 32 bit build by - for example - protobuf) is expected to be found in default
      location. This change adds possibility to provide path to directory containing
      both sysroots for linux (32 bit and 64 bit).
      Review-Url: https://codereview.chromium.org/2096323002
      Cr-Commit-Position: refs/heads/master@{#402742}
  23. 14 Jun, 2016 1 commit
  24. 18 May, 2016 1 commit
  25. 21 Apr, 2016 1 commit
  26. 04 Feb, 2016 1 commit
    • zforman's avatar
      Reverts fdca07 and makes it possible to force absolute paths. · 4b6f030a
      zforman authored
      Explicitly: This reverts the patch that reverted the patch that
      removed the majority of absolute paths from linux builds, and makes
      it possible to use an absolute path by setting dont_embed_build_metadata
      to false.
      In conjunction with codereview.chromium.org/1642193002 that modifies the codesearch
      buildbot to use dont_embed_build_metadata = false, this CL should allow
      codesearch to continue working, and all other buildbots and users
      to gain the benefits of not requiring absolute paths.
      Review URL: https://codereview.chromium.org/1643523004
      Cr-Commit-Position: refs/heads/master@{#373432}
  27. 22 Jan, 2016 1 commit
  28. 20 Jan, 2016 1 commit
    • zforman's avatar
      clang: Makes builds with clang less dependent on absolute file path · fdca0741
      zforman authored
      [Note: Dependency claims are only valid on Linux builds]
      This change removes absolute file paths from several locations in
      produced binaries, reducing the total number of files containing
      absolute file paths from ~30k to ~4k.
      Specifically, this removes absolute paths from:
      .rodata (sysroot based)
      .debug_str, .debug_info (debug prefix based)
      .debug_line (debug prefix and sysroot based)
      .debug_info still contains (on Linux) 22 absolute paths, but
      as discussed below, this is most likely simple to resolve.
      This can be measured by using
      $ find out/Default/ -type f | grep -v ninja | xargs -I '{}' grep -l \
        'absolute-path-component' '{}' | wc -l
      Before: 30420
      After: 3917 (https://gist.github.com/anonymous/fd870076c990fcf792c7)
      The remaining instances mostly originate from NaCL not
      having the flag enabled. Enabling requires updating the
      toolchain's version of clang to newer than release 3.8
      Generated ninja files still have some absolute file paths. At
      the very least, they contain -fdebug-prefix-map=/ABSOLUTE/PATH/TO/DIR.
      This will be removed later.
      Review URL: https://codereview.chromium.org/1556923002
      Cr-Commit-Position: refs/heads/master@{#370320}
  29. 09 Dec, 2015 1 commit
  30. 03 Dec, 2015 1 commit
  31. 26 Nov, 2015 2 commits
  32. 24 Nov, 2015 2 commits