yocto.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Mittal, Anuj" <anuj.mittal@intel.com>
To: "steven.monsees@baesystems.com" <steven.monsees@baesystems.com>,
	"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] #zeus meta-intel
Date: Thu, 14 Oct 2021 01:27:34 +0000	[thread overview]
Message-ID: <5adffd49d0ac93ea0953696ccb2ace88f09b9e05.camel@intel.com> (raw)
In-Reply-To: <9e8b91$7f8sbe@mga01.intel.com>

There are no patches needed other than what is already in oe-core/meta-
intel/meta-clang. I tried building zeus on Ubuntu 16.04 and didn't see
any problem.

zeus is no longer maintained or supported so I'd suggest checking a
newer release or experimenting without using buildtools to see if that
is exposing this problem. It does look like things are not being
compiled properly or perhaps opencl-clang-native is linking to
incorrect LLVM ... 

Thanks,

Anuj

On Wed, 2021-10-13 at 16:53 +0000, Monsees, Steven C (US) wrote:
> 
> Anything ?, I have yet to resolve this.
> 
> -----Original Message-----
> From: Monsees, Steven C (US) 
> Sent: Wednesday, October 13, 2021 9:03 AM
> To: 'Mittal, Anuj' <anuj.mittal@intel.com>;
> 'yocto@lists.yoctoproject.org' <yocto@lists.yoctoproject.org>
> Subject: RE: [yocto] #zeus meta-intel
> 
> 
> Are there any patches required for these components (igc, opencl-
> clang, and intel-compute-runtime) ?
> 
> -----Original Message-----
> From: Monsees, Steven C (US) 
> Sent: Wednesday, October 13, 2021 7:13 AM
> To: 'Mittal, Anuj' <anuj.mittal@intel.com>;
> yocto@lists.yoctoproject.org
> Subject: RE: [yocto] #zeus meta-intel
> 
> 
> Anuj:
> 
> I rebuilt the entire image (but did not delete the state_cache)...
> I am building meta-clang (zeus based, I believe it is 9.0.1).
> 
> Steve
> 
> -----Original Message-----
> From: Mittal, Anuj <anuj.mittal@intel.com>
> Sent: Tuesday, October 12, 2021 10:10 PM
> To: Monsees, Steven C (US) <steven.monsees@baesystems.com>;
> yocto@lists.yoctoproject.org
> Subject: Re: [yocto] #zeus meta-intel
> 
> External Email Alert
> 
> This email has been sent from an account outside of the BAE Systems
> network.
> 
> Please treat the email with caution, especially if you are requested
> to click on a link, decrypt/open an attachment, or enable macros. 
> For further information on how to spot phishing, access
> “Cybersecurity OneSpace Page” and report phishing by clicking the
> button “Report Phishing” on the Outlook toolbar.
> 
> 
> Did you build everything with this compiler from start? Is opencl-
> clang building with the right LLVM lib from meta-clang?
> 
> Thanks,
> 
> Anuj
> 
> On Tue, 2021-10-12 at 17:15 +0000, Monsees, Steven C (US) wrote:
> > 
> > Anuj:
> > 
> > I picked up the tarball for for the baseline dunfell tools platform
> > to 
> > update host tools...
> > 
> > I am seeing it compile cleaner but for one issue causng ld to fail:
> > 
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1331:
> > undefined reference to `vtable for
> > llvm::cl::opt<std::__cxx11::basic_string<char,
> > std::char_traits<char>, 
> > std::allocator<char> >, false, 
> > llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > > >'
> > 
> > Isn't LLVM brought in along with clang under meta-clang ?
> > 
> > Is there a missing build dependency ?
> > 
> > Thanks,
> > Steve
> > 
> > Build excerpt showing multiple " undefined reference to `vtable "
> > errors...
> > 
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::opt<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> >, false, 
> > llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > > >::~opt()':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1331:
> > undefined reference to `vtable for
> > llvm::cl::opt<std::__cxx11::basic_string<char,
> > std::char_traits<char>, 
> > std::allocator<char> >, false, 
> > llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::OptionValue<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > >::OptionValue()':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:601:
> > undefined reference to `vtable for
> > llvm::cl::OptionValue<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::opt<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> >, false, 
> > llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > >
> > > ::opt<llvm::cl::FormattingFlags, llvm::cl::desc,
> > llvm::cl::desc const&, llvm::cl::initializer<char [2]> const&)':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1407:
> > undefined reference to `vtable for
> > llvm::cl::opt<std::__cxx11::basic_string<char,
> > std::char_traits<char>, 
> > std::allocator<char> >, false, 
> > llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> >
> > > ::parser(llvm::cl::Option&)':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1072:
> > undefined reference to `vtable for
> > llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::opt<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> >, false, 
> > llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > > >::~opt()':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1331:
> > undefined reference to `vtable for
> > llvm::cl::opt<std::__cxx11::basic_string<char,
> > std::char_traits<char>, 
> > std::allocator<char> >, false, 
> > llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::OptionValue<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > >::OptionValue()':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:601:
> > undefined reference to `vtable for
> > llvm::cl::OptionValue<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::opt<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> >, false, 
> > llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > > >::opt<char [9], 
> > llvm::cl::desc>(char const (&) [9], llvm::cl::desc const&)':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1407:
> > undefined reference to `vtable for
> > llvm::cl::opt<std::__cxx11::basic_string<char,
> > std::char_traits<char>, 
> > std::allocator<char> >, false, 
> > llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> >
> > > ::parser(llvm::cl::Option&)':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1072:
> > undefined reference to `vtable for
> > llvm::cl::parser<std::__cxx11::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > >'
> > collect2: error: ld returned 1 exit status
> > 
> > -----Original Message-----
> > From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org>
> > On 
> > Behalf Of Anuj Mittal
> > Sent: Tuesday, October 12, 2021 10:43 AM
> > To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; 
> > yocto@lists.yoctoproject.org
> > Subject: Re: [yocto] #zeus meta-intel
> > 
> > External Email Alert
> > 
> > network.
> > 
> > Please treat the email with caution, especially if you are
> > requested 
> > to click on a link, decrypt/open an attachment, or enable macros. 
> > For 
> > further information on how to spot phishing, access “Cybersecurity 
> > OneSpace Page” and report phishing by clicking the button “Report 
> > Phishing” on the Outlook toolbar.
> > 
> > 
> > On Tue, 2021-10-12 at 12:43 +0000, Monsees, Steven C (US) wrote:
> > > g++: error: unrecognized command line option ‘-std=c++14’
> > 
> > It looks like the gcc version is too old on your host for this to
> > work.
> > 
> > Thanks,
> > 
> > Anuj
> 


       reply	other threads:[~2021-10-14  1:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9e8b91$7f8sbe@mga01.intel.com>
2021-10-14  1:27 ` Mittal, Anuj [this message]
2021-10-14 10:49   ` [yocto] #zeus meta-intel Monsees, Steven C (US)
2021-10-19 19:17   ` Monsees, Steven C (US)
2021-10-13 16:53 Monsees, Steven C (US)
  -- strict thread matches above, loose matches on Subject: below --
2021-10-13 13:03 Monsees, Steven C (US)
     [not found] <561a5d$6c7l18@mga18.intel.com>
2021-10-13  2:10 ` Mittal, Anuj
2021-10-13 11:12   ` Monsees, Steven C (US)
     [not found] <83b8bb$6ndulk@mga04.intel.com>
2021-10-12 14:42 ` Mittal, Anuj
2021-10-12 17:15   ` Monsees, Steven C (US)
     [not found] <MADEUP.16AD44B3D74AA38E.8938@lists.yoctoproject.org>
2021-10-12 12:43 ` Monsees, Steven C (US)
     [not found] <MADEUP.16AC1A1B0F173D71.20366@lists.yoctoproject.org>
2021-10-09  3:04 ` Mittal, Anuj
2021-10-12 11:21   ` Monsees, Steven C (US)
     [not found] <036a98$65nf6t@mga17.intel.com>
2021-10-08 16:01 ` Mittal, Anuj
2021-10-08 16:10   ` Monsees, Steven C (US)
     [not found] <MADEUP.16ABCC21AC1C56E0.1166@lists.yoctoproject.org>
2021-10-08 15:07 ` Mittal, Anuj
2021-10-08 15:30   ` Monsees, Steven C (US)

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=5adffd49d0ac93ea0953696ccb2ace88f09b9e05.camel@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=steven.monsees@baesystems.com \
    --cc=yocto@lists.yoctoproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).