Re: [Rpm-maint] [rpm-software-management/rpm] Add architecture macro for all RISC-V processors (#1036)

2020-02-03 Thread Florian Festi
Merged #1036 into master. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/1036#event-3005044854___ Rpm-maint mailing list

Re: [Rpm-maint] [rpm-software-management/rpm] Add architecture macro for all RISC-V processors (#1036)

2020-02-03 Thread David Abdurachmanov
Forgot to mention. OpenEmbedded already supports riscv32 IIRC and it also supports RPM packaging. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Add architecture macro for all RISC-V processors (#1036)

2020-02-03 Thread David Abdurachmanov
32b is a thing even if some distributions don't have current plans to support it. It might be especially popular in buildroot and OpenEmbedded for embedded Linux based RV32 systems, but that markets could be more complicated. I mean most of such available soft cores probably don't support

Re: [Rpm-maint] [rpm-software-management/rpm] Add architecture macro for all RISC-V processors (#1036)

2020-02-03 Thread ニール・ゴンパ
@rwmjones In OpenMandriva, there was some interest in building the different variants (including 32-bit stuff), so for a bit of future-proofing, we've gone ahead and made the same architecture macro structure as ARM, MIPS, and POWER have to simplify future work. -- You are receiving this

Re: [Rpm-maint] [rpm-software-management/rpm] Add architecture macro for all RISC-V processors (#1036)

2020-02-03 Thread rwmjones
... which is not to say that I'm opposing this change, just pointing out some stuff. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Add architecture macro for all RISC-V processors (#1036)

2020-02-03 Thread rwmjones
I'm confused why we need the `%{riscv32}`/64/128 macros at all. They don't seem to be necessary for this change unless there's something about how RPM macros work which I don't understand. The `%{riscv}` macro seems as if it would be useful to mean "all RISC-V architectures". Although I will

Re: [Rpm-maint] [rpm-software-management/rpm] Add architecture macro for all RISC-V processors (#1036)

2020-02-03 Thread rwmjones
Adding @davidlt -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/1036#issuecomment-581346762___ Rpm-maint mailing list

Re: [Rpm-maint] [rpm-software-management/rpm] Add architecture macro for all RISC-V processors (#1036)

2020-02-03 Thread Panu Matilainen
Looks sane to me, but then I know absolutely nothing about this arch. @rwmjones , any thoughts/comments? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[Rpm-maint] [rpm-software-management/rpm] Add architecture macro for all RISC-V processors (#1036)

2020-02-01 Thread ニール・ゴンパ
This makes it easier to reference all RISC-V architectures supported by RPM in the same way that ARM and POWER architectures are. You can view, comment on, or merge this pull request online at: https://github.com/rpm-software-management/rpm/pull/1036 -- Commit Summary -- * Add architecture