Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/openssl
Date: Tue, 08 Jul 2008 15:45:59 +0200	[thread overview]
Message-ID: <87vdzgh4ko.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <d6cda7730807080635m5c2949e2me4b4cca844e82e07@mail.gmail.com> ("Thiago A. Corrêa"'s message of "Tue\, 8 Jul 2008 10\:35\:21 -0300")

>>>>> "Thiago" == Thiago A Corr?a <thiago.correa@gmail.com> writes:

Hi,

 >> I don't get it, how do the files get installed into TARGET_DIR?
 >> 
 Thiago> Oh, that's because in the google repository it was made in different
 Thiago> commits, but there John changed it to use make install instead. He was
 Thiago> looking into the issue of having Midori and other packages connect to
 Thiago> https servers. To fix that, besides having a proper openssl install,
 Thiago> one needs to install the CA certificates. But none the less make
 Thiago> install is better than copying individual files.

Yes, if it doesn't install a bunch of unneeded stuff.

 Thiago> $(STAGING_DIR)/usr/lib/libcrypto.a: $(OPENSSL_DIR)/apps/openssl
 Thiago>         $(MAKE) CC=$(TARGET_CC) INSTALL_PREFIX=$(STAGING_DIR)/usr -C
 Thiago> $(OPENSSL_DIR) install
 Thiago>         $(MAKE) CC=$(TARGET_CC) INSTALL_PREFIX=$(TARGET_DIR) -C
 Thiago> $(OPENSSL_DIR) install

Ahh, we normally put those in seperate targets
($TARGET_DIR)/usr/lib/libcrypto... )

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2008-07-08 13:45 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 10:13 [Buildroot] svn commit: trunk/buildroot/package/openssl ulf at uclibc.org
2008-07-08 10:31 ` Peter Korsgaard
2008-07-08 12:04 ` Hamish Moffatt
2008-07-08 12:25   ` Thiago A. Corrêa
2008-07-08 12:39     ` Peter Korsgaard
2008-07-08 13:16       ` Thiago A. Corrêa
2008-07-08 13:29         ` Peter Korsgaard
2008-07-08 13:35           ` Thiago A. Corrêa
2008-07-08 13:45             ` Peter Korsgaard [this message]
2008-07-08 14:56               ` Thiago A. Corrêa
2008-07-08 15:02                 ` Peter Korsgaard
2008-07-08 15:34                   ` John Voltz
2008-07-08 15:42                     ` John Voltz
2008-07-08 16:30             ` Ulf Samuelsson
2008-07-08 16:48         ` Ulf Samuelsson
  -- strict thread matches above, loose matches on Subject: below --
2009-03-05 13:48 jacmet at uclibc.org
2009-02-24  0:37 hamish at uclibc.org
2009-01-21 20:31 jacmet at uclibc.org
2009-01-06 11:59 jacmet at uclibc.org
2008-12-28 16:08 jacmet at uclibc.org
2009-01-06 11:38 ` Mark Jackson
2009-01-06 12:00   ` Peter Korsgaard
2009-01-06 13:25     ` Mark Jackson
2008-10-13  8:10 egtvedt at uclibc.org
2008-10-07  7:11 egtvedt at uclibc.org
2008-09-24  9:12 egtvedt at uclibc.org
2008-09-24  9:10 egtvedt at uclibc.org
2008-07-08 13:49 jacmet at uclibc.org
2008-07-08  6:40 hamish at uclibc.org
2008-07-08  9:36 ` Ulf Samuelsson
2008-07-08 12:03   ` Hamish Moffatt
2008-07-05  7:25 ulf at uclibc.org
2008-07-05 15:55 ` Thiago A. Corrêa
2008-07-05 21:59   ` Ulf Samuelsson
2008-07-05  6:54 ulf at uclibc.org
2007-08-13 19:35 ulf at uclibc.org
2007-08-11 16:55 ulf at uclibc.org
2007-04-06 15:01 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=87vdzgh4ko.fsf@macbook.be.48ers.dk \
    --to=jacmet@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