New issue
Advanced search Search tips

Issue 631943 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

out/Debug folder is missing

Reported by rohan.k...@gmail.com, Jul 27 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce the problem:
1.fetch --nohooks chromium
2.cd src && ./build/install-build-deps.sh
3.git show-ref --tags
4.git checkout -b br54 54.0.2808.0
5.gclient sync --with_branch_heads --jobs 16

What is the expected behavior?
Debug and Release folders are missing inside src/out directory.

What went wrong?
Unable to execute ninja -C out/Debug chrome chrome to install chrome

Did this work before? Yes version 53.0.2774.0

Chrome version: 54.0.2808.0  Channel: stable
OS Version: 15.04
Flash Version: Shockwave Flash 22.0 r0
 
Labels: Needs-Feedback
Are you using the GN to build chromium?

To make a build folder for you, have you ever tried:
$ gn gen out/Debug

This should generate a out/Debug folder for you.

For more details, please refer to https://chromium.googlesource.com/chromium/src/+/master/tools/gn/docs/quick_start.md

Comment 2 by grt@chromium.org, Jul 27 2016

Labels: Proj-GN-Migration
Status: WontFix (was: Unconfirmed)
What zhongyi@ wrote is correct.

We no longer run GYP as part of `gclient sync`, and so that directory will not be present in a new checkout, until you run `gn gen`.
Okay. Thank You,
Can you tell me which is the last build version with which I can build using GYP parameters.
You can still build w/ GYP now, it just doesn't run by default. I.e., run build/gyp_chromium explicitly.

However, that's going to start breaking any day now.
The build fails with Clang error:
Error log attached.

that looks like you couldn't run the clang binary at all (though I'm not sure). I'm not sure why that would be, unless maybe you weren't running on an x64 machine?
Since it's just on the very last step and linking, maybe it just ran out of memory or some other resource?

Sign in to add a comment