From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] slang: fix static builds
Date: Wed, 10 Dec 2014 10:22:19 +0000 [thread overview]
Message-ID: <54881EDB.208@imgtec.com> (raw)
In-Reply-To: <20141209203440.53026bbb@free-electrons.com>
Dear Thomas Petazzoni,
On 12/09/2014 07:34 PM, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
>
> On Tue, 9 Dec 2014 11:51:18 +0000, Vicente Olivert Riera wrote:
>> - Rename current patches to follow the new name convention.
>> - Adapt upstream patches to allow building only the static library and a
>> static version of slsh.
>> - Use specific build and install commands when doing static builds.
>>
>> Vicente Olivert Riera (3):
>> slang: rename patches to follow the new name convention
>> slang: add adapted upstream patches for static builds
>> slang: use specific build and install commands for static builds
>
> All three patches applied, thanks. The last two patches could have been
> only one since they are both needed to fix the static linking problem.
Well..., yeah, but it's easier to review, and the series is still
bisectable :P
Cheers,
--
Vicente Olivert Riera
Graduate Software Engineer, MIPS Platforms
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
prev parent reply other threads:[~2014-12-10 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 11:51 [Buildroot] [PATCH 0/3] slang: fix static builds Vicente Olivert Riera
2014-12-09 11:51 ` [Buildroot] [PATCH 1/3] slang: rename patches to follow the new name convention Vicente Olivert Riera
2014-12-09 11:51 ` [Buildroot] [PATCH 2/3] slang: add adapted upstream patches for static builds Vicente Olivert Riera
2014-12-09 11:51 ` [Buildroot] [PATCH 3/3] slang: use specific build and install commands " Vicente Olivert Riera
2014-12-09 19:34 ` [Buildroot] [PATCH 0/3] slang: fix " Thomas Petazzoni
2014-12-10 10:22 ` Vicente Olivert Riera [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=54881EDB.208@imgtec.com \
--to=vincent.riera@imgtec.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