Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lbase64: fix build
Date: Sat, 30 Sep 2017 11:34:53 +0200	[thread overview]
Message-ID: <20170930113453.523b5dc5@windsurf> (raw)
In-Reply-To: <CAB0FRsvSY3xZEWmaY1np9046L0t-x4KWQPTvjBBXJBa02aDS9w@mail.gmail.com>

Hello,

On Sat, 30 Sep 2017 10:12:54 +0200, Fran?ois Perrad wrote:

> There are 3 useful words in
> http://autobuild.buildroot.net/results/b56/b567096cbfdb89b1895924051265c56204ffb512/build-end.log
> :
>     "recompile with -fPIC"

Still, please write better commit logs.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-09-30  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 16:59 [Buildroot] [PATCH] lbase64: fix build Francois Perrad
2017-09-29 19:52 ` Thomas Petazzoni
2017-09-30  8:12   ` François Perrad
2017-09-30  9:34     ` Thomas Petazzoni [this message]
2017-10-06 19:00 ` Arnout Vandecappelle

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=20170930113453.523b5dc5@windsurf \
    --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