Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] curl sagmentatation fault - > is openssl the culprit ?
Date: Fri, 16 Mar 2012 16:53:39 +0100	[thread overview]
Message-ID: <201203161653.39678.arnout@mind.be> (raw)
In-Reply-To: <F4A167A0B310422C906F05845738AE17@JohanW7>

On Friday 16 March 2012 15:52:53 Sagaert Johan wrote:
> Hi
> 
> Things are not always what they seem:
> 
> It seems to me that when the configure script of curl runs it checks for openssh, if none is found
> Then it is build without openssl.

 Hm, could be.  Maybe try if other programs work with openssl, e.g. 
lighttpd (make sure you configure it to use openssl).

 But of course, that doesn't tell you what the real problem is...  You'll 
still need to get a strack trace.

[snip]

 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-03-16 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 14:52 [Buildroot] curl sagmentatation fault - > is openssl the culprit ? Sagaert Johan
2012-03-16 15:53 ` Arnout Vandecappelle [this message]
2012-03-16 16:08   ` [Buildroot] curl sagmentatation fault - > is openssl theculprit ? Sagaert Johan
2012-03-16 16:32     ` Gustavo Zacarias

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=201203161653.39678.arnout@mind.be \
    --to=arnout@mind.be \
    --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