On Mon, Sep 7, 2020, 3:09 PM Heinz Junkes wrote:
>
>
> > On 7. Sep 2020, at 21:53, Joel Sherrill wrote:
> >
> > i386-rtems5-ar dv librtemscpu.a dummy.o
>
> That was really the trick and helped.
>
Still seems like something isn't 100% right in your configuration. But at
least this works for now
> On 7. Sep 2020, at 21:53, Joel Sherrill wrote:
>
> i386-rtems5-ar dv librtemscpu.a dummy.o
That was really the trick and helped.
Danke Heinz
smime.p7s
Description: S/MIME cryptographic signature
___
users mailing list
users@rtems.org
http://lists.
On Mon, Sep 7, 2020 at 2:40 PM Heinz Junkes
wrote:
>
> > On 7. Sep 2020, at 21:18, Joel Sherrill wrote:
> >
> >
> > It needs to be in an object file defined between rtemsTestData.o and
> -lCom. Otherwise, there are configuration symbols lacking and the dummy
> configuration will get pulled i
> On 7. Sep 2020, at 21:18, Joel Sherrill wrote:
>
>
> It needs to be in an object file defined between rtemsTestData.o and
> -lCom. Otherwise, there are configuration symbols lacking and the dummy
> configuration will get pulled in.
>
>
Unfortunately I do not understand that. These a
On Mon, Sep 7, 2020 at 2:08 PM Heinz Junkes
wrote:
> unfortunately leads to this:
>
> ...
> rtemsTestHarness.o rtemsTestData.o -lCom -Wl,--gc-sections -lm
> -lrtemsCom -lc -lrtemscpu -lrtemsCom -lCom -lnfs -lm -lgcc
>
It needs to be in an object file defined between rtemsTestData.o and
unfortunately leads to this:
...
rtemsTestHarness.o rtemsTestData.o -lCom -Wl,--gc-sections -lm
-lrtemsCom -lc -lrtemscpu -lrtemsCom -lCom -lnfs -lm -lgcc
/home/h1/GSOC/rtems5_epics7/QtC-epics-base/lib/RTEMS-pc386-qemu/librtemsCom.a(rtems_config.o):(.data+0x0):
multiple definition of `rt
On 07/09/2020 19:14, Heinz Junkes wrote:
rtems 4.10 —with-network —with-posix
Unfortunately I cannot resolve a reference:
source/rtems-source-builder/rtems/build/i386-rtems4.10-kernel-4.10-1/i386-rtems4.10-kernel-4.10-1-4.10/build/i386-rtems4.10/c/pc686/cpukit/libblock/../../../../../../rtems-
rtems 4.10 —with-network —with-posix
Unfortunately I cannot resolve a reference:
source/rtems-source-builder/rtems/build/i386-rtems4.10-kernel-4.10-1/i386-rtems4.10-kernel-4.10-1-4.10/build/i386-rtems4.10/c/pc686/cpukit/libblock/../../../../../../rtems-4.10/c/src/../../cpukit/libblock/src/bdbuf.c
Hello Karel,
On 07/09/2020 11:33, Karel Gardas wrote:
> On 9/7/20 11:22 AM, Christian Mauderer wrote:
>> Hello Karel,
>>
>> note that rtems-littlevgl is still quite new and most likely _only_ used
>> on BBB and (with an external display driver) on the imx. I don't think
>> anyone tried it on pc686
On Mon, 7 Sep 2020 at 11:05, Schweikhardt, Jens (TSPCE3-TL4)
wrote:
>
> hello world\n
>
>
>
> I’m looking at
> https://git.rtems.org/rtems/tree/bsps/riscv/shared/start/start.S which
> contains near the end
>
>
>
> /* Wait for go issued by the boot processor (mhartid == 0) */
>
>
hello world\n
I'm looking at https://git.rtems.org/rtems/tree/bsps/riscv/shared/start/start.S
which contains near the end
/* Wait for go issued by the boot processor (mhartid == 0) */
LADDR t0, .Lsecondary_processor_go
.Lwait_for_go_again:
lw
On 9/7/20 11:22 AM, Christian Mauderer wrote:
> Hello Karel,
>
> note that rtems-littlevgl is still quite new and most likely _only_ used
> on BBB and (with an external display driver) on the imx. I don't think
> anyone tried it on pc686.
Yes, I'm kind of aware of that.
> On 07/09/2020 11:06, Ka
Hello Karel,
note that rtems-littlevgl is still quite new and most likely _only_ used
on BBB and (with an external display driver) on the imx. I don't think
anyone tried it on pc686.
On 07/09/2020 11:06, Karel Gardas wrote:
>
> Hello,
>
> I'm trying to compile rtems-littlevgl on pc686 BSP from
Hello,
I'm trying to compile rtems-littlevgl on pc686 BSP from RTEMS 5.1
release built with RSB -- hence with libbsd compiled in.
I'm hitting following compilation failure:
../../lv_drivers/indev/evdev.c:16:10: fatal error: dev/evdev/input.h: No
such file or directory
#include
^~~~
On 9/7/20 8:34 AM, Chris Johns wrote:
> On 7/9/20 4:06 pm, Karel Gardas wrote:
>> On 9/7/20 2:34 AM, Chris Johns wrote:
>>> On 7/9/20 8:29 am, Chris Johns wrote:
Hmm looks like the socket returns a string in Python 2 and bytes in Python
3. I
will need to play around to find a s
15 matches
Mail list logo