On 21.03.22 07:14, Jan Kiszka wrote:
> From: Jan Kiszka <[email protected]>
> 
> For x86_64 and aarch64, we rely on ARCH having no suffix anyway. So,
> avoid confusion of the reader by matching on the full arch string.
> 
> Signed-off-by: Jan Kiszka <[email protected]>
> ---
>  configure.ac | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/configure.ac b/configure.ac
> index 09d06d7..31340ae 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -82,11 +82,11 @@ AC_SUBST(GNUEFI_LIB_DIR)
>  AC_DEFINE_UNQUOTED(GNUEFI_LIB_DIR, ["$GNUEFI_LIB_DIR"], [The lib directory 
> for gnuefi])
>  
>  dnl Define ARCH_<NAME> conditionals
> -SET_ARCH(I586, i586*)
> -SET_ARCH(I686, i686*)
> -SET_ARCH(X86_64, x86_64*)
> -SET_ARCH(IA64, ia64*)
> -SET_ARCH(AARCH64, aarch64*)
> +SET_ARCH(I586, i586)
> +SET_ARCH(I686, i686)
> +SET_ARCH(X86_64, x86_64)
> +SET_ARCH(IA64, ia64)
> +SET_ARCH(AARCH64, aarch64)
>  
>  ARCH=$(echo $host | sed "s/\(-\).*$//")
>  

This one was pre-coffee non-sense: The suffix cut-off happens after the
match and has no impact on it. I'm dropping this patch.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux

-- 
You received this message because you are subscribed to the Google Groups "EFI 
Boot Guard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/efibootguard-dev/47e1a5c1-f3d3-5ae0-93d0-7c7b0c281fe6%40siemens.com.

Reply via email to