From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] fix host-openssl binary installation
Date: Fri, 19 Feb 2016 11:36:14 +0100 [thread overview]
Message-ID: <87fuwphtr5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAJjDOTkbynNqt_19U_W+Nmn7iDHL9t9GuCREzo8ak6R6HaO_vg@mail.gmail.com> (matthew amlogic shyu's message of "Fri, 19 Feb 2016 18:33:44 +0800")
>>>>> "matthew" == matthew amlogic shyu <matthew.shyu.amlogic@gmail.com> writes:
Hi,
>> But we only pass INSTALL_PREFIX=$(STAGING_DIR)/usr during the
>> make-install-to-staging step, and not when we configure/build/install
>> the host variant:
>>
>> define OPENSSL_INSTALL_STAGING_CMDS
>> $(MAKE) -C $(@D) INSTALL_PREFIX=$(STAGING_DIR) install
>> endef
>>
>> define HOST_OPENSSL_INSTALL_CMDS
>> $(MAKE) -C $(@D) install
>> endef
>>
>> define OPENSSL_INSTALL_TARGET_CMDS
>> $(MAKE) -C $(@D) INSTALL_PREFIX=$(TARGET_DIR) install
>> rm -rf $(TARGET_DIR)/usr/lib/ssl
>> rm -f $(TARGET_DIR)/usr/bin/c_rehash
>> endef
>>
>> So I'm still not sure what you are trying to solve?
> Ha, you're right!
> I found that I have a stupid package inside my Buildroot tree that's
> exporting INSTALL_PREFIX during the build and thus messing up my
> environment.
> There's nothing wrong with host-openssl package.
Ahh, that explains it ;)
> My bad. Sorry.
No problem. I've marked you patch as rejected in patchwork.
--
Venlig hilsen,
Peter Korsgaard
prev parent reply other threads:[~2016-02-19 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 10:41 [Buildroot] [PATCH 1/1] fix host-openssl binary installation Matthew Shyu
2016-02-17 15:02 ` Peter Korsgaard
2016-02-18 1:05 ` matthew.amlogic shyu
2016-02-19 10:18 ` Peter Korsgaard
2016-02-19 10:33 ` matthew.amlogic shyu
2016-02-19 10:36 ` Peter Korsgaard [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=87fuwphtr5.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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