From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] fastd: add new package
Date: Wed, 4 Nov 2015 22:21:34 +0100 [thread overview]
Message-ID: <20151104222134.792979c1@free-electrons.com> (raw)
In-Reply-To: <1446102782-4565-2-git-send-email-post@lespocky.de>
Dear Alexander Dahl,
On Thu, 29 Oct 2015 08:13:02 +0100, Alexander Dahl wrote:
> This is a new package for the fastd "Fast and Secure Tunneling Daemon"
> which was developed for the Freifunk Gluon project in the first place.
> It's one of my first buildroot packages and I tried to follow the
> developer guide, if something can be improved I'm open for suggestions.
> I hope I covered the necessary build options and set reasonable
> defaults. Included is a patch to allow cross compiling with toolchains
> without LTO support which fails with the unpatched version due to some
> ugly cmake hacks in fastd v17, details in the patch.
This commit log again contained some "personal" messages, so I reworded
it.
I also did a few other changes:
[Thomas:
- Get rid of trailing spaces in Config.in
- Remove the BR2_PACKAGE_FASTD_OPENSSL, and simply rely on
BR2_PACKAGE_OPENSSL
- Remove -DWITH_CAPABILITIES=TRUE, since libcap support is anyway
mandatory.
- Use ON/OFF instead of TRUE/FALSE.]
and then applied your patch.
Could you submit your LTO related patch to the upstream project and get it merged, so that next time we update the fastd package we can get rid of the patch?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-04 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 7:13 [Buildroot] [PATCH 1/2] libuecc: add new package Alexander Dahl
2015-10-29 7:13 ` [Buildroot] [PATCH 2/2] fastd: " Alexander Dahl
2015-11-04 21:21 ` Thomas Petazzoni [this message]
2015-11-05 8:31 ` Alexander Dahl
2015-11-04 20:48 ` [Buildroot] [PATCH 1/2] libuecc: " Thomas Petazzoni
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=20151104222134.792979c1@free-electrons.com \
--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