Chromium 60 build failure: pangocairo/freetype conflict

[rvalles]

For a few days now, world update's been failing at Chromium 60 (~amd64) like this:

[mv]

[rvalles]

[gmt]

[gmt]

[mv]

[gmt]

I tried a bunch of stuff that didn't work but here's what did -- can't say for sure, yet, which of these things made the difference:

• I un-applied the "notmpfs" portage.env keyword I use to move things from /var/tmp/portage on tmpfs to /var/tmp/notmpfs/portage on btrfs. The corresponding /etc/portage/env/notmpfs simply changes PORTAGE_TMPDIR. FTR I have a fairly large tmpfs (30GB) at /var/tmp/portage.
  
• I applied the "nodebug" portage.env keyword I use to turn off debug symbol generation. The corresponding /etc/portage/env/nodebug looks like this:
  

  Code:

  GMT_NO_DEBUG="gmt_no_debug" FEATURES="${FEATURES} -splitdebug -compressdebug -installsources"

  
  Which triggers this in /etc/portage/bashrc:
  

  Code:

  gmt_strip_gdb_flags() {         local rslt=() flag flagz=( $* )         for flag in "${flagz[@]}"; do                 case "${flag}" in                         -g*) continue;;                         *) rslt+=("${flag}"); continue;;                 esac         done         echo "${rslt[*]}" } if [[ ${GMT_NO_DEBUG} == gmt_no_debug ]]; then         GMT_NO_DEBUG=didit         CFLAGS="$(gmt_strip_gdb_flags "${CFLAGS}")"         CXXFLAGS="$(gmt_strip_gdb_flags "${CXXFLAGS}")"         FCFLAGS="$(gmt_strip_gdb_flags "${FCFLAGS}")" fi

  
  
• I turned off the custom-cflags use-flag
  

_________________
-gmt

[fkeaz]

I got around this by rolling back gcc to pre 5.x gcc

[crowbert]

I have been suffering the same problem starting with chromium-60, but only on one of two systems, both new installs in the last six months or so. The problem is that on one system I had -ggdb in my CFLAGS. The ebuild for chromium modifies the flags, but doesn't strip out that option. Removing it allows chromium to build.