On Nov 4, 2015 1:57 PM, "Gedare Bloom" wrote:
>
> Did you bootstrap -c and then bootstrap? I think I saw this error
> earlier today too, with a new sparc toolchain, but then it went away
> after i rm-rf'd my build tree and tried over.
Hmm.. I thought I did that but am not sure. Maybe Martin can c
On Nov 4, 2015 1:39 PM, "Martin Galvan" <
martin.gal...@tallertechnologies.com> wrote:
>
> Hi everyone! I'm currently having some trouble when building RTEMS
> from the git mainline. I'm using a toolchain built using (a fairly
> recent) RSB. My configure is:
>
> ../source/configure --target=arm-rte
On Wed, Nov 4, 2015 at 7:33 PM, Pavel Pisa wrote:
> So it is important what are intended use cases.
> The one where RTEMS image starts from address 0
> is simple and should no use POM nor VIM interrupt bypassing.
> But it requires integration with HAL startup for now.
This should probably go on a
Should be fixed now.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäft
Hello Martin and Gedare,
On Wednesday 04 of November 2015 22:58:57 Martin Galvan wrote:
> On Wed, Nov 4, 2015 at 6:57 PM, Gedare Bloom wrote:
> > Did you bootstrap -c and then bootstrap? I think I saw this error
> > earlier today too, with a new sparc toolchain, but then it went away
> > after i
On Wed, Nov 4, 2015 at 6:57 PM, Gedare Bloom wrote:
> Did you bootstrap -c and then bootstrap? I think I saw this error
> earlier today too, with a new sparc toolchain, but then it went away
> after i rm-rf'd my build tree and tried over.
Yeah, I did this several times and I'm still seeing it.
__
Did you bootstrap -c and then bootstrap? I think I saw this error
earlier today too, with a new sparc toolchain, but then it went away
after i rm-rf'd my build tree and tried over.
On Wed, Nov 4, 2015 at 4:39 PM, Martin Galvan
wrote:
> Hi everyone! I'm currently having some trouble when building
Hi everyone! I'm currently having some trouble when building RTEMS
from the git mainline. I'm using a toolchain built using (a fairly
recent) RSB. My configure is:
../source/configure --target=arm-rtems4.11
--enable-rtemsbsp=beagleboneblack --enable-posix --enable-cxx
--disable-networking --enable
On 24/07/15 10:13, Joel Sherrill wrote:
__tls_get_addr.c needs to include rtems/score/percpu.h
I have a similar patch on my laptop for m68k. None of the bsps built for that
target.
Sorry, I fixed this also.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim,
On 24/07/15 10:21, Ric Claus wrote:
On Jul 24, 2015, at 10:13 AM, Sebastian Huber
wrote:
On 24/07/15 10:08, Ric Claus wrote:
Building rtems-libbsd, with either a modified Makefile or waf (exactly as per
rtems-libbsd/README.waf, i.e., for realview_pbx_a9_qemu), ends with:
In file include
On Jul 24, 2015, at 10:13 AM, Sebastian Huber
wrote:
>
>
> On 24/07/15 10:08, Ric Claus wrote:
>>
>>Building rtems-libbsd, with either a modified Makefile or waf (exactly
>>as per rtems-libbsd/README.waf, i.e., for realview_pbx_a9_qemu), ends
>>with:
>>
>>In fi
On July 24, 2015 9:08:57 AM GMT+01:00, Ric Claus
wrote:
>
>On Jul 24, 2015, at 9:50 AM, Sebastian Huber
> wrote:
>
>>
>>
>> On 23/07/15 18:57, Ric Claus wrote:
>>> Since a fresh git pull of the RTEMS master this morning (CET), I’ve
>been having trou
On 24/07/15 10:08, Ric Claus wrote:
>>
>>Building rtems-libbsd, with either a modified Makefile or waf (exactly as per
rtems-libbsd/README.waf, i.e., for realview_pbx_a9_qemu), ends with:
>>
>>In file included from ../../rtemsbsd/rtems/rtems-bsd-mutex.c:41:0:
>>.../rtems-libbsd/rtemsbsd/includ
On Jul 24, 2015, at 9:50 AM, Sebastian Huber
wrote:
>
>
> On 23/07/15 18:57, Ric Claus wrote:
>> Since a fresh git pull of the RTEMS master this morning (CET), I’ve been
>> having trouble building various components. Building the
>> xilinx-zynq-zedboard with —e
On 23/07/15 18:57, Ric Claus wrote:
Since a fresh git pull of the RTEMS master this morning (CET), I’ve been having
trouble building various components. Building the xilinx-zynq-zedboard with
—enable-smp ends with failing to build sptls01 (which had no trouble yesterday):
cpukit/score/cpu
Since a fresh git pull of the RTEMS master this morning (CET), I’ve been having
trouble building various components. Building the xilinx-zynq-zedboard with
—enable-smp ends with failing to build sptls01 (which had no trouble
yesterday):
cpukit/score/cpu/arm/__tls_get_addr.c:28: undefined
On Tue, 06 Jan 2015 02:40:48 +0100, Chris Johns wrote:
On 6/01/2015 8:29 am, Dominik Taborsky wrote:
Waf is configured (hopefully) fine. Otherwise it wouldn't even try to
build. Has anyone had any similar problem?
waf configure was run with these options: --rtems=/opt/rtems-4.11/
--rtems-too
On 6/01/2015 8:29 am, Dominik Taborsky wrote:
Waf is configured (hopefully) fine. Otherwise it wouldn't even try to
build. Has anyone had any similar problem?
waf configure was run with these options: --rtems=/opt/rtems-4.11/
--rtems-tools=$HOME/development/RTEMS-tools/4.11 --rtems-bsps=sparc/s
m scratch and it works now. It
looks
like some old config was still in place.
Now I have a different problem - waf has trouble building examples-v2
in
root of the repo. GCC complains about bsp_specs trying to rename spec
'endfile' to already defined spec 'old_endfile'. It happens
>>>#error "CONFIGURATION ERROR: POSIX API support not configured!!"
>>>>>>>
>>>>>>> All repos are up-to-date, ran make clean between configs and even
>>>>>>> manually deleted the installed RTEMS files to ensure new o
the mail, I configured it with
--enable-posix. Or would you like the whole command?
Sure. Since it worked for me, that's the next step.
OK. I've completely rebuilt RTEMS from scratch and it works now. It
looks
like some old config was still in place.
Now I have a different problem - w
>>> installed. Any ideas?
>>>> How did you configure RTEMS? If you has --disable-posix, then this is
>>>> expected.
>>> As I said in the beginning of the mail, I configured it with
>>> --enable-posix. Or would you like the whole command?
>>
orked for me, that's the next step.
OK. I've completely rebuilt RTEMS from scratch and it works now. It looks
like some old config was still in place.
Now I have a different problem - waf has trouble building examples-v2 in
root of the repo. GCC complains about bsp_specs trying
23 matches
Mail list logo
