gustavonihei edited a comment on pull request #3836: URL: https://github.com/apache/incubator-nuttx/pull/3836#issuecomment-856727916
> riscv64-unknown-elf-gcc: error: unrecognized command line option '-melf32lriscv' I saw that you passed the flag to GCC as `-Wl,-m,elf32lriscv`, I believe the second comma might not be necessary. > Something strange happens with riscv boards. The github workflow tries to build some configurations, which I cannot configure locally. > > On github > > ``` > ==================================================================================== > Configuration/Tool: esp32c3-devkit/elf,CONFIG_RV32IM_TOOLCHAIN_GNU_RVGL > ------------------------------------------------------------------------------------ > Cleaning... > Configuring... > Disabling CONFIG_RV32IM_TOOLCHAIN_GNU_RVGL > Enabling CONFIG_RV32IM_TOOLCHAIN_GNU_RVGL > Building NuttX... > riscv64-unknown-elf-gcc: error: unrecognized command line option '-melf32lriscv' > make[5]: *** [Makefile:70: errno] Error 1 > ``` > > Locally > > ``` > tools/configure.sh esp32c3-devkit:elf > Directory for esp32c3-devkit:elf does not exist. > ``` > > Ok, these configurations have been created recently. But why does the workflow build against them? My branch doesn't have them. Should I merge from master? But how the pull-request system will treat this merge? The CI always builds the branch after rebasing it to the HEAD of the target repository, which in this case is the **master**. So, in order to correctly build this new `elf` configuration, it is recommended that you do the same, because a recent commit created some new variables: https://github.com/apache/incubator-nuttx/commit/dd4962b2f8d3d98d5bef03b433c32fdd1bc62340 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
