Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Re: [DRBD-cvs] svn commit by lars - r2551 - in branches/drbd-0.7: . drbd drbd/linux scripts - fix some odities in the paranoia checks of our build sy
Date: Mon, 30 Oct 2006 23:29:35 +0100	[thread overview]
Message-ID: <20061030222935.GC3927@marowsky-bree.de> (raw)
In-Reply-To: <20061024144835.GH20631@marowsky-bree.de>

On 2006-10-24T16:48:35, Lars Marowsky-Bree <lmb@suse.de> wrote:

This seems to have gotten lost. Can I interest you in the patch again?

> On 2006-10-19T16:56:00, drbd-cvs@lists.linbit.com wrote:
> 
> > Author: lars
> > Date: 2006-10-19 16:55:58 +0200 (Thu, 19 Oct 2006)
> > New Revision: 2551
> > 
> > Added:
> >    branches/drbd-0.7/scripts/get_uts_release.sh
> > Modified:
> >    branches/drbd-0.7/Makefile
> >    branches/drbd-0.7/drbd.spec.in
> >    branches/drbd-0.7/drbd/Makefile
> >    branches/drbd-0.7/drbd/drbd_worker.c
> >    branches/drbd-0.7/drbd/linux/drbd_config.h
> >    branches/drbd-0.7/scripts/adjust_drbd_config_h.sh
> > Log:
> > fix some odities in the paranoia checks of our build system,
> > should build agains 2.6.18 now out of the box.
> 
> That actually introduced a bug: building the tgz now requires the
> kernel source to be installed, which is in fact only required when the
> kernel modules are built (and which could happen on another system).
> 
> How about the rather simple patch attached instead?
> 
> 
> 
> -- 
> High Availability & Clustering
> SUSE Labs, Research and Development
> SUSE LINUX Products GmbH - A Novell Business	 -- Charles Darwin
> "Ignorance more frequently begets confidence than does knowledge"
> 

> Index: Makefile
> ===================================================================
> --- Makefile	(revision 2564)
> +++ Makefile	(working copy)
> @@ -160,9 +160,6 @@
>  
>  KDIR := $(shell echo /lib/modules/`uname -r`/build)
>  KVER := $(shell KDIR=$(KDIR) O=$(O) scripts/get_uts_release.sh)
> -ifeq ($(KVER),)
> -$(error "could not determine uts_release")
> -endif
>  
>  kernel-patch: drbd/drbd_buildtag.c
>  	set -o errexit; \
> @@ -173,6 +170,10 @@
>  
>  # maybe even dist/RPMS/$(ARCH) ?
>  rpm: tgz
> +	@if [ -z "$(KVER)" ]; then \
> +		echo "Could not determine uts_release" ; \
> +		false ; \
> +	fi
>  	mkdir -p dist/BUILD \
>  	         dist/RPMS  \
>  	         dist/SPECS \

> _______________________________________________
> drbd-dev mailing list
> drbd-dev@lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-dev

Sincerely,
Mit freundlichen Grüßen,
    Lars Marowsky-Brée

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business	 -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"


      reply	other threads:[~2006-10-30 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061019145600.78C0B2DF6539@mail.linbit.com>
2006-10-24 14:48 ` [Drbd-dev] Re: [DRBD-cvs] svn commit by lars - r2551 - in branches/drbd-0.7: . drbd drbd/linux scripts - fix some odities in the paranoia checks of our build sy Lars Marowsky-Bree
2006-10-30 22:29   ` Lars Marowsky-Bree [this message]

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=20061030222935.GC3927@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=drbd-dev@lists.linbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox