All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser] Modern Chromium with GN
Date: Fri, 20 Oct 2017 11:33:08 -0400	[thread overview]
Message-ID: <20171020153307.GA6636@linux-uys3> (raw)
In-Reply-To: <87shefnm1g.fsf@rkubodac-desk.ger.corp.intel.com>

On Thu 2017-10-19 @ 06:24:11 PM, Raphael Kubo da Costa wrote:
> Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> writes:
> > Work on Chromium 62 has started, but updating is a bit slower now that
> > I'm trying to test GCC 5, 7, pyro and rocko.
> 
> I've pushed a new branch called "chromium62". It's been test-built
> against Yocto's pyro (with GCC 5) and rocko (with GCC 7) for x86 and
> x86-64.
> 
> Additional testing is appreciated!

It looks like something in the chromium62 build is calling my native g++ and
expecting that this native g++ will be recent enough to support c++14:


	| g++  -MMD -MF base/base_paths.o.d  -I/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/chromium-62.0.3202.62/out_bootstrap/gen -I/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/chromium-62.0.3202.62 -isystem/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/recipe-sysroot-native/usr/include -O2 -pipe -DNO_TCMALLOC -D__STDC_FORMAT_MACROS -O2 -g0 -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions -isystem/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/recipe-sysroot-native/usr/include -O2 -pipe -std=c++14 -Wno-c++11-narrowing -c /z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/chromium-62.0.3202.62/base/base_paths.cc -o base/base_paths.o
	| g++: error: unrecognized command line option ‘-std=c++14’


Unfortunately on my openSUSE 42.2 host this isn't the case:

	$ g++ -v
	Using built-in specs.
	COLLECT_GCC=g++
	COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/4.8/lto-wrapper
	Target: x86_64-suse-linux
	Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.8 --enable-ssp --disable-libssp --disable-plugin --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap --with-slibdir=/lib64 --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --enable-linker-build-id --enable-linux-futex --program-suffix=-4.8 --without-system-libunwind --with-arch-32=i586 --with-tune=generic --build=x86_64-suse-linux --host=x86_64-suse-linux
	Thread model: posix
	gcc version 4.8.5 (SUSE Linux)


Is there any way to intercept these calls and have it call OE's gcc-native
instead?


  reply	other threads:[~2017-10-20 15:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02 15:35 [meta-browser] Modern Chromium with GN Jacobo Aragunde Pérez
2017-10-02 17:07 ` Otavio Salvador
2017-10-05  0:43   ` Trevor Woerner
2017-10-05 10:20     ` Jacobo Aragunde Pérez
2017-10-05 15:26     ` Jacobo Aragunde Pérez
2017-10-09 15:27       ` Raphael Kubo da Costa
2017-10-10 18:28         ` Trevor Woerner
2017-10-10 19:10           ` Kubo Da Costa, Raphael
2017-10-11 12:20             ` Trevor Woerner
2017-10-11 15:00               ` Raphael Kubo da Costa
2017-10-27  8:49                 ` Daniel Mack
2017-10-27  9:19                   ` Jacobo Aragunde Pérez
2017-10-28 16:13                     ` Daniel Mack
     [not found]       ` <5612aa4c-d986-89f7-7667-14898b5f7bfc@igalia.com>
2017-10-16 14:37         ` Raphael Kubo da Costa
2017-10-16 14:59           ` Raphael Kubo da Costa
2017-10-18 14:08             ` Raphael Kubo da Costa
2017-10-19 16:24               ` Raphael Kubo da Costa
2017-10-20 15:33                 ` Trevor Woerner [this message]
2017-10-23 11:06                   ` Raphael Kubo da Costa
2017-10-23 11:12                     ` Otavio Salvador
2017-10-23 13:33                       ` Raphael Kubo da Costa
2017-10-27 15:44                         ` Trevor Woerner
2017-10-30 11:05                           ` Jacobo Aragunde Pérez
2017-10-30 13:23                           ` Raphael Kubo da Costa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171020153307.GA6636@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=raphael.kubo.da.costa@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.