All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Rempel <razzor@kopf-tisch.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHES] device-mapper is now included in LVM2
Date: Tue, 16 Jun 2009 10:38:04 +0200	[thread overview]
Message-ID: <20090616103804.639700ab@bandomeer.europe.flane.local> (raw)
In-Reply-To: <4A365D42.5000006@lbsd.net>

On Mon, 15 Jun 2009 14:40:02 +0000
Nigel Kukard <nkukard@lbsd.net> wrote:

> 
> > I think this should close bug 241?
> >
> > https://bugs.busybox.net/show_bug.cgi?id=241
> >   
> 
> Yep ... lets just wait a day or so and see if everyone is happy  :)

Why no conversion to Makefile.autotools.in?

The clean target is not working:
> lvm2-clean:
> 	$(MAKE) DESTDIR=$(TARGET_DIR) -C $(LVM2_DIR) uninstall
make[1]: Entering directory `/home/development/buildroot/build_i586/LVM2.2.02.47'
make[1]: *** No rule to make target `uninstall'.  Stop.
make[1]: Leaving directory `/home/development/buildroot/build_i586/LVM2.2.02.47'

I've attached an updated version of my patch (against current HEAD) which 
doesn't use post_install_hooks for stripping the binaries. Seems to be cleaner.

Regards
Olaf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-device-mapper-lvm2-build-together-take-2.patch
Type: text/x-patch
Size: 14818 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090616/44dfb648/attachment-0001.bin>

  reply	other threads:[~2009-06-16  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 14:34 [Buildroot] [PATCHES] device-mapper is now included in LVM2 Nigel Kukard
2009-06-15 14:40 ` Will Newton
2009-06-15 14:40   ` Nigel Kukard
2009-06-16  8:38     ` Olaf Rempel [this message]
2009-06-20  5:20 ` Peter Korsgaard

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=20090616103804.639700ab@bandomeer.europe.flane.local \
    --to=razzor@kopf-tisch.de \
    --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 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.