Enable riscv64 for ppa:xypron/nezha

Asked by Heinrich Schuchardt

Please, enable the RISC-V build architecture for ppa:xypron/nezha.

Best regards

Heinrich

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Heinrich Schuchardt
Solved:
Last query:
Last reply:
Revision history for this message
Colin Watson (cjwatson) said :
#1

Done.

Revision history for this message
Heinrich Schuchardt (xypron) said :
#2

Hello Colin,

thanks for adding the flag. But the ppa only builds amd64 though
debian/control has 'Architecture: all'.

Best regards

Heinrich

On Mon, Oct 4, 2021 at 1:25 PM Colin Watson <
<email address hidden>> wrote:

> Your question #698955 on Launchpad itself changed:
> https://answers.launchpad.net/launchpad/+question/698955
>
> Status: Open => Answered
>
> Colin Watson proposed the following answer:
> Done.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/launchpad/+question/698955/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/launchpad/+question/698955
>
> You received this question notification because you asked the question.
>

Revision history for this message
Colin Watson (cjwatson) said :
#3

"Architecture: all" means that the source package is *built* on a single architecture (typically amd64) and that build is then *published* for all architectures. If you want it to be built separately on all supported architectures, use "Architecture: any".

Revision history for this message
William Grant (wgrant) said :
#4

If you do want a single binary across all architectures, which is not uncommon for firmware, you should either use a cross-compiler or, if that's not possible, set `XS-Build-Indep-Architecture: riscv64` to hint where the `Architecture: all` binary should be built.

Revision history for this message
Heinrich Schuchardt (xypron) said :
#5

The problem is solved. Thanks.