Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 345] New: libcurl package needs a urandom fix
Date: Fri, 22 May 2009 13:21:10 +0000 (UTC)	[thread overview]
Message-ID: <bug-345-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=345

              Host: i686-linux
            Target: arm-softfloat-linux-uclibcgnueabi
           Summary: libcurl package needs a urandom fix
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: gustavo at zacarias.com.ar
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=343)
 --> (https://bugs.busybox.net/attachment.cgi?id=343)
Fix libcurl's urandom needs

Doing a huge test-build for 2009.05-rc2 i've found that the libcurl package
only specifies the random (/dev/urandom) device to configure when building
against openssl.
But it requires this when building in general so the patch specifies the random
device always instead of conditionally, otherwise the build breaks with the
dreaded "can't determine random device when cross compiling".


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2009-05-22 13:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 13:21 bugzilla at busybox.net [this message]
2009-05-22 20:15 ` [Buildroot] [Bug 345] libcurl package needs a urandom fix bugzilla at busybox.net
2009-05-22 20:20 ` bugzilla at busybox.net
2009-05-23  6:53 ` bugzilla at busybox.net
2009-05-26 17:10 ` bugzilla at busybox.net
2009-05-26 17:52 ` bugzilla at busybox.net
2009-05-27 18:23 ` bugzilla at busybox.net

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=bug-345-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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