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 1/1] ipmiutil: new package
Date: Sun, 21 Sep 2014 22:06:01 +0200	[thread overview]
Message-ID: <20140921220601.79d50cb8@free-electrons.com> (raw)
In-Reply-To: <1411033115-6914-1-git-send-email-david.bachelart@bbright.com>

Dear David Bachelart,

On Thu, 18 Sep 2014 11:38:35 +0200, David Bachelart wrote:

> diff --git a/package/ipmiutil/Config.in b/package/ipmiutil/Config.in
> new file mode 100644
> index 0000000..29d6e26
> --- /dev/null
> +++ b/package/ipmiutil/Config.in
> @@ -0,0 +1,15 @@
> +config BR2_PACKAGE_IPMIUTIL
> +	bool "ipmiutil"
> +	depends on BR2_TOOLCHAIN_HAS_SSP

Did you test if it works with an internal toolchain (i.e a toolchain
built by Buildroot) that has SSP enabled? Apparently, the package
forcefully links against -lssp. But I'm not sure if a libssp library is
built when SSP is enabled in the internal toolchain, because we use the
SSP support from the C library and not from the compiler. A
verification would be good, or even better, an improvement to ipmiutil
to make SSP support optional.

> +	select BR2_PACKAGE_OPENSSL
> +	select BR2_PACKAGE_ZLIB

This dependency on zlib seems unnecessary: I didn't see anything in
ipmiutil that references zlib directly. Did I miss it?

Also, the code contains call to fork(), so your package should depend
on BR2_USE_MMU. And the code uses threads, so it should depend on
thread support.

Try to make sure that your package builds fine with the following
toolchain configurations:

 - http://autobuild.buildroot.org/toolchains/configs/br-arm-basic.config
 - http://autobuild.buildroot.org/toolchains/configs/br-arm-full.config
 - http://autobuild.buildroot.org/toolchains/configs/bfin-linux-uclibc.config
 - http://autobuild.buildroot.org/toolchains/configs/bfin-uclinux.config

Thanks!

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

  reply	other threads:[~2014-09-21 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18  9:38 [Buildroot] [PATCH 1/1] ipmiutil: new package David Bachelart
2014-09-21 20:06 ` Thomas Petazzoni [this message]
2014-10-05 21:47 ` Thomas Petazzoni
2014-10-06  8:37   ` David Bachelart
2014-10-06 10:33     ` 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=20140921220601.79d50cb8@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