linkcmds.yml problems

[Sam Price]

Thanks i was trying to figure out how to debug this but didnt make much
progress.
Was trying to get waf to generate verbose information of all the calls it
was doing but wasnt sure how to do this.

Also saw these warnings during the compile process.  Have not had a chance
to dig into them to see if the conversion from unsigned int to void * is ok.

../../../bsps/microblaze/include/../../shared/dev/clock/clockimpl.h: In
function '_Clock_Initialize':
../../../bsps/microblaze/include/../../shared/dev/clock/clockimpl.h:235:37:
warning: passing argument 1 of 'microblaze_clock_handler_install' from
incompatible pointer type [-Wincompatible-pointer-types]
  235 |   Clock_driver_support_install_isr( Clock_isr );
      |                                     ^~~~~~~~~
      |                                     |
      |                                     rtems_isr
(*)(rtems_vector_number) {aka void (*)(unsigned int)}
../../../bsps/microblaze/microblaze_fpga/clock/clock.c:141:37: note: in
definition of macro 'Clock_driver_support_install_isr'
  141 |   microblaze_clock_handler_install( isr )
      |                                     ^~~
../../../bsps/microblaze/microblaze_fpga/clock/clock.c:122:71: note:
expected 'rtems_interrupt_handler' {aka 'void (*)(void *)'} but argument is
of type 'rtems_isr (*)(rtems_vector_number)' {aka 'void (*)(unsigned int)'}
  122 | static void microblaze_clock_handler_install(
rtems_interrupt_handler isr )
      |



On Thu, Jul 7, 2022 at 3:09 PM Alex White <alex.white at oarcorp.com> wrote:

> 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
>


-- 
Thank you,

Sam Price
(707) 742-3726
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20220707/95df3e04/attachment-0001.htm>