From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/6] uclibc: add libgcc_s_resume fix
Date: Sun, 14 Jun 2015 22:33:47 +0200 [thread overview]
Message-ID: <20150614223347.3f0525b4@free-electrons.com> (raw)
In-Reply-To: <20150614162409.GC8165@tarshish>
Dear Baruch Siach,
On Sun, 14 Jun 2015 19:24:09 +0300, Baruch Siach wrote:
> > +When built with gcc 5.1, uClibc-ng fails to build with the following
> > +issue:
>
> This patch is for uClibc.
Bad copy/paste, indeed.
> > + librt/librt_so.a(rt-unwind-resume.oS): In function `_Unwind_Resume':
> > + rt-unwind-resume.c:(.text+0x3c): undefined reference to
>
> Is that the full error message? I have that strange feeling that something is
> missing. Same goes for the uClibc-ng patch.
Gah, again a copy/paste issue (though different than the previous one).
The full error message is:
LD librt-0.9.33.2.so
librt/librt_so.a(rt-unwind-resume.oS): In function `_Unwind_Resume':
rt-unwind-resume.c:(.text+0x3c): undefined reference to `libgcc_s_resume'
collect2: error: ld returned 1 exit status
make[2]: *** [lib/librt.so] Error 1
I'll update the commit log accordingly.
Thanks for the review!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-14 20:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 14:33 [Buildroot] [PATCH 0/6] Internal toolchain backend updates Thomas Petazzoni
2015-06-14 14:33 ` [Buildroot] [PATCH 1/6] uclibc: bump uClibc-ng to 1.0.3 Thomas Petazzoni
2015-06-14 19:03 ` Waldemar Brodkorb
2015-06-14 20:40 ` Thomas Petazzoni
2015-06-22 22:17 ` Peter Korsgaard
2015-06-14 14:33 ` [Buildroot] [PATCH 2/6] uclibc: add libgcc_s_resume fix Thomas Petazzoni
2015-06-14 16:24 ` Baruch Siach
2015-06-14 20:33 ` Thomas Petazzoni [this message]
2015-06-22 22:28 ` Peter Korsgaard
2015-06-14 14:33 ` [Buildroot] [PATCH 3/6] gcc: add support for gcc 5.1 Thomas Petazzoni
2015-06-20 15:12 ` Bernd Kuhls
2015-06-20 15:38 ` Bernd Kuhls
2015-06-22 22:27 ` Peter Korsgaard
2015-06-22 22:18 ` Peter Korsgaard
2015-06-14 14:33 ` [Buildroot] [PATCH 4/6] gcc: switch to gcc 4.9 as the default version Thomas Petazzoni
2015-06-22 22:19 ` Peter Korsgaard
2015-06-14 14:33 ` [Buildroot] [PATCH 5/6] gdb: bump 7.9 series to 7.9.1 Thomas Petazzoni
2015-06-22 22:23 ` Peter Korsgaard
2015-06-14 14:33 ` [Buildroot] [PATCH 6/6] toolchain-buildroot: mark eglibc as deprecated Thomas Petazzoni
2015-06-22 22:24 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150614223347.3f0525b4@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox