Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: "Philipp Hug" <philipp@hug.cx>
To: "Helmut Wollmersdorfer" <helmut@wollmersdorfer.at>,
	<drbd-dev@lists.linbit.com>
Subject: Re: [Drbd-dev] 0.7.5 release tomorrow...
Date: Wed, 6 Oct 2004 09:24:07 +0200	[thread overview]
Message-ID: <060901c4ab75$7752e0a0$532210ac@morpheus> (raw)
In-Reply-To: 416315AF.80004@wollmersdorfer.at

> [...]
> cd user && /usr/bin/make
> make[1]: Entering directory `/home/helmut/drbd-0.7.5/user'
> gcc -c -Wall -I../drbd   -c -o drbdsetup.o drbdsetup.c
> make[1]: *** No rule to make target `../drbd/drbd_buildtag.o', needed by 
> `drbdsetup'.  Stop.
> make[1]: Leaving directory `/home/helmut/drbd-0.7.5/user'
> make: *** [build-arch-stamp] Error 2
> 
> After
>    make install-tools
> as workaround it builds .debs and works the usual debian way.
Shouldn't drbd_buildtag.c be included in the release tarball?
If not, I'll add the workaround to the debian packaging...

> Next item:
> Whatever the reason is, the following is necessary with current packaging
> 
> xp2400:/home/helmut# mv /lib/modules/2.4.26/kernel/drivers/block/drbd.o 
> /lib/modules/2.4.26-1-386/kernel/drivers/block/drbd.o

How did you build the kernel module? module-assistant? make-kpkg?
anyway: looks like a bug... I'll fix it..

philipp

  parent reply	other threads:[~2004-10-06  7:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29  8:54 [Drbd-dev] 0.7.5 release tomorrow Philipp Reisner
2004-09-29 15:55 ` Lars Ellenberg
2004-09-29 21:40 ` Philipp Hug
2004-09-30 12:10 ` Philipp Reisner
2004-09-30 15:46   ` Philipp Hug
2004-10-05 21:44     ` Helmut Wollmersdorfer
2004-10-05 23:28       ` Helmut Wollmersdorfer
2004-10-06  7:24       ` Philipp Hug [this message]
2004-10-06  9:32         ` Helmut Wollmersdorfer
2004-10-06  9:38         ` Lars Ellenberg
2004-10-06 13:48           ` Helmut Wollmersdorfer

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='060901c4ab75$7752e0a0$532210ac@morpheus' \
    --to=philipp@hug.cx \
    --cc=drbd-dev@lists.linbit.com \
    --cc=helmut@wollmersdorfer.at \
    /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