From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/gettext
Date: Wed, 23 Jul 2008 23:42:17 +1000 [thread overview]
Message-ID: <20080723134217.GC27147@cloud.net.au> (raw)
In-Reply-To: <20080723103550.70E8B3C7D7@busybox.net>
On Wed, Jul 23, 2008 at 03:35:50AM -0700, jacmet at uclibc.org wrote:
> Author: jacmet
> Date: 2008-07-23 03:35:50 -0700 (Wed, 23 Jul 2008)
> New Revision: 22929
>
> Log:
> gettext: also remove from staging on -clean
>
> Modified:
> trunk/buildroot/package/gettext/gettext.mk
>
>
> Changeset:
> Modified: trunk/buildroot/package/gettext/gettext.mk
> ===================================================================
> --- trunk/buildroot/package/gettext/gettext.mk 2008-07-23 08:41:08 UTC (rev 22928)
> +++ trunk/buildroot/package/gettext/gettext.mk 2008-07-23 10:35:50 UTC (rev 22929)
> @@ -125,6 +125,7 @@
> gettext-unpacked: $(GETTEXT_DIR)/.unpacked
>
> gettext-clean:
> + -$(MAKE) DESTDIR=$(STAGING_DIR) CC=$(TARGET_CC) -C $(GETTEXT_DIR) uninstall
> -$(MAKE) DESTDIR=$(TARGET_DIR) CC=$(TARGET_CC) -C $(GETTEXT_DIR) uninstall
> -$(MAKE) -C $(GETTEXT_DIR) clean
This demonstrates another problem with sharing the build_$(ARCH) (and
particularly build_$(ARCH)/staging-dir) between projects built out of
the same tree.. running gettext-clean (probably among others) on one
project trashes the staging directory for others. Rebuilding those will
reinstall it in the staging directory I suppose.
Personally I think the shared build_$(ARCH) is just wrong with multiple
projects. I might hack my local copy to define BUILD_DIR to match
PROJECT_BUILD_DIR to fix this.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-07-23 13:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 10:35 [Buildroot] svn commit: trunk/buildroot/package/gettext jacmet at uclibc.org
2008-07-23 13:42 ` Hamish Moffatt [this message]
2008-07-23 14:23 ` Bernhard Fischer
2008-07-26 7:28 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2008-10-27 9:45 jacmet at uclibc.org
2007-09-05 6:50 ulf at uclibc.org
2007-08-12 23:36 ulf at uclibc.org
2007-07-27 7:29 ulf at uclibc.org
2007-07-23 8:35 ulf at uclibc.org
2007-07-16 10:00 ulf at uclibc.org
2007-07-08 18:58 aldot at uclibc.org
2007-06-20 12:10 aldot at uclibc.org
2007-01-16 1:29 sjhill at uclibc.org
2007-01-15 21:28 andersen at uclibc.org
2007-01-14 3:09 sjhill at uclibc.org
2007-01-10 10:30 andersen at uclibc.org
2007-01-10 6:05 andersen at uclibc.org
2006-07-19 17:06 vapier
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=20080723134217.GC27147@cloud.net.au \
--to=hamish@cloud.net.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox