From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] sunxi-cedarx: needs -fPIC
Date: Sat, 12 Jan 2019 14:55:41 +0100 [thread overview]
Message-ID: <20190112145541.316d0b60@windsurf.home> (raw)
In-Reply-To: <20190112092459.21382-1-fontaine.fabrice@gmail.com>
Hello,
On Sat, 12 Jan 2019 10:24:59 +0100, Fabrice Fontaine wrote:
> Fixes:
> - http://autobuild.buildroot.org/results/c17062e1558f26c2db837883a0c33ef39dd031a2
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Could you explain why we are seeing such build errors since December
5th, 2018, while the package hasn't been touched since 2016 ? What
changed that makes those errors visible now ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-12 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 9:24 [Buildroot] [PATCH 1/1] sunxi-cedarx: needs -fPIC Fabrice Fontaine
2019-01-12 13:55 ` Thomas Petazzoni [this message]
2019-01-12 15:49 ` Fabrice Fontaine
2019-01-16 12:09 ` Peter Korsgaard
2019-01-24 19:05 ` 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=20190112145541.316d0b60@windsurf.home \
--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