All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Dominig Ar Foll <dominig.arfoll@fridu.net>
Cc: yocto@yoctoproject.org
Subject: Re: Enabling tpm from meta-security for AGL
Date: Fri, 05 May 2017 12:41:21 +0200	[thread overview]
Message-ID: <1493980881.4241.305.camel@intel.com> (raw)
In-Reply-To: <CADG2P4U7wOSsHwB0Wt3nzejWvRi5h2TOLFB9TcrK+b7pNYje-A@mail.gmail.com>

On Fri, 2017-05-05 at 12:12 +0200, Dominig Ar Foll wrote:
> Hello,
> 
> I am trying to enable tpm on an Intel target using yocto (morty) from
> meta-security
> 
> When I activate the tpm-tools-2.0 feature in my configuration, I have
> a compilation error (see log bellow)
> Search for line:
> | /usr/src/debug/glibc/2.24-r0/git/csu/../sysdeps/x86_64/start.S:104:
> undefined reference to `main'

g++ ends up trying to link an executable instead of a shared objection.
If I remember correctly, -fstack-protector-strong in CFLAGS causes that.
The order of parameters must be ${CFLAGS) $(LDFLAGS).

I've tried with meta-security master and it doesn't happen there, so
perhaps it was already fixed.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2017-05-05 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 10:12 Enabling tpm from meta-security for AGL Dominig Ar Foll
2017-05-05 10:41 ` Patrick Ohly [this message]
2017-05-05 12:45 ` Khem Raj
2017-05-05 13:13   ` Patrick Ohly
2017-05-05 13:14     ` Khem Raj

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=1493980881.4241.305.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=dominig.arfoll@fridu.net \
    --cc=yocto@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 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.