Raising priority as the failures I saw looking to be blocking the ANGLE CQ.

Just had this exact error on my local machine.

The solution was to manually removed out/Release/libfreetype* (or out/Debug in this case) and rebuild.

This is probably due to a broken build rule somewhere, I guess? So I'd keep this bug open even after the bot is saved and try to find someone who knows about this.

I hit this as well on my local machine this morning.

I ended up removing out/*/libfreetype.so.6, after which everything built correctly. The file system suggested that that file hadn't been modified since October 5, so I'd also suspect a missing build rule for it.

I hit this today on a target_os="chromeos" component build, if that's helpful.

@troopers: Could you please wipe the output directories of these buildslaves?  The ANGLE CQ cannot land patches consistently until these bots can build again. 

The builders are:
slave550-c4
slave551-c4
slave553-c4
slave554-c4
slave897-c4
slave898-c4
slave899-c4
slave900-c4
slave901-c4
slave902-c4

i did 
  rm -rf /b/c/b/linux
on all these machines

https://build.chromium.org/p/tryserver.chromium.angle/builders/linux_angle_dbg_ng/builds/6705
and 
https://build.chromium.org/p/tryserver.chromium.angle/builders/linux_angle_dbg_ng/builds/6706
failed because of my actions

I also get this locally on Linux debug builds, 2/2 times.

Apparently `gn clean out/YourBuildDirectory` fixes this.

Bot hasn't seen a failure since nodir's wipe, thanks!  Not sure if the underlying issue has been fixed.

Issue 783050 has been merged into this issue.

+dpranke this failure is interesting.  Something built out/.../libfreetype.so.6 at one point, but it has since been removed.  After the freetype roll yesteday, v8_context_snapshot_generator (which indirectly loads libfreetype.so.6) fails now that the symbols have diverged, and you must manually remove out/.../libfreetype.so.6 to get the build working again.

Is there anything we can do about this besides "don't name our libraries the same as system libraries"?

https://build.chromium.org/p/tryserver.chromium.angle/builders/linux_angle_dbg_ng?numbuilds=50 is green since #7, so pulling it out from the troopers queue

@thomasanderson - the only other thing that comes to mind is landing a landmine, but we want to avoid doing that where possible.

I wonder if this is partially due to reusing the same output directory for different build configurations, e.g., we might want libfreetype.so.6 for one builder, and not want it for another, but try to build them both in the same directory with different sets of GN args and be bedeviled by file collisions as a result.

Work-around: you don't have to gn clean the out dir. Just deleting out/XXX/libfreetype.so.6 is sufficient.

c#14: Though I think this can be triggered with just one build configuration per out dir, I think it's a good point that the bots should be using separate out dirs for each config.  I noticed they all tend to use out/Debug or out/Release.  Maybe it would make more sense to use out/<buildername>?

Anyway, I think everything has cycled through by now so I'm closing this issue out.

 Issue 786588  has been merged into this issue.

The buildername in the above is linux_angle_dbg_ng?