linkcmds.yml problems

[Alex White]

On Thu, Jul 7, 2022 at 10:31 AM Sam Price <thesamprice at gmail.com> wrote:
> Is it possible i have a bad python instance ?

I was able to reproduce the linker problem using the latest RTEMS upstream code.

It looks like it was broken by commit a0aaa394b68727d204904b59514cb0f90840ba6f from 6 days ago.

I will submit a fix.

Alex

>
>
> --
> Thank you,
>
> Sam Price
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel

________________________________________
From: devel <devel-bounces at rtems.org> on behalf of Sam Price <thesamprice at gmail.com>
Sent: Thursday, July 7, 2022 10:30 AM
To: devel at rtems.org
Subject: linkcmds.yml problems

Was trying to build the latest source builder/rtems/libbsd but ran into a linker problem.

You ever see this the source linker has

spec/build/bsps/microblaze/microblaze_fpga/linkcmds.yml: RAM : ORIGIN = _TEXT_START_ADDR, LENGTH = ${BSP_MICROBLAZE_FPGA_RAM_LENGTH}


But the generated linker file is creating

RAM : ORIGIN = _TEXT_START_ADDR, LENGTH =

when building rtems without populating the BSP_MICROBLAZE_FPGA_RAM_LENGTH.



My config.ini has this specified as
configs/config_kcu105_cpu0.ini:BSP_MICROBLAZE_FPGA_RAM_LENGTH=0x10000000

Is it possible i have a bad python instance ?


--
Thank you,

Sam Price