On 14/11/2019 10:53, Hesham Almatary wrote:
To which directory NEWLIB_SYSROOT in the /opt/rtems/5 installation tree
must this point?
riscv-rtems5. Or the corresponding multilib directory for your RISC-V BSP.
So, if I use --sysroot=/opt/rtems/5/riscv-rtems5, then clang will pick
up /opt/rtems/5
On Thu, 14 Nov 2019 at 07:27, Sebastian Huber
wrote:
>
> Hello Hesham,
>
> On 13/11/2019 16:32, Hesham Almatary wrote:
> > On Wed, 13 Nov 2019 at 14:48, Sebastian Huber
> > wrote:
> >>
> >> Hello Hesham,
> >>
> >> On 23/10/2019 15:50, Hesham Almatary wrote:
> >>> Hi,
> >>>
> >>> I submitted a RFC
Hello Hesham,
On 13/11/2019 16:32, Hesham Almatary wrote:
On Wed, 13 Nov 2019 at 14:48, Sebastian Huber
wrote:
Hello Hesham,
On 23/10/2019 15:50, Hesham Almatary wrote:
Hi,
I submitted a RFC patch series to be able to build RTEMS/RISC-V with
LLVM/Clang. I'd appreciate your feedback on that
On Wed, 13 Nov 2019 at 14:48, Sebastian Huber
wrote:
>
> Hello Hesham,
>
> On 23/10/2019 15:50, Hesham Almatary wrote:
> > Hi,
> >
> > I submitted a RFC patch series to be able to build RTEMS/RISC-V with
> > LLVM/Clang. I'd appreciate your feedback on that.
> >
> > A sample configure line to build
Hello Hesham,
On 23/10/2019 15:50, Hesham Almatary wrote:
Hi,
I submitted a RFC patch series to be able to build RTEMS/RISC-V with
LLVM/Clang. I'd appreciate your feedback on that.
A sample configure line to build RTEMS with LLVM/Clang is:
../rtems/configure --target=riscv-rtems6
--enable-rte
On 29/10/19 12:51 am, Hesham Almatary wrote:
> On Mon, 28 Oct 2019 at 10:33, Sebastian Huber
> wrote:
>>
>> On 28/10/2019 11:16, Hesham Almatary wrote:
>>> Hi Sebastian,
>>>
>>> The *_clang ones aren't expected to be compiled by GCC (and the native
>>> *.cfg won't compile with clang). Is there a r
On Mon, 28 Oct 2019 at 10:33, Sebastian Huber
wrote:
>
> On 28/10/2019 11:16, Hesham Almatary wrote:
> > Hi Sebastian,
> >
> > The *_clang ones aren't expected to be compiled by GCC (and the native
> > *.cfg won't compile with clang). Is there a reason they should be?
>
> You can build all BSPs of
On 28/10/2019 11:16, Hesham Almatary wrote:
Hi Sebastian,
The *_clang ones aren't expected to be compiled by GCC (and the native
*.cfg won't compile with clang). Is there a reason they should be?
You can build all BSPs of an architecture with:
../configure --target=riscv-rtems5
This no longe
Hi Sebastian,
The *_clang ones aren't expected to be compiled by GCC (and the native
*.cfg won't compile with clang). Is there a reason they should be?
On Mon, 28 Oct 2019 at 07:42, Sebastian Huber
wrote:
>
> Hello,
>
> when you build the new clang variants with GCC you get:
>
> gmake[3]: Lea
Hello,
when you build the new clang variants with GCC you get:
gmake[3]: Leaving directory
'/build/git-build/b-all-riscv-5/riscv-rtems5/c/rv32i_clang'
checking for RTEMS_CPU_MODEL...
checking for RTEMS_BSP_FAMILY... riscv
checking for CPU_CFLAGS... (cached) -march=rv32i -mabi=ilp32 -target
ri
Hi Sebastian,
On Thu, 24 Oct 2019 at 12:48, Sebastian Huber
wrote:
>
> Hello,
>
> I work currently on a new build system based on waf and Doorstop. It
> would be good to have the clang support at the top level of the build
> system. Doing this for the current build system is probably a waste of
>
Hello,
I work currently on a new build system based on waf and Doorstop. It
would be good to have the clang support at the top level of the build
system. Doing this for the current build system is probably a waste of
time. In general, I am fine with your changes.
It would be great if you cou
12 matches
Mail list logo
