[PATCH] build: Check for cargo when building rust language

From: Pierre-Emmanuel Patry Hello, The rust frontend requires cargo to build some of it's components, it's presence was not checked during configuration. Best regards, Pierre-Emmanuel -- Prevent rust language from building when cargo is missing. config/ChangeLog:

Re: libgrust: 'AM_ENABLE_MULTILIB' only for target builds [PR113056]

Hello Thomas, On 12/18/23 17:58, Thomas Schwinge wrote: --- a/libgrust/configure.ac +++ b/libgrust/configure.ac -# AM_ENABLE_MULTILIB(, ..) +AM_ENABLE_MULTILIB(, ..) Such a change was applied eventually, and is necessary for target builds -- but potentially harmful for host builds. OK to

Re: build: Don't check for host-prefixed 'cargo' program

Hi, On 4/15/24 1:50 PM, Thomas Schwinge wrote: I now wonder: instead of 'AC_CHECK_TOOL', shouldn't this use 'AC_CHECK_PROG'? (We always want plain 'cargo', not host-prefixed 'aarch64-linux-gnu-cargo' etc., right?) I'll look into changing this. This is a mistake, we should use 'AC_CHECK_PROG'

Re: build: Use of cargo not yet supported here in Canadian cross configurations

Hello, On 4/15/24 2:44 PM, Thomas Schwinge wrote: On top of that, OK to push the attached "build: Use of cargo not yet supported here in Canadian cross configurations"? This additional patch looks good. I wonder whether we should enable canadian cross in the future with cargo or simply wait f

[PATCH v2] Handle non default git prefix configurations

: Force default git prefixes. Signed-off-by: Pierre-Emmanuel Patry --- contrib/prepare-commit-msg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/prepare-commit-msg b/contrib/prepare-commit-msg index 1b878772dcc..75d102559c7 100755 --- a/contrib/prepare-commit-msg

Re: [PATCH] Handle non default git configurations with mklog

On 7/7/25 3:41 PM, Alexander Monakov wrote: Is switching the algorithm actually necessary for solving the problem at hand? I think it is possible for the default algorithm to produce diffs that lead to poorly generated changelog entries, so forcing it here seems undesirable. I was not aware of

[PATCH] Handle non default git configurations with mklog

/ChangeLog: * prepare-commit-msg: Force default git prefixes and algorithm usage. Signed-off-by: Pierre-Emmanuel Patry --- contrib/prepare-commit-msg | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/contrib/prepare-commit-msg b/contrib/prepare-commit-msg index