From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libaio: Fix library creation for ARC with -Os
Date: Tue, 18 Sep 2018 15:58:00 +0200 [thread overview]
Message-ID: <20180918155800.748eae34@windsurf> (raw)
In-Reply-To: <24f81ffc5c8606c74c9d478a29b245d7646b90f6.camel@synopsys.com>
Hello,
On Tue, 18 Sep 2018 12:44:26 +0000, Alexey Brodkin wrote:
> Sure that's indeed an option. We'll just finally add "-mno-millicode"
> in TARGET_ABI for ARC and forget about that class of problems. Also
> maybe it worth having "-mno-millicode" set by default for Linux
> toolchains so looking forward there will be no need to mess with
> millicode manually.
Yes, that's indeed one solution, though the problem also exists for
PowerPC, so it would have been nice to understand it.
What I find weird is that why it happens only with libaio ? I mean
there are plenty of libraries built with -fpic, and libaio is the only
one causing this problem. The fact that libaio is using -nostdlib
-nostartfiles was an initial hint to explain why libgcc isn't brought
into the link, but as Alexey said, removing -nostdlib -nostartfiles
doesn't solve the problem.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-18 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 20:43 [Buildroot] [PATCH] libaio: Fix library creation for ARC with -Os Alexey Brodkin
2018-09-18 7:36 ` Thomas Petazzoni
2018-09-18 8:03 ` Alexey Brodkin
2018-09-18 9:15 ` Thomas Petazzoni
2018-09-18 9:17 ` Alexey Brodkin
2018-09-18 9:26 ` Thomas Petazzoni
2018-09-18 9:30 ` Alexey Brodkin
[not found] ` <098ECE41A0A6114BB2A07F1EC238DE89667FD144@de02wembxa.internal.synopsys.com>
2018-09-18 12:44 ` Alexey Brodkin
2018-09-18 13:58 ` Thomas Petazzoni [this message]
2018-09-28 13:36 ` Alexey Brodkin
2018-09-18 9:20 ` Thomas Petazzoni
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=20180918155800.748eae34@windsurf \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.