All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manish Singh <manish.singh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Updated Patch for 2.6 Make system
Date: Tue Mar  2 17:47:44 2004	[thread overview]
Message-ID: <20040302234739.GA2650@ca-server1.us.oracle.com> (raw)
In-Reply-To: <40450AC7.1060507@intel.com>

On Tue, Mar 02, 2004 at 02:29:27PM -0800, John L. Villalovos wrote:
> Fixes an error from the previous patch where I forgot to do NPTL :(
> 
> This now compiles with SVN revision 748.

I just committed a modified version of the configure.in and Config.make.in
changes.

> Index: configure.in
> ===================================================================
> --- configure.in	(revision 747)
> +++ configure.in	(working copy)
> @@ -83,6 +83,13 @@
>    AC_MSG_ERROR(GCC is required)
>  fi
> 
> +AC_ARG_ENABLE(kernel-2_6, AC_HELP_STRING([--enable-kernel-2_6], [(BROKEN!) 
> Enable building on Linux kernel version 2.6.x 
> (default=no)]),enable_kernel26=yes,enable_kernel26=no)
> +OCFS_KERNEL_2_6=
> +if test "x$enable_kernel26" = "xyes"; then
> +  OCFS_KERNEL_2_6=yes
> +fi
> +AC_SUBST(OCFS_KERNEL_2_6)

I got rid of the _'s. configure's never use _ in switches. Also, we can't
use AC_HELP_STRING since we still need to support AS 2.1, which ships with
ancient autoconf 2.13.

> +      AC_MSG_NOTICE([Support for kernel version 2.6 is BROKEN at this 
> time!  Your system WILL hang.])

Used AC_MSG_WARN instead of AC_MSG_NOTICE for the same reason.

> @@ -314,4 +331,5 @@
>  vendor/unitedlinux/ocfs2-2.4.21-107.spec
>  vendor/unitedlinux/ocfs2-2.4.21-111.spec
>  vendor/unitedlinux/ocfs2-2.4.21-138.spec
> +src/Makefile-2.6

In makebo philosophy, Makefiles should never be generated from .in's. You
should be able to include Config.make for what you need.

What I'd like to see is having one Makefile that does everything, with the
defines, cflags, and object files defined only once. Keeping this in sync
across multiple files is a maintainence headache.

-Manish

  reply	other threads:[~2004-03-02 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 16:29 [Ocfs2-devel] Updated Patch for 2.6 Make system John L. Villalovos
2004-03-02 17:47 ` Manish Singh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-02 18:01 Villalovos, John L
2004-03-02 19:51 ` Manish Singh
2004-03-03 10:57 Villalovos, John L
2004-03-03 17:15 ` Manish Singh

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=20040302234739.GA2650@ca-server1.us.oracle.com \
    --to=manish.singh@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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.