Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Fatih Aşıcı" <fatih.asici@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ruby: fix build with recent openssl versions
Date: Fri, 23 May 2014 09:56:08 +0300	[thread overview]
Message-ID: <201405230956.08531.fatih.asici@gmail.com> (raw)
In-Reply-To: <537E41C3.8030904@zacarias.com.ar>

On Thursday 22 May 2014 21:28:19 Gustavo Zacarias wrote:
> On 05/22/2014 10:52 AM, Thomas Petazzoni wrote:
> > Dear Fatih A??c?,
> > 
> > On Wed, 21 May 2014 08:22:52 +0300, Fatih A??c? wrote:
> >> OpenSSL version on my system (Debian Wheezy) is 1.0.1e-2+deb7u9. When
> > 
> >> building host-ruby it fails because of an undefined macro:
> > Then we should either:
> >  1) Build host-ruby without openssl support, if it's possible and not
> >  
> >     necessary.
> >  
> >  2) Make host-ruby depend on host-openssl, but that wouldn't be really
> >  
> >     nice.
> > 
> > No? I don't think we have OpenSSL development files as part of the
> > mandatory requirements to run Buildroot, so we shouldn't rely on them.
> > I believe option (1) above is possible, because my autobuilders don't
> > have the openssl development files installed IIRC, but we don't see any
> > ruby issue.
> 
> Patch sent to disable openssl for host-ruby (option 1) since there's
> really no need for it at the moment.
> Fatih can you give it a shot and report back?

Tested your patch. It fixes the issue.

Thanks,
Fatih

      reply	other threads:[~2014-05-23  6:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 14:06 [Buildroot] [PATCH] ruby: fix build with recent openssl versions Fatih Aşıcı
2014-05-20 20:50 ` Peter Korsgaard
2014-05-21  5:22   ` Fatih Aşıcı
2014-05-22 13:52     ` Thomas Petazzoni
2014-05-22 18:28       ` Gustavo Zacarias
2014-05-23  6:56         ` Fatih Aşıcı [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=201405230956.08531.fatih.asici@gmail.com \
    --to=fatih.asici@gmail.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