From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Clean up top level configure part 1
Date: Sat, 22 Sep 2007 10:09:03 +0200 [thread overview]
Message-ID: <46F4CD9F.8070908@ubuntu.com> (raw)
Hi guys,
the patch in attachment is purely cosmetic. I switched the top level configure
to use perl -w rather than just perl and spotted a bunch of warnings.
This patch:
- switches permanently to perl -w
- fixes all the warnings in the script.
Part1 because I plan to re-rewrite the top level configure from scratch by using
the only known thing in every system (that being /bin/sh) and make path to perl
configurable (not all system use /usr/bin/perl).
I also plan to kill the need of make/defines.mk.input and create make/define.mk
directly.
use Usual::ACK::Apply::disclaimer
Cheers
Fabio
--
I'm going to make him an offer he can't refuse.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: configure.diff
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070922/3ecdbb81/attachment.ksh>
next reply other threads:[~2007-09-22 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 8:09 Fabio Massimo Di Nitto [this message]
2007-09-24 13:45 ` [Cluster-devel] [PATCH] Clean up top level configure part 1 Patrick Caulfield
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=46F4CD9F.8070908@ubuntu.com \
--to=fabbione@ubuntu.com \
/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.