Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] package/libtalloc: new package
Date: Thu, 15 Oct 2020 22:16:57 +0200	[thread overview]
Message-ID: <20201015221657.7a224c6a@windsurf> (raw)
In-Reply-To: <20201015200609.20205-1-dgouarin@gmail.com>

Hello David,

Thanks for this new iteration!

On Thu, 15 Oct 2020 22:06:08 +0200
David GOUARIN <dgouarin@gmail.com> wrote:

> talloc is a hierarchical, reference counted memory pool system with destructors.
> It is the core memory allocator used in Samba.
> 
> Signed-off-by: David GOUARIN <dgouarin@thalesgroup.com>
> 
> Change v1 -> v2:
>   - merge with work from jared.bents at rockwellcollins.com, as sujested by Matthew Weber
>     http://patchwork.ozlabs.org/project/buildroot/patch/20200327150225.15277-1-jared.bents at rockwellcollins.com
> 
> Change v2 -> v4: (no v3, resubmitting the whole patch series)
>   - fix build with BR2_PARANOID_UNSAFE_PATH (Thomas review)
>   - add hashes of license files (Thomas)
>   - license is GPL-3.0+ for both talloc and pytalloc (Thomas)
>   - remove useless --prefix and --libdir (Thomas)

Your changelog should be below the --- sign...

> 
> ---

... here.


> +LIBTALLOC_VERSION = 2.3.1
> +LIBTALLOC_SOURCE = talloc-$(LIBTALLOC_VERSION).tar.gz
> +LIBTALLOC_SITE = https://www.samba.org/ftp/talloc
> +LIBTALLOC_LICENSE = GPL-3.0+
> +LIBTALLOC_LICENSE_FILES = talloc.h pytalloc.h
> +LIBTALLOC_INSTALL_STAGING = YES
> +
> +LIBTALLOC_CONF_OPTS += --cross-compile \
> +		--cross-answers=$(@D)/cache.txt \
> +		--hostcc=gcc \
> +		--with-libiconv=$(HOST_DIR)/usr # waf will search by default in /usr/local with causes an error at configure step when BR2_COMPILER_PARANOID_UNSAFE_PATH is set

This is almost certainly not correct: HOST_DIR/usr contains libraries
compiled for the host... but you're building libtalloc for the target.

So unless libiconv is only used by libtalloc to build host binaries,
this looks wrong. If it's using the target libiconv, you should use
--with-libiconv=$(STAGING_DIR)/usr. However, keep in mind that libiconv
is not provided by all C libraries: with the uClibc C library built
without locale support, you would have to enable the
BR2_PACKAGE_LIBICONV option, and depend on libiconv. See for example
the package/acsccid package.

Other than this issue, the rest looks good.

However, please send libtalloc and freeradius-server as a series: the
latter depends on the former.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2020-10-15 20:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 14:37 [Buildroot] [PATCH 1/2] package/libtalloc: new package David GOUARIN
2020-10-13 14:37 ` [Buildroot] [PATCH 2/2] package/freeradius-server: " David GOUARIN
2020-10-13 19:51   ` [Buildroot] [PATCH v2 3/3] " David GOUARIN
2020-10-14 17:02     ` [Buildroot] [PATCH v3] " David GOUARIN
2020-10-14 19:26       ` Thomas Petazzoni
2020-10-15 20:06       ` [Buildroot] [PATCH v4] package/libtalloc: " David GOUARIN
2020-10-15 20:06         ` [Buildroot] [PATCH v4] package/freeradius-server: " David GOUARIN
2020-10-15 20:16         ` Thomas Petazzoni [this message]
2020-10-16  6:25           ` [Buildroot] [PATCH v4] package/libtalloc: " david gouarin
2020-10-16 10:03             ` Thomas Petazzoni
2020-10-19 20:00           ` [Buildroot] [PATCH v5 1/2] " David GOUARIN
2020-10-19 20:00             ` [Buildroot] [PATCH v5 2/2] package/freeradius-server: " David GOUARIN
2020-10-13 14:50 ` [Buildroot] [PATCH 1/2] package/libtalloc: " Matthew Weber
2020-10-13 19:50 ` [Buildroot] [PATCH v2 2/3] " David GOUARIN
2020-10-14 19:18   ` 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=20201015221657.7a224c6a@windsurf \
    --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