[riot-devel] Unable to build in native

Jose Alamos jialamos at uc.cl
Fri Feb 12 12:10:03 CET 2016


Hi!

It seems to be a problem with libgcc. You could try this:
http://askubuntu.com/questions/346377/cannot-find-lgcc-s

Or this:
http://serverfault.com/questions/266138/cannot-find-lgcc-s-from-gcc-3-4-on-unbuntu-11-04

Best regards.

2016-02-12 9:00 GMT+01:00 <devel-request at riot-os.org>:

> Send devel mailing list submissions to
>         devel at riot-os.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.riot-os.org/mailman/listinfo/devel
> or, via email, send a message with subject or body 'help' to
>         devel-request at riot-os.org
>
> You can reach the person managing the list at
>         devel-owner at riot-os.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of devel digest..."
>
>
> Today's Topics:
>
>    1. accidentally commited to master (Landsmann, Martin)
>    2. Re: accidentally commited to master (Joakim Nohlgård)
>    3. Re: accidentally commited to master (Landsmann, Martin)
>    4. no main-thread while making a port to a new MCU (Bernhard Nägele)
>    5. Problems during porting RIOT-OS (Bernhard Nägele)
>    6. IPv6 NDP router advertisement from global address
>       (Michael Andersen)
>    7. Unable to build in native (tobaccopipeyoyo .)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 11 Feb 2016 12:11:59 +0000
> From: "Landsmann, Martin" <Martin.Landsmann at haw-hamburg.de>
> To: RIOT OS kernel developers ‎[devel at riot-os.org]‎
>         <devel at riot-os.org>
> Subject: [riot-devel] accidentally commited to master
> Message-ID:
>         <
> 2D3546F9EA22AB48A00276A6F528BD0140EFB413 at MB04.mailcluster.haw-hamburg.de>
>
> Content-Type: text/plain; charset="cp1256"
>
> Hi guys,
>
> I accidentally commited directly to master ): [1]
> Is there a way to revert it?
>
> Best Regards,
> Martin
>
> [1]
> https://github.com/RIOT-OS/RIOT/commit/30ab68833999931e29ce8453ebc1057f939575e6
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.riot-os.org/pipermail/devel/attachments/20160211/e2689b0e/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Thu, 11 Feb 2016 13:17:35 +0100
> From: Joakim Nohlgård <joakim.nohlgard at eistec.se>
> To: RIOT OS kernel developers <devel at riot-os.org>
> Subject: Re: [riot-devel] accidentally commited to master
> Message-ID:
>         <CAOy=vanE6LVa9j=
> cH4RPvsDvjpWnqBg5V-TKJ1Pxmcri0K5czw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I think it is better to make a revert commit and push that as well, that
> avoids the problem of rewritten history.
>
> git revert 30ab68833999931e29ce8453ebc1057f939575e6
> git push
>
> To prevent mistakes like this in the future, change the upstream repo URL
> to use the https:// or git:// links instead of ssh://
>
> Best regards,
> Joakim
>
> On Thu, Feb 11, 2016 at 1:11 PM, Landsmann, Martin <
> Martin.Landsmann at haw-hamburg.de> wrote:
>
> > Hi guys,
> >
> > I accidentally commited directly to master ): [1]
> > Is there a way to revert it?
> >
> > Best Regards,
> > Martin
> >
> > [1]
> >
> https://github.com/RIOT-OS/RIOT/commit/30ab68833999931e29ce8453ebc1057f939575e6
> >
> > _______________________________________________
> > devel mailing list
> > devel at riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.riot-os.org/pipermail/devel/attachments/20160211/75812d56/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Thu, 11 Feb 2016 12:25:53 +0000
> From: "Landsmann, Martin" <Martin.Landsmann at haw-hamburg.de>
> To: RIOT OS kernel developers <devel at riot-os.org>
> Subject: Re: [riot-devel] accidentally commited to master
> Message-ID:
>         <
> 2D3546F9EA22AB48A00276A6F528BD0140EFB457 at MB04.mailcluster.haw-hamburg.de>
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Did revert, again sorry for that ):
> and @gebart thx for the hint
>
> Best regards,
> Martin
>
> ________________________________
> Von: devel [devel-bounces at riot-os.org]" im Auftrag von "Joakim Nohlgård [
> joakim.nohlgard at eistec.se]
> Gesendet: Donnerstag, 11. Februar 2016 13:17
> An: RIOT OS kernel developers
> Betreff: Re: [riot-devel] accidentally commited to master
>
> I think it is better to make a revert commit and push that as well, that
> avoids the problem of rewritten history.
>
> git revert 30ab68833999931e29ce8453ebc1057f939575e6
> git push
>
> To prevent mistakes like this in the future, change the upstream repo URL
> to use the https:// or git:// links instead of ssh://
>
> Best regards,
> Joakim
>
> On Thu, Feb 11, 2016 at 1:11 PM, Landsmann, Martin <
> Martin.Landsmann at haw-hamburg.de<mailto:Martin.Landsmann at haw-hamburg.de>>
> wrote:
> Hi guys,
>
> I accidentally commited directly to master ): [1]
> Is there a way to revert it?
>
> Best Regards,
> Martin
>
> [1]
> https://github.com/RIOT-OS/RIOT/commit/30ab68833999931e29ce8453ebc1057f939575e6
>
> _______________________________________________
> devel mailing list
> devel at riot-os.org<mailto:devel at riot-os.org>
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.riot-os.org/pipermail/devel/attachments/20160211/57071772/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 4
> Date: Thu, 11 Feb 2016 22:50:41 +0100
> From: Bernhard Nägele <bernhard.naegele at t-online.de>
> To: devel at riot-os.org
> Subject: [riot-devel] no main-thread while making a port to a new MCU
> Message-ID: <56BD0231.2080406 at t-online.de>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Dear sirs,
> I tried to do everything which is described in the RIOT-porting guide,
> but I stuck at a very early level. The base-system seems to work.
> Everytime when I stop the MCU with the emulation probe I am in the
> idle-thread and I can single-step further on. The misterious thing is
> that it seems, that the main thread is not involved in the working flow.
> Only one character is seen by a terminal software per restart.
> Have you any idea what's going wrong here?
>
> Best regards
> Bernhard
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 11 Feb 2016 23:24:04 +0100
> From: Bernhard Nägele <bernhard at naegele-privat.de>
> To: devel at riot-os.org
> Subject: [riot-devel] Problems during porting RIOT-OS
> Message-ID: <56BD0A04.9060907 at naegele-privat.de>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hello, I am trying to port RIOT-OS to the STM32L053 MCU and I get stuck
> at the moment.
> The base system seems to work - every time I stop the system with the
> emulation probe I
> can see that the system is in the idle-thread and I can single-step
> until I reach the next idle-thread.
> The misterious thing is that the main task is never executed. No "Hello
> World" on the serial
> interface. One character is seen by a terminal software after each
> restart, but not more.
> Have you any idea what could going wrong at that step. The UART is
> set-up correctly, because
> I got the dummy handler message before I worked at the vectors.c file.
>
> Question 2: I want to use the Low Power Timer of the STM32L053 during
> the idle thread (stop-mode).
> Can you give me a hint, where to place the change-over from the normal
> clock to the LPTimer?
> lpm_arch.c ?
>
> Best regards,
> Bernhard
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 11 Feb 2016 20:53:35 -0800
> From: Michael Andersen <michael at steelcode.com>
> To: RIOT OS kernel developers <devel at riot-os.org>
> Subject: [riot-devel] IPv6 NDP router advertisement from global
>         address
> Message-ID:
>         <CAPLpPru2qZ0zn27BOyUk-4iWZ4yp6Pa3FBYGd=
> tsNgeDzdR3fQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi
>
> My nodes are getting "invalid" router advertisements a whole lot, and
> falling out here
> <
> https://github.com/RIOT-OS/RIOT/blob/master/sys/net/gnrc/network_layer/ndp/gnrc_ndp.c#L500
> >
> which
> is causing a severe decrease in mesh reliability.
>
> Specifically, it is the first check: the IPv6 source address is not link
> local. (And I have verified that with a sniffer, the packets contain a full
> 128-bit inlined global address). I don't know the standards well enough to
> know who is at fault here, but I reckon either the sender or the receiver
> must be wrong :-)
>
> Does anyone know if this requirement is true? That router advertisements in
> response to router solicitations must contain link-local source addresses?
> Incidentally, the node responding is one link away, so it could have used a
> link-local address, it just chose not to.
>
> Thanks again for your help
> Michael
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.riot-os.org/pipermail/devel/attachments/20160211/af3258d4/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 7
> Date: Fri, 12 Feb 2016 00:00:02 -0800
> From: "tobaccopipeyoyo ." <tobaccopipeyoyo at gmail.com>
> To: devel at riot-os.org
> Subject: [riot-devel] Unable to build in native
> Message-ID:
>         <
> CAAQJGesKhLtkpph7VOP3J8npfn+TM-N5vEjjqjD1ernhTcwBMw at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi everyone,
> Sorry to disturb y'all.
> This is my second post here, still not able to build the native code
>
> This is the output that am getting.
> "make" -C /home/riot/RIOT/sys/shell
> "make" -C /home/riot/RIOT/sys/shell/commands
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-linux-gnu/4.9/libgcc.a when searching for -lgcc
> /usr/bin/ld: cannot find -lgcc
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-linux-gnu/4.9/libgcc_s.so when searching for
> -lgcc_s
> /usr/bin/ld: cannot find -lgcc_s
> collect2: error: ld returned 1 exit status
> make: *** [all] Error 1
>
>
> It would be great if you could provide some insight.
>
> Thanks,
> tbyy
>
> gcc -v
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Ubuntu
> 4.9.3-8ubuntu2~14.04'
> --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs
> --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
> --program-suffix=-4.9 --enable-shared --enable-linker-build-id
> --libexecdir=/usr/lib --without-included-gettext
> --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9
> --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
> --enable-libstdcxx-debug --enable-libstdcxx-time=yes
> --enable-gnu-unique-object --disable-vtable-verify --enable-plugin
> --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk
> --enable-gtk-cairo
> --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre
> --enable-java-home
> --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64
> --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64
> --with-arch-directory=amd64
> --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc
> --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
> --with-multilib-list=m32,m64,mx32 --enable-multilib
> --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu
> --host=x86_64-linux-gnu --target=x86_64-linux-gnu
> Thread model: posix
> gcc version 4.9.3 (Ubuntu 4.9.3-8ubuntu2~14.04)
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> devel mailing list
> devel at riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
> ------------------------------
>
> End of devel Digest, Vol 36, Issue 18
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20160212/0a36d59a/attachment-0001.html>


More information about the devel mailing list