Bug 613180 – dev-util/bcc-0.2.0-r1 : /.../loader.cc:192:48: error: no matching function for call to ‘clang::CompilerInstance::setInvocation

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Toralf Förster 2017-03-19 08:30:00 UTC]

             ^
/var/tmp/portage/dev-util/bcc-0.2.0-r1/work/bcc-0.2.0/src/cc/frontends/clang/loader.cc: In member function ‘int ebpf::ClangLoader::parse(std::unique_ptr<llvm::Module>*, std::unique_ptr<std::vector<ebpf::TableDesc> >*, const string&, bool, const char**, int)’:
/var/tmp/portage/dev-util/bcc-0.2.0-r1/work/bcc-0.2.0/src/cc/frontends/clang/loader.cc:192:48: error: no matching function for call to ‘clang::CompilerInstance::setInvocation(std::unique_ptr<clang::CompilerInvocation>::pointer)’
   compiler0.setInvocation(invocation0.release());
                                                ^
In file included from /var/tmp/portage/dev-util/bcc-0.2.0-r1/work/bcc-0.2.0/src/cc/frontends/clang/loader.cc:39:0:

  -----------------------------------------------------------------

  This is an unstable amd64 chroot image (named desktop_20170317-213240) at a hardened host acting as a tinderbox.

  -----------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-5.4.0 *

Available Python interpreters, in order of preference:
  [1]   python3.4
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby21 (with Rubygems) *
java-config:
The following VMs are available for generation-2:
*)	IcedTea JDK 3.3.0 [icedtea-bin-8]
Available Java Virtual Machines:
  [1]   icedtea-bin-8  system-vm

[Comment 1 Toralf Förster 2017-03-19 08:30:04 UTC]

Created attachment 467528 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2017-03-19 08:30:07 UTC]

Created attachment 467530 [details]
dev-util:bcc-0.2.0-r1:20170319-074545.log

[Comment 3 Toralf Förster 2017-03-19 08:30:09 UTC]

Created attachment 467532 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2017-03-19 08:30:13 UTC]

Created attachment 467534 [details]
environment

[Comment 5 Toralf Förster 2017-03-19 08:30:16 UTC]

Created attachment 467536 [details]
etc.portage.tbz2

[Comment 6 Toralf Förster 2017-03-19 08:30:19 UTC]

Created attachment 467538 [details]
temp.tbz2

[Comment 7 Zac Medico 2017-03-19 23:55:00 UTC]

If it's the same problem as this, then you need to rebuild llvm with your current version of gcc:

https://github.com/iovisor/bcc/issues/721

[Comment 8 Toralf Förster 2017-03-20 18:28:28 UTC]

(In reply to Zac Medico from comment #7)

I'm unsure if it is the smae or not - llvm was just installed once - look at the attached emerge history :
Sat Mar 18 06:49:33 2017 >>> sys-devel/llvm-4.0.0

[Comment 9 Andreas K. Hüttel 2017-04-16 19:57:53 UTC]

Not stable, can't block a stabilization

[Comment 10 Zac Medico 2017-04-20 22:08:29 UTC]

(In reply to Toralf Förster from comment #8)
> (In reply to Zac Medico from comment #7)
> 
> I'm unsure if it is the smae or not - llvm was just installed once - look at
> the attached emerge history :
> Sat Mar 18 06:49:33 2017 >>> sys-devel/llvm-4.0.0

The emerge history will not tell us when you used gcc-config to switch your compiler from gcc-4.9.x to gcc-5.x, but we can probably see the compiler in the llvm-4.0.0 build log if you have that.

[Comment 11 Toralf Förster 2017-04-21 16:35:48 UTC]

(In reply to Zac Medico from comment #10)
oh - the switch to the new compiler is made immediately after "emerge -u gcc"

[Comment 12 Patrick McLean 2020-08-25 00:47:06 UTC]

This is fixed in newer releases.