Hi!
The WIP bsp_specs I've been using is here:
https://github.com/AmaanC/rtems/blob/ac/stub-x86-link-tests-pre-bspreorg-bak/c/src/lib/libbsp/x86_64/no_bsp/startup/bsp_specs
I think minimizing it and having the linker script take care of things
should be possible - I'll have to look into it as I p
Updates #3425.
---
bsps/sparc64/include/arch/arch.h | 4
bsps/sparc64/include/arch/mm/frame.h | 4
bsps/sparc64/include/arch/mm/mmu.h| 4
bsps/sparc64/include/arch/mm/tlb.h| 3 +++
bsps/sparc64/include/arch/mm/tte.h| 4 +
Updates #3425.
---
bsps/arm/smdk2410/config/smdk2410.cfg | 2 +-
bsps/arm/smdk2410/include/bsp/irq.h| 2 ++
bsps/arm/smdk2410/include/s3c24xx.h| 4
c/src/lib/libbsp/arm/smdk2410/configure.ac | 7 +--
4 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/bsps
Just running covoar there, we seem to be running into some problems at the
source line lookup stage
cpod@cpod ~/development/rtems/leon3 $ covoar -S
/home/cpod/development/rtems/test/rtems-tools/tester/rtems/testing/coverage/score-symbols.ini
-O /home/cpod/coverage_test/test/score
-E/home/cpod/deve
On 10/5/18 8:47 am, Cillian O'Donnell wrote:
> Just running covoar there, we seem to be running into some problems at the
> source line lookup stage
Thank you for testing this. I assume it builds OK and we can run it?
> cpod@cpod ~/development/rtems/leon3 $ covoar -S
> /home/cpod/development/rtem
Hi folks,
I just got a new laptop (Windows system) and I got stuck on building a
SPARC tool set using Ubuntu in Virtual Box. To build a SPARC tool set, I
use the command as below.
../source-builder/sb-set-builder --log=1-sparc.txt
--prefix=$HOME/development/rtems config/5/rtems-sparc64.bset
Is
Hi Dannie,
Did you check the python version? It should be a development version.
First run this command:
sudo apt-get python2.7-dev
then try
../source-builder/sb-set-builder --log=1-sparc.txt
--prefix=$HOME/development/rtems config/5/rtems-sparc64.bset
Hope, It will solve your problem.
Regards,
On Thu, 10 May 2018, 03:43 Chris Johns, wrote:
> On 10/5/18 8:47 am, Cillian O'Donnell wrote:
> > Just running covoar there, we seem to be running into some problems at
> the
> > source line lookup stage
>
> Thank you for testing this. I assume it builds OK and we can run it?
>
Builds with a cou
