From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dependencies.sh: improve the missing perl modules detection
Date: Wed, 23 Sep 2015 22:50:51 +0300 [thread overview]
Message-ID: <20150923195051.GA2229@tarshish> (raw)
In-Reply-To: <1443015861-11295-1-git-send-email-Vincent.Riera@imgtec.com>
Hi Vincent,
On Wed, Sep 23, 2015 at 02:44:21PM +0100, Vicente Olivert Riera wrote:
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> support/dependencies/dependencies.sh | 26 +++++++++++++++++++++-----
> 1 files changed, 21 insertions(+), 5 deletions(-)
>
> diff --git a/support/dependencies/dependencies.sh b/support/dependencies/dependencies.sh
> index 01ad828..af9aefe 100755
> --- a/support/dependencies/dependencies.sh
> +++ b/support/dependencies/dependencies.sh
> @@ -236,10 +236,26 @@ if grep -q ^BR2_HOSTARCH_NEEDS_IA32_COMPILER=y $BR2_CONFIG ; then
> fi
> fi
>
> -# Check that the Perl installation is complete enough to build
> -# host-autoconf.
The information that we need perl for host-autoconf should be preserved, I
think.
> -if ! perl -e "require Data::Dumper" > /dev/null 2>&1 ; then
> - echo "Your Perl installation is not complete enough, at least Data::Dumper is missing."
> - echo "On Debian/Ubuntu distributions, install the 'perl' package."
You are also removing this bit of valuable information.
Maybe we should split this into two checks, one for perl itself, and then for
some required modules. That would allow us to give the user a more precise
diagnosis.
> +# Check that the Perl installation is complete enough for Buildroot.
> +# Here is the space-separated list of the required modules:
> +required_perl_modules="Data::Dumper Thread:Queue"
> +
> +# This variable will keep the modules that are missing in your system:
> +missing_perl_modules=""
> +
> +for pm in $required_perl_modules ; do
> + if ! perl -e "require $pm" > /dev/null 2>&1 ; then
> + missing_perl_modules="$missing_perl_modules $pm"
> + fi
> +done
> +
> +if [ -n "$missing_perl_modules" ] ; then
> + echo "Your Perl installation is not complete enough; at least the following"
> + echo "modules are missing:"
> + echo ""
> + for pm in $missing_perl_modules ; do
> + echo -e "\t $pm"
> + done
> + echo ""
> exit 1
> fi
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-09-23 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 13:44 [Buildroot] [PATCH] dependencies.sh: improve the missing perl modules detection Vicente Olivert Riera
2015-09-23 19:50 ` Baruch Siach [this message]
2015-09-23 20:52 ` Vicente Olivert Riera
2015-09-23 21:00 ` Vicente Olivert Riera
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=20150923195051.GA2229@tarshish \
--to=baruch@tkos.co.il \
--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