From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/openvmtools: fix procps-ng library name
Date: Sat, 18 Apr 2015 19:16:09 +0200 [thread overview]
Message-ID: <55329159.5000609@openwide.fr> (raw)
In-Reply-To: <1429269780-107634-1-git-send-email-kaszak@gmail.com>
Hi Karoly,
Le 17/04/2015 13:23, Karoly Kasza a ?crit :
> procps-ng libraries are now accesible on the same name as procps, thus
> using the CUSTOM_PROCPS_NAME environment variable breaks compilation.
>
> This fixes autobuild error 2a19f84c35de0ff008c2cd1aea96f6a4f2767ee1.
Usually we use a complete path like:
http://autobuild.buildroot.net/results/2a1/2a19f84c35de0ff008c2cd1aea96f6a4f2767ee1
>
> Signed-off-by: Karoly Kasza <kaszak@gmail.com>
> ---
Issue reproduced locally.
Reviewed-by: Romain Naour <romain.naour@openwide.fr>
Tested-by: Romain Naour <romain.naour@openwide.fr>
Best regards,
Romain
> package/openvmtools/openvmtools.mk | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/package/openvmtools/openvmtools.mk b/package/openvmtools/openvmtools.mk
> index f180f6f..ef6544a 100644
> --- a/package/openvmtools/openvmtools.mk
> +++ b/package/openvmtools/openvmtools.mk
> @@ -33,7 +33,6 @@ endif
>
> ifeq ($(BR2_PACKAGE_OPENVMTOOLS_PROCPS),y)
> OPENVMTOOLS_CONF_OPTS += --with-procps
> -OPENVMTOOLS_CONF_ENV += CUSTOM_PROCPS_NAME=procps
> OPENVMTOOLS_DEPENDENCIES += procps-ng
> else
> OPENVMTOOLS_CONF_OPTS += --without-procps
>
next prev parent reply other threads:[~2015-04-18 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 11:23 [Buildroot] [PATCH] package/openvmtools: fix procps-ng library name Karoly Kasza
2015-04-18 17:16 ` Romain Naour [this message]
2015-04-19 8:16 ` 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=55329159.5000609@openwide.fr \
--to=romain.naour@openwide.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.