* next-nofpu build breakage @ 2018-10-17 2:01 Jim Wilson 2018-10-17 2:01 ` Jim Wilson 2018-10-17 18:44 ` Palmer Dabbelt 0 siblings, 2 replies; 4+ messages in thread From: Jim Wilson @ 2018-10-17 2:01 UTC (permalink / raw) To: linux-riscv Building from Palmer's for-next branch gives an error for an invalid -march option. This bug came in via the next-nofpu branch. In arch/riscv/Makefile I had to change riscv-march-$(CONFIG_FPU) := fd to riscv-march-$(CONFIG_FPU) := $(riscv-march-y)fd to get past this problem. Jim ^ permalink raw reply [flat|nested] 4+ messages in thread
* next-nofpu build breakage 2018-10-17 2:01 next-nofpu build breakage Jim Wilson @ 2018-10-17 2:01 ` Jim Wilson 2018-10-17 18:44 ` Palmer Dabbelt 1 sibling, 0 replies; 4+ messages in thread From: Jim Wilson @ 2018-10-17 2:01 UTC (permalink / raw) To: linux-riscv Building from Palmer's for-next branch gives an error for an invalid -march option. This bug came in via the next-nofpu branch. In arch/riscv/Makefile I had to change riscv-march-$(CONFIG_FPU) := fd to riscv-march-$(CONFIG_FPU) := $(riscv-march-y)fd to get past this problem. Jim _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv ^ permalink raw reply [flat|nested] 4+ messages in thread
* next-nofpu build breakage 2018-10-17 2:01 next-nofpu build breakage Jim Wilson 2018-10-17 2:01 ` Jim Wilson @ 2018-10-17 18:44 ` Palmer Dabbelt 2018-10-17 18:44 ` Palmer Dabbelt 1 sibling, 1 reply; 4+ messages in thread From: Palmer Dabbelt @ 2018-10-17 18:44 UTC (permalink / raw) To: linux-riscv On Tue, 16 Oct 2018 19:01:10 PDT (-0700), Jim Wilson wrote: > Building from Palmer's for-next branch gives an error for an invalid > -march option. This bug came in via the next-nofpu branch. In > arch/riscv/Makefile I had to change > riscv-march-$(CONFIG_FPU) := fd > to > riscv-march-$(CONFIG_FPU) := $(riscv-march-y)fd > to get past this problem. Thanks. Someone else had pointed this out as well, it turns out I'd merged the wrong version of a patch set. This should be fix on both next-nofpu and for-next now. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: next-nofpu build breakage 2018-10-17 18:44 ` Palmer Dabbelt @ 2018-10-17 18:44 ` Palmer Dabbelt 0 siblings, 0 replies; 4+ messages in thread From: Palmer Dabbelt @ 2018-10-17 18:44 UTC (permalink / raw) To: Jim Wilson; +Cc: linux-riscv On Tue, 16 Oct 2018 19:01:10 PDT (-0700), Jim Wilson wrote: > Building from Palmer's for-next branch gives an error for an invalid > -march option. This bug came in via the next-nofpu branch. In > arch/riscv/Makefile I had to change > riscv-march-$(CONFIG_FPU) := fd > to > riscv-march-$(CONFIG_FPU) := $(riscv-march-y)fd > to get past this problem. Thanks. Someone else had pointed this out as well, it turns out I'd merged the wrong version of a patch set. This should be fix on both next-nofpu and for-next now. _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-10-17 18:45 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-10-17 2:01 next-nofpu build breakage Jim Wilson 2018-10-17 2:01 ` Jim Wilson 2018-10-17 18:44 ` Palmer Dabbelt 2018-10-17 18:44 ` Palmer Dabbelt
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).