Package Details: gn-git r1682.a5bcbd72-1

Git Clone URL: https://aur.archlinux.org/gn-git.git (read-only, click to copy)
Package Base: gn-git
Description: Meta-build system which generates Ninja build files
Upstream URL: https://gn.googlesource.com/gn
Keywords: build chromium gn ninja
Licenses: BSD
Conflicts: gn, gn-bin
Provides: gn
Submitter: aperez
Maintainer: aperez (zopieux)
Last Packager: aperez
Votes: 5
Popularity: 0.000000
First Submitted: 2015-09-14 18:50 (UTC)
Last Updated: 2020-01-02 16:13 (UTC)

Required by (34)

Sources (2)

Latest Comments

1 2 3 4 Next › Last »

petronny commented on 2020-06-20 10:11 (UTC)

Get this error

[160/274] CXX src/gn/version.o
FAILED: src/gn/version.o 
c++ -MMD -MF src/gn/version.o.d -I../src -I. -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -pthread -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -pthread -DNDEBUG -O3 -g -fdata-sections -ffunction-sections -flto -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions -fno-rtti -fdiagnostics-color -Wall -Wextra -Wno-unused-parameter -std=c++17 -c ../src/gn/version.cc -o src/gn/version.o
../src/gn/version.cc: In member function ‘bool Version::operator<(const Version&) const’:
../src/gn/version.cc:51:15: error: ‘tie’ is not a member of ‘std’
   51 |   return std::tie(major_, minor_, patch_) <
      |               ^~~
../src/gn/version.cc:10:1: note: ‘std::tie’ is defined in header ‘<tuple>’; did you forget to ‘#include <tuple>’?
    9 | #include "base/strings/string_number_conversions.h"
  +++ |+#include <tuple>
   10 | 
../src/gn/version.cc:52:15: error: ‘tie’ is not a member of ‘std’
   52 |          std::tie(other.major_, other.minor_, other.patch_);
      |               ^~~
../src/gn/version.cc:52:15: note: ‘std::tie’ is defined in header ‘<tuple>’; did you forget to ‘#include <tuple>’?

sigint commented on 2019-12-09 11:08 (UTC)

Upstream removed the cc rule, stating that "gn has no C code" (https://gn.googlesource.com/gn/+/de542971d3cbc4b9d42e603667ac3c24b639a02a%5E%21/)

Additionally, tools/misc was moved from gn/tools/gn/misc to the top-level gn/misc (https://gn.googlesource.com/gn/+/3f6100c97584f7d3f7664add92f1c1dbe0223218).

All in all, I had to make the following changes to the PKGBUILD and the patch to make the package install:

diff --git a/PKGBUILD b/PKGBUILD
index 3059bd4..87354e7 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@

 pkgname=gn-git
 pkgdesc='Meta-build system which generates Ninja build files'
-pkgver=r1668.776bbfd9
+pkgver=r1676.fe36c7c1
 pkgrel=1
 license=('BSD')
 arch=('x86_64' 'i686')
@@ -14,7 +14,7 @@ makedepends=(python ninja git)
 url='https://gn.googlesource.com/gn'
 source=("gn::git+${url}" gcc-support.patch)
 sha256sums=('SKIP'
-            '5b7d79a6953f023109f0c23601ba9fbb8b63f50ebb6b185e32102c213a97d81a')
+            'SKIP')

 pkgver () {
        export GIT_DIR="${startdir}/gn"
@@ -54,7 +54,7 @@ package () {
        local item
        for item in autoload ftplugin ftdetect syntax ; do
                install -Dm 644 -t "${pkgdir}/usr/share/vim/vimfiles/${item}" \
-                       "gn/tools/gn/misc/vim/${item}"/*.vim
+                       "gn/misc/vim/${item}"/*.vim
        done

        # License
diff --git a/gcc-support.patch b/gcc-support.patch
index 61d8737..ffb8d1c 100644
--- a/gcc-support.patch
+++ b/gcc-support.patch
@@ -10,7 +10,7 @@ index d2305c8f..811c2e95 100755
 -        ldflags.extend(['-flto', '-fwhole-program-vtables'])
 +        cflags.append('-flto')
 +        ldflags.append('-flto')
-+        if "clang" in cc:
++        if "clang++" in cxx:
 +          cflags.append('-fwhole-program-vtables')
 +          ldflags.append('-fwhole-program-vtables')

LinuxUserGD commented on 2019-12-07 12:47 (UTC)

I get the same error: "name 'cc' is not defined"

sng commented on 2019-11-19 22:36 (UTC)

Cannot build

This is the whole procedure

$ git clone https://aur.archlinux.org/gn-git.git 
Cloning into 'gn-git'...
remote: Enumerating objects: 86, done.
remote: Counting objects: 100% (86/86), done.
remote: Compressing objects: 100% (73/73), done.
remote: Total 86 (delta 10), reused 85 (delta 10)
Unpacking objects: 100% (86/86), done.

$ cd gn-git
$ makepkg
==> Making package: gn-git r1668.776bbfd9-1 (Wed Nov 20 00:34:36 2019)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Cloning gn git repo...
Cloning into bare repository '/ .... /makepkg/gn-git/gn'...
remote: Sending approximately 26.61 MiB ...
remote: Counting objects: 11677, done
remote: Finding sources: 100% (11676/11676)
remote: Total 40033 (delta 18396), reused 40033 (delta 18396)
Receiving objects: 100% (40033/40033), 33.26 MiB | 2.81 MiB/s, done.
Resolving deltas: 100% (18396/18396), done.
  -> Found gcc-support.patch
==> Validating source files with sha256sums...
    gn ... Skipped
    gcc-support.patch ... Passed
==> Extracting sources...
  -> Creating working copy of gn git repo...
Cloning into 'gn'...
done.
==> Starting prepare()...
patching file build/gen.py
Hunk #1 succeeded at 316 (offset -8 lines).
==> Starting pkgver()...
==> Updated version: gn-git r1673.9a9aff09-1
==> Starting build()...
Traceback (most recent call last):
  File "build/gen.py", line 704, in <module>
    sys.exit(main(sys.argv[1:]))
  File "build/gen.py", line 122, in main
    WriteGNNinja(os.path.join(out_dir, 'build.ninja'), platform, host, options)
  File "build/gen.py", line 321, in WriteGNNinja
    if "clang" in cc:
NameError: name 'cc' is not defined
==> ERROR: A failure occurred in build().
    Aborting...

buffdaddyjr commented on 2019-11-17 00:57 (UTC) (edited on 2019-11-17 00:59 (UTC) by buffdaddyjr)

Still getting....

=> Entering fakeroot environment... ==> Starting package()... install: cannot stat 'gn/tools/gn/misc/vim/autoload/*.vim': No such file or directory ==> ERROR: A failure occurred in package().

Any ideas??

zopieux commented on 2019-11-16 15:32 (UTC)

Fixed the patch.

petronny commented on 2019-11-16 02:46 (UTC)

Please update the patch.

misc commented on 2019-11-08 16:19 (UTC)

patch needs slight update for stuff added below

aperez commented on 2019-09-16 16:00 (UTC)

@sl1pkn07 Thanks for the tip, I have updated the package to use Python 3.x :)

sl1pkn07 commented on 2019-09-14 13:29 (UTC)

seems can build with python3. is possible use it instead python2?

greetings