Build errors when building latest DEV tarball (34.0.1788.0)

[Raymond Wooninck]

Hi,

I tried to build the latest DEV build, but I am getting the following build
error:

[ 291s] ERROR [0mat //build/config/linux/pkg_config.gni:5:1: Not valid from
an import.
[ 291s] import("//build/config/sysroot.gni")
[ 291s] [0m^----------------------------------
[ 291s] [0mImports are for defining defaults, variables, and rules. The
[ 291s] appropriate place for this kind of thing is really in a normal
[ 291s] BUILD file.
[ 291s] Generating gyp files from GN...
[ 291s] error: Bad exit status from /var/tmp/rpm-tmp.G7pgoQ (%build)

I know that this configuration is new with the 34 releases, but I am wondering
if this is an error in the tarball or that I am doing something wrong. I know
that building from SVN works fine, so maybe we just got a wrong build here ?

Thanks

Regards

Raymond
openSUSE Chromium packager

[Lei Zhang]

By svn builds work fine. I'm extracting the tarball and trying it out now.

> --
> You received this message because you are subscribed to the Google Groups "chromium-packagers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to chromium-packag...@chromium.org.
> To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/20150395.tV0LzP9Rph%40hqvmt4xx20.eur.cchbc.com.

[Lei Zhang]

There's no tools/gn/bin/linux/gn and gn32 binaries. You probably need
to add the gn_linux (or gn_linux32) step into your build script.

From the src/ directory, run: download_from_google_storage --no_resume
'--platform=linux*' --no_auth --bucket chromium-gn -s
tools/gn/bin/linux/gn.sha1

[Raymond Wooninck]

On Thursday 16 January 2014 14:57:23 Lei Zhang wrote:
> There's no tools/gn/bin/linux/gn and gn32 binaries. You probably need
> to add the gn_linux (or gn_linux32) step into your build script.
>
> From the src/ directory, run: download_from_google_storage --no_resume
> '--platform=linux*' --no_auth --bucket chromium-gn -s
> tools/gn/bin/linux/gn.sha1
>

Hi,

Thanks for the info. This lead me to the solution of the issue I was facing.
In my case it was not that the binaries were missing, but they were too old.
Unfortunately during the build, the openSUSE Build Service doesn't have
connectivity to the outside world, so I have to download the binaries
beforehand and include them as a separate tarball. However the binaries I used
were from beginning of December.

I have to see how I can include this in the update process, although it would
be nice if these binaries can somehow be included in the official tarball.

Regards

Raymond

[Paweł Hajdan, Jr.]

One thing you could do for now is just disabling GN (http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-client/chromium/files/chromium-gn-r1.patch?revision=1.1&view=markup). Obviously that won't work when GN starts to be required for building.

A better solution would be to enable bootstrapping GN from source (just like you can bootstrap ninja). I plan to work on that, most likely when GN actually becomes required. Because GN is still changing rapidly, I'm just trying to waste too much effort on these changes. Also, when it's a required part of the build it'll be easier to test the bootstrapped GN is working properly.

I can consider publishing tarballs which contain files created by hooks (that includes GN). It looks like it's now possible to disable gyp from the environment (the machine publishing tarballs doesn't necessarily have all dependencies needed to successfully run gyp). The tarballs would be bigger (perhaps much bigger), but if that makes packaging easier I'm probably fine with that.

Note that generally for distro packages it's strongly preferred to build everything from source and not use any prebuilt binaries (with obvious exceptions like bootstrapping the C/C++ compiler).

Paweł

--
You received this message because you are subscribed to the Google Groups "chromium-packagers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-packag...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/9146521.Iio7Ihvtle%40hqvmt4xx20.eur.cchbc.com.

[Saikrishna Arcot]

It is currently possible to build gn from source. The gyp file for
building gn is located at tools/gn/gn.gyp, and the make target that
will have to be run is gn. Of course, the section requiring gn will
have to be disabled first (unless you are using the prebuilt binary).
The final binary will be located at src/out/Release/gn and needs to be
copied over to the appropriate directory. I've been using this method
in the dev branch to build gn and then use that for building chromium.

Saikrishna Arcot

> <mailto:chromium-packagers%2Bunsu...@chromium.org>.

> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/9146521.Iio7Ihvtle%40hqvmt4xx20.eur.cchbc.com.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "chromium-packagers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to chromium-packag...@chromium.org.
> To view this discussion on the web visit

> https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/CAATLsPZ5PzwLWQSA%3DXJK4AyjGdrobhGr3ON-5ZB3tXY1DYTw0w%40mail.gmail.com.