On 19/12/19 11:33 pm, Heinz P. Junkes wrote:
> Hi Chris, another issue with the Release Snapshot and powerpc (qoriq_e500):
>
> libbsd :
>
> ./waf configure --prefix=/home/epics/MVME2500/RTEMS/5.0.0-m1912
> --rtems-bsps=powerpc/qoriq_e500 --buildset=buildset/default.ini
>
>
> ./waf
>
> ...
>
> [1850/1940] Linking build/powerpc-rtems5-qoriq_e500-default/debugger01.exe
> /home/epics/MVME2500/RTEMS/5.0.0-m1912/lib/gcc/powerpc-rtems5/7.5.0/../../../../powerpc-rtems5/bin/ld:
> cannot find -ldebugger
> collect2: error: ld returned 1 exit status
>
> Waf: Leaving directory
> `/home/epics/MVME2500/RTEMS_DEV/rtems-libbsd-5.0.0-m1912/build/powerpc-rtems5-qoriq_e500-default'
>
> Build failed
> -> task in 'debugger01.exe' failed with exit status 1 (run with -v to display
> more information)
>
> From Sebastian Huber I got already the info to remove
> debugger01:epics@epics:~/MVME2500/RTEMS_DEV/rtems-
>
> libbsd-5.0.0-m1912$ diff libbsd.py libbsd.py.fix
> 5107,5109d5106
> < self.addTest(mm.generator['test-if-header']('debugger01',
> 'rtems/rtems-debugger.h',
> < ['test_main'], runTest = False, netTest = True,
> < extraLibs =
> ['debugger']))
>
> which does it it.
>
I wonder if `rtems/rtems-debugger.h` is being installed for the PowerPC BSP
which has no libdebugger support? It should not.
I wonder if the libbsd test needs to look for libdebugger.a and not the header.
If more than one BSP is installed into the prefix and one supports libdebugger
we would have this issue.
I have raised https://devel.rtems.org/ticket/3848
Chris
_______________________________________________
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users
