mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] tpm2-tss: Version bump. 2.3.1 -> 3.1.0
Date: Sat, 29 Jan 2022 16:36:28 +0100	[thread overview]
Message-ID: <20220129153628.GG11273@pengutronix.de> (raw)
In-Reply-To: <36c721f5-a9cc-d55c-cde3-1fa9a0568053@t2data.com>

On Sat, Jan 29, 2022 at 09:29:43AM +0100, Christian Melki wrote:
> On 1/28/22 19:32, Michael Olbrich wrote:
> > On Fri, Jan 28, 2022 at 06:22:19PM +0100, Christian Melki wrote:
> >> On 1/28/22 17:16, Michael Olbrich wrote:
> >>> On Thu, Jan 27, 2022 at 03:35:30PM +0100, Christian Melki wrote:
> >>>> Approx. 2,5 year worth of fixes.
> >>>> https://github.com/tpm2-software/tpm2-tss/releases
> >>>> Fixes CVE-2020-24455 (three times over).
> >>>> tpm2-tss now depends on JSON_C and LIBCURL.
> >>>> Remove changed configuration options.
> >>>
> >>> Fails to build here:
> >>>
> >>> checking for groupadd... no
> >>> configure: error: Missing required program 'groupadd': ensure it is installed and on PATH.
> >>>
> >>> Adding a group should not be done during install anyways and it would fail,
> >>> so I think this should work:
> >>>
> >>> TPM2_TSS_CONF_ENV := \
> >>> 	$(CROSS_ENV) \
> >>> 	GROUPADD=: \
> >>> 	USERADD=:
> >>>
> >>> Michael
> >>>
> >>
> >> Didn't see that one coming. How abusive!
> >> From a makefile none the less.
> >> I have the required binaries on my development machine so I didn't notice.
> >> Now, I've tried your suggestion, but I can't see that it helps?
> >>
> >> Looks like the entire thing goes about the binaries in a very static
> >> fashion.
> >>
> >> ..
> >> define make_tss_user_and_group
> >>     (id -g tss 2>/dev/null || groupadd -r tss) && \
> >>     (id -u tss 2>/dev/null || useradd -r -g tss tss)
> >> endef
> > 
> > 	@$(call make_tss_user_and_group) || echo "WARNING Failed to create the tss user and group"
> > 
> > so any error here is ignored. We just need to get through the configure
> > check.
> > 
> 
> ack.
> 
> TPM2_TSS_CONF_ENV := \
>         $(CROSS_ENV) \
>         ac_cv_prog_result_groupadd=yes \
>         ac_cv_prog_result_useradd=yes
> 
> should work for getting through configure?

I think so. You should see a "(cached)" in the configure output for those
checks.

Michael


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


  reply	other threads:[~2022-01-29 15:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 14:35 [ptxdist] [PATCH] wpa_supplicant: Version bump 2.9 -> 2.10 Christian Melki
2022-01-27 14:35 ` [ptxdist] [PATCH] efivar: Version bump 37 -> 38 Christian Melki
2022-01-28 10:17   ` Michael Olbrich
2022-01-27 14:35 ` [ptxdist] [PATCH] sysklogd: Version bump. 2.2.3 -> 2.3.0 Christian Melki
2022-01-30 15:49   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-27 14:35 ` [ptxdist] [PATCH] dump1090fa: Version bump 6.1 -> 7.1 Christian Melki
2022-01-27 15:56   ` Bruno Thomsen
2022-01-27 16:31     ` Christian Melki
2022-01-28  9:37       ` Michael Olbrich
2022-01-27 14:35 ` [ptxdist] [PATCH] chrony: Version bump. 4.1 -> 4.2 Christian Melki
2022-01-30 15:49   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-27 14:35 ` [ptxdist] [PATCH] strace: Version bump. 5.15 -> 5.16 Christian Melki
2022-01-28  9:19   ` Michael Olbrich
2022-01-27 14:35 ` [ptxdist] [PATCH] alsa-lib: Version bump 1.2.5.1 -> 1.2.6.1 Christian Melki
2022-01-30 15:49   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-27 14:35 ` [ptxdist] [PATCH] alsa-utils: Version bump 1.2.5.1 -> 1.2.6 Christian Melki
2022-01-30 15:49   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-27 14:35 ` [ptxdist] [PATCH] libsndfile: Version bump 1.0.25 -> 1.0.31 Christian Melki
2022-01-28 12:46   ` Michael Olbrich
2022-01-27 14:35 ` [ptxdist] [WIP: PATCH] pps-tools: Version bump. 1.0.2 -> 1.0.3 Christian Melki
2022-01-28  9:26   ` Michael Olbrich
2022-01-28  9:39     ` Christian Melki
2022-01-28 10:36       ` Michael Olbrich
2022-01-27 14:35 ` [ptxdist] [PATCH] tpm2-tss: Version bump. 2.3.1 -> 3.1.0 Christian Melki
2022-01-28 16:16   ` Michael Olbrich
2022-01-28 17:22     ` Christian Melki
2022-01-28 18:32       ` Michael Olbrich
2022-01-29  8:29         ` Christian Melki
2022-01-29 15:36           ` Michael Olbrich [this message]
2022-01-27 14:35 ` [ptxdist] [PATCH] tpm2-tools: Version bump. 4.1 -> 5.2 Christian Melki
2022-01-27 15:54   ` Bruno Thomsen
2022-01-28  9:31     ` Michael Olbrich
2022-01-28 13:33       ` Christian Melki
2022-01-28 14:56         ` Michael Olbrich
2022-01-27 14:35 ` [ptxdist] [PATCH] ncurses: Version bump. 6.2 -> 6.3 Christian Melki
2022-01-30 15:49   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-30 15:49 ` [ptxdist] [APPLIED] wpa_supplicant: Version bump 2.9 -> 2.10 Michael Olbrich

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=20220129153628.GG11273@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --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