On Tue, Aug 09 2022, Stuart Henderson wrote:
> On 2022/08/09 02:10, Jeremie Courreges-Anglas wrote:
>> > Another approach with more explicit code would be to use a variable in
>> > the file names, that variable would hold either "rv64", "64" or "32"
>> > depending on the arch.
>>
>> That would gi
Jeremie Courreges-Anglas wrote:
> On Tue, Aug 09 2022, Jeremie Courreges-Anglas wrote:
> > Another diff I have used on riscv64 bulk build cluster since some
> > weeks/months. The executables are named differently on riscv64.
> >
> > The SConstruct file has this logic:
> >
> > if env["arch"]
On 2022/08/09 02:10, Jeremie Courreges-Anglas wrote:
> > Another approach with more explicit code would be to use a variable in
> > the file names, that variable would hold either "rv64", "64" or "32"
> > depending on the arch.
>
> That would give something like the diff below (tested on riscv64 a
On Tue, Aug 09 2022, Jeremie Courreges-Anglas wrote:
> Another diff I have used on riscv64 bulk build cluster since some
> weeks/months. The executables are named differently on riscv64.
>
> The SConstruct file has this logic:
>
> if env["arch"] != "":
> suffix += "." + env["arch"]
>
Another diff I have used on riscv64 bulk build cluster since some
weeks/months. The executables are named differently on riscv64.
The SConstruct file has this logic:
if env["arch"] != "":
suffix += "." + env["arch"]
elif env["bits"] == "32":
suffix += ".32"
elif env