From: aldot at uclibc.org <aldot@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libelf
Date: Tue, 2 Oct 2007 08:38:28 -0700 (PDT) [thread overview]
Message-ID: <20071002153828.CD59EA493F@busybox.net> (raw)
Author: aldot
Date: 2007-10-02 08:38:27 -0700 (Tue, 02 Oct 2007)
New Revision: 20174
Log:
- make sure that the target's usr/include dir exists when installing the headers
It would make sense to provide a $(PREREQ_TARGETDIR_USR_INCLUDE) prerequisite that expands to $(TARGET_DIR)/usr/include
if installing any headers was requested to fix this in a generic manner..
Modified:
trunk/buildroot/package/libelf/libelf.mk
Changeset:
Modified: trunk/buildroot/package/libelf/libelf.mk
===================================================================
--- trunk/buildroot/package/libelf/libelf.mk 2007-10-02 11:25:37 UTC (rev 20173)
+++ trunk/buildroot/package/libelf/libelf.mk 2007-10-02 15:38:27 UTC (rev 20174)
@@ -57,7 +57,9 @@
ifeq ($(BR2_PACKAGE_LIBELF_HEADERS),y)
$(TARGET_DIR)/usr/lib/libelf.so.$(LIBELF_VERSION): $(STAGING_DIR)/usr/lib/libelf.a
- $(INSTALL) $(STAGING_DIR)/usr/lib/libelf* $(@D)
+ mkdir -p $(@D)
+ cp -dpf $(STAGING_DIR)/usr/lib/libelf* $(@D)
+ mkdir -p $(TARGET_DIR)/usr/include
cp -dpR $(STAGING_DIR)/usr/include/{gelf.h,libelf*} $(TARGET_DIR)/usr/include/
$(STRIPCMD) $(STRIP_STRIP_UNNEEDED) $@
next reply other threads:[~2007-10-02 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 15:38 aldot at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-24 7:34 [Buildroot] svn commit: trunk/buildroot/package/libelf aldot at uclibc.org
2007-04-06 14:21 aldot at uclibc.org
2007-04-06 12:51 aldot at uclibc.org
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=20071002153828.CD59EA493F@busybox.net \
--to=aldot@uclibc.org \
--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