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 11:20:55 +0200 [thread overview]
Message-ID: <20180918112055.66612b12@windsurf> (raw)
In-Reply-To: <20180918111506.0648d78c@windsurf>
Hello,
On Tue, 18 Sep 2018 11:15:06 +0200, Thomas Petazzoni wrote:
> And I believe the reason is because -nostdlib -nostartfiles are used.
> Why is libaio using those flags? Is there a good reason ?
BTW: https://patchwork.openembedded.org/patch/106979/. It is still
there in their tree:
https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-extended/libaio/libaio/system-linkage.patch
In Debian:
https://sources.debian.org/patches/libaio/0.3.111-1/01_link_libs.patch/
In Gentoo:
https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/libaio/files/libaio-0.3.110-link-stdlib.patch
Perhaps we should use the same solution, and submit it upstream :-)
I looked at the Git history of libaio, and the first import of libaio
already had those flags, so there is no useful Git commit information
to explain those flags.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-09-18 9:20 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
2018-09-28 13:36 ` Alexey Brodkin
2018-09-18 9:20 ` Thomas Petazzoni [this message]
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=20180918112055.66612b12@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox