instaling rtems on windows 10
gedare at rtems.org
Thu Mar 18 16:11:14 UTC 2021
On Thu, Mar 18, 2021 at 8:25 AM Alireza Banejad
<alibanejad1376 at gmail.com> wrote:
> Hey Gedare
> Thanks for the reply
> I checked out rtems 7 and it seems to pass building gdb
I guess you mean that you have built the 7/ tools with the RSB. These
are "bleeding edge" toolchain, because there is no such thing as rtems
7, but they are probably suitable for you to use with rtems 6
(rtems.git/master branch). Since your gdb build problem goes away,
this indicates to me that gdb has resolved this bcrypt issue.
> It seems that the issue I mentioned is just for rtems 6
> Also thanks for the ldflag tip. Yet I don't exactly know where to add this flag. Is there some sort of file I need to edit and add the linker flag or should I just pass it through the command line when building the rsb?
You could add it in the command that builds gdb for your target, but I
don't know that it is quite so easy and anyway it is just a local hack
to try to get things to work. You could just as easily make your
rtems6 config use the updated version of gdb that fixes this bug.
> On Wed, Mar 17, 2021, 21:28 Gedare Bloom <gedare at rtems.org> wrote:
>> On Wed, Mar 17, 2021 at 5:07 AM Alireza Banejad
>> <alibanejad1376 at gmail.com> wrote:
>> > hello every one
>> > I'm trying to install rtems 6 arm toolchain on windows 10 but when the source builder tries to build the rtems-gdb-10 it results in an error
>> > reading the report gives me the following:
>> > C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ../gnulib/import/libgnu.a(getrandom.o): in function `getrandom':
>> > C:\opt\rtems\rsb\rtems\build\argfxwm1\build\gnulib\import/../../../sourceware-mirror-binutils-gdb-fc9b4c8/gnulib/import/getrandom.c:129: undefined reference to `BCryptGenRandom'
>> This looks relevant:
>> It seems that the configure probe for getrandom picks up libbcrypt
>> exists on your Windows, but then it does not get linked properly. This
>> seems to be a gdb build system problem. Possibly a newer gdb has fixed
>> it? You might be able to figure out how to add -lbcrypt to your linker
>> flags (export LDFLAGS=-lbcrypt might just work) locally while
>> compiling GDB.
>> > collect2.exe: error: ld returned 1 exit status
>> > make: *** [Makefile:1866: gdb.exe] Error 1
>> > make: Leaving directory '/c/opt/rtems/rsb/rtems/build/argfxwm1/build/gdb'
>> > make: *** [Makefile:9744: all-gdb] Error 2
>> > make: Leaving directory '/c/opt/rtems/rsb/rtems/build/argfxwm1/build'
>> > make: *** [Makefile:866: all] Error 2
>> > shell cmd failed: sh -ex /c/opt/rtems/rsb/rtems/build/argfxwm1/do-build
>> > error: building argfxwm1
>> > Any thoughts?
>> > _______________________________________________
>> > users mailing list
>> > users at rtems.org
>> > http://lists.rtems.org/mailman/listinfo/users
More information about the users