Building RISC-V BSP

Hesham Almatary heshamelmatary at gmail.com
Tue May 30 20:16:27 UTC 2017


Hi Denis,

Yes, that's a leftover flag that used to exist in the 2-year-old
toolchain. There's no m32 (or m64) flag anymore. I submitted a fix
(54bf80e) to my repo. You'll most likely get similar issues though in
later stages. Fix-ups are welcome.

Cheers,
Hesham

On Wed, May 31, 2017 at 3:19 AM, Gedare Bloom <gedare at rtems.org> wrote:
> On Tue, May 30, 2017 at 12:09 PM, Denis Obrezkov
> <denisobrezkov at gmail.com> wrote:
>> 2017-05-30 18:31 GMT+03:00 Gedare Bloom <gedare at rtems.org>:
>>>
>>> On Tue, May 30, 2017 at 7:49 AM, Denis Obrezkov <denisobrezkov at gmail.com>
>>> wrote:
>>> > Hello,
>>> > I am trying to build RTEMS for RISC-V BSP. I applied Hesham's patch for
>>> > RSB
>>> > and built RSB. But when I am trying to build rtems-generic target I get
>>> > the
>>> > mistake.
>>> > This is my sequence of steps:
>>> >
>>> > git clone git://git.rtems.org/rtems-source-builder.git
>>> >
>>> > #patch applied here
>>> >
>>> > mkdir -p ./development/rtems/kernel
>>> >
>>> > cd ./development/rtems/kernel
>>> >
>>> > export RTEMS_DEV=~Projects/riscv/rtems/development
>>> >
>>> > git clone https://github.com/heshamelmatary/rtems-riscv.git
>>> >
>>> > cd ..
>>> >
>>> > mkdir rsb
>>> >
>>> > mv ../../rtems-source-builder/ ./rsb/
>>> >
>>> > cd rsb/rtems-source-builder/rtems/
>>> >
>>> > ../source-builder/sb-set-builder --prefix=$RTEMS_DEV/rtems/4.12
>>> > 4.12/rtems-riscv32
>>> >
>>> is $RTEMS_DEV/rtems/4.12/bin in your $PATH?
>>>
>> You are right, somehow it wasn't there.
>>
>> Now I have another issue during make:
>>
>> checking for RTEMS_CPU_MODEL...
>> checking for RTEMS_BSP_FAMILY... riscv_generic
>> checking for CPU_CFLAGS... (cached) -m32 -march=I
>> checking for CFLAGS_OPTIMIZE_V... (cached) -O0 -g
>> checking for style of include used by make... GNU
>> checking for riscv32-rtems4.12-gcc... riscv32-rtems4.12-gcc
>> checking for riscv32-rtems4.12-gcc... (cached) riscv32-rtems4.12-gcc
>> checking whether the C compiler works... no
>> configure: error: in
>> `/home/reprofy/Projects/riscv/rtems/development/rtems/kernel/riscv32/riscv32-rtems4.12/c/riscv_generic':
>> configure: error: C compiler cannot create executables
>>
>> Now I can see the error - there is no such an option "-m32" in 32-bit gcc.
>> But what does "(cached)" mean?
>>
> I think it means configure previously made this check and uses the
> cached result of the previous check.
>
>>
>>
>> --
>> Regards, Denis Obrezkov



-- 
Hesham


More information about the devel mailing list