Realtek-RTL8195AM compilation failure for mbed-os-example-blinky

[mray190]

Type: Bug
Target: Realtek-RTL8195AM

When compiling on the online compiler, mbed-os-example-blinky does not compile with the Realtek-RTL8195AM target.

Error:

"/extras/mbed-os.lib/targets/TARGET_Realtek/TARGET_AMEBA/TARGET_RTL8195A/device/TOOLCHAIN_ARM_STD/rtl8195a.sct", line 16 (column 22): Error: L6236E: No section matches selector - no section to be FIRST/LAST.

MbedOS version:
Head of 5.6 (Commit 182bbd5)

[0xc0170]

To be certain, this is only online environment related? Based on the above, seems like startup file missing in the workspace.

I tested same commit SHA locally, builds. Thus this is related to the online IDE. Please confirm

[0xc0170]

cc @theotherjimmy

[mray190]

@0xc0170 - Can confirm that is only on the online compiler

[0xc0170]

@0xc0170 - Can confirm that is only on the online compiler

You can also test it locally to be certain. I did as I wrote above, fetched blinky, same sha for mbed-os and built it without errors.

[prashantrar]

The PR for this issue has been merged but the online compiler still gives a compilation issue, is the issue still persistent even after merge?

[0xc0170]

The PR for this issue has been merged but the online compiler still gives a compilation issue, is the issue still persistent even after merge?

Are you using mbed OS 5.7.3? Please specify what versions and how are you testing

[prashantrar]

I am using mbed OS 5.7.3, I loaded the example into the compiler using this link

https://os.mbed.com/teams/mbed-os-examples/code/mbed-os-example-blinky/

[0xc0170]

The PR for this issue has been merged but the online compiler still gives a compilation issue, is the issue still persistent even after merge?

Please also specify what errors are you getting, more information you can provide, better response you can get.

@ARMmbed/team-realtek Can you reproduce?

I tested it just now, getting internal compiler error for this target (5.7.3 mbed-os, blinky example), other targets build fine (freedom k64f, nucleo f429

[prashantrar]

This is the snapshot of the issue that im getting

[prashantrar]

Is there any way we can debug the root cause of this issue from our side?