mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: Bastian Krause <bst@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v3 2/3] tpm2-tools: version bump 3.1.4 -> 4.1
Date: Tue, 7 Jan 2020 15:44:43 +0100	[thread overview]
Message-ID: <CAH+2xPBKn+-ufmg1C+=jkTgup-aVdG121wTVbs3-amb8d7qj6A@mail.gmail.com> (raw)
In-Reply-To: <5895f066-b529-5258-7ee8-e42ea2d990fa@pengutronix.de>

Hi Bastian,

Den man. 6. jan. 2020 kl. 15.41 skrev Bastian Krause <bst@pengutronix.de>:
>
> >>> TPM2_TOOLS_CFLAGS := \
> >>>     -fPIC
> >>>
> >>>
> >>> I don't know if this is the correct fix or something else is the root cause.
> >>
> >> Looks okay to me. Let's wait what Michael has to say about it.
> >
> > That makes sense to me. I think this should be handled correctly
> > internally, but I think for a lot if distributions that's already the
> > default in the toolchain, so it does not fail there.
>
> Alright. Bruno, could you send this as a proper patch?

Yes, I can do that.

Bruno

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2020-01-07 14:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 11:51 [ptxdist] [PATCH v3 1/3] tpm2-tss: version bump 2.2.2 -> 2.3.1 Bastian Krause
2019-11-29 11:51 ` [ptxdist] [PATCH v3 2/3] tpm2-tools: version bump 3.1.4 -> 4.1 Bastian Krause
2019-12-17 15:16   ` Bruno Thomsen
2019-12-18  8:57     ` Bastian Krause
2020-01-06 11:24       ` Michael Olbrich
2020-01-06 14:41         ` Bastian Krause
2020-01-07 14:44           ` Bruno Thomsen [this message]
2019-11-29 11:51 ` [ptxdist] [PATCH v3 3/3] tpm2-abrmd: version bump 2.1.1 -> 2.3.0 Bastian Krause

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='CAH+2xPBKn+-ufmg1C+=jkTgup-aVdG121wTVbs3-amb8d7qj6A@mail.gmail.com' \
    --to=bruno.thomsen@gmail.com \
    --cc=bst@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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