From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Johan Oudinet <johan.oudinet@gmail.com>,
Will Newton <will.newton@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/erlang-jiffy: fix build failure due to lack of -fPIC
Date: Fri, 17 Dec 2021 21:49:40 +0100 [thread overview]
Message-ID: <20211217214940.106e9ed5@windsurf> (raw)
In-Reply-To: <20211018221415.60dc705a@windsurf>
On Mon, 18 Oct 2021 22:14:15 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Thanks! However, did you review the discussion at:
>
> https://lore.kernel.org/buildroot/20201224101440.3427472-1-fontaine.fabrice@gmail.com/
>
> Especially the feedback from Arnout around the end of the thread?
Ping?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-17 20:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 21:54 [Buildroot] [PATCH 1/2] package/erlang-jiffy: fix build failure due to lack of -fPIC Giulio Benetti
2021-10-14 21:54 ` [Buildroot] [PATCH 2/2] package/erlang-jiffy: bump version to 1.0.9 Giulio Benetti
2021-12-20 9:34 ` Giulio Benetti
2021-12-28 22:06 ` Thomas Petazzoni
2021-10-14 21:54 ` [Buildroot] [PATCH 2/2] package/erlang-jiffy: fix build failure due to lack of -fPIC Giulio Benetti
2021-10-14 21:57 ` Giulio Benetti
2021-10-18 20:14 ` [Buildroot] [PATCH 1/2] " Thomas Petazzoni
2021-12-17 20:49 ` Thomas Petazzoni [this message]
2021-12-17 21:14 ` Giulio Benetti
2021-12-19 7:03 ` [Buildroot] [PATCH] package/erlang-rebar: fix linking failure on shared library Giulio Benetti
2021-12-19 8:08 ` Yann E. MORIN
2021-12-27 0:08 ` Giulio Benetti
2021-12-28 21:49 ` Yann E. MORIN
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=20211217214940.106e9ed5@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=johan.oudinet@gmail.com \
--cc=will.newton@gmail.com \
--cc=yann.morin.1998@free.fr \
/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