RTEMS | Draft: Support for building RTEMS with LLVM toolchains (!1539)

[Sebastian Huber (@sebhub)]

Sebastian Huber started a new discussion on spec/build/cpukit/optclang.yml: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1539#note_161201

 >  - set-value:
 >    - -o
 >  - env-assign: ASLNK_TGT_F
 > -- set-value: --target=${ARCH}${ARCH_BITS}-unknown-rtems${__RTEMS_MAJOR__}
 > +- set-value: --target=${ARCH}${ARCH_BITS}-rtems${__RTEMS_MAJOR__}
 >  - substitute: null
 >  - env-append: ABI_FLAGS
 >  - script: |
 >      conf.load("ar asm clang clang++ gccdeps")
 > +- set-value:
 > +  - -nostartfiles

These flags add the C++ libraries to every link, also to a pure C application. GCC gets the libraries of a link from the RTEMS specs of its driver. `optusegnuld.yml` and the `__USE_INIT_FINI__` changes work around the same gap in the clang driver. Is RTEMS support in the clang driver planned upstream? The build items then need much less special code.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1539#note_161201
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/6-8yglv7drxwzyq0cnkqj70lpbc-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20261016/8dcb2e98/attachment-0001.htm>