From: Ralph Siemsen <ralphs@netwinder.org>
To: buildroot@busybox.net
Subject: [Buildroot] curl needs more love too
Date: Fri, 13 Jul 2007 10:12:13 -0400 [thread overview]
Message-ID: <20070713141212.GC27875@marvin.netwinder.org> (raw)
In-Reply-To: <0707081547390.3987@somehost>
On Sun, Jul 08, 2007 at 03:49:03PM +0200, Cristian Ionescu-Idbohrn wrote:
> -CURL_VERSION:=7.13.1
> +CURL_VERSION:=7.16.3
Current version seems to be 7.16.4
> - toolchain/patch-kernel.sh $(CURL_DIR) package/curl/ \*.patch*
> + toolchain/patch-kernel.sh $(CURL_DIR) package/curl curl-$(CURL_VERSION)-\*.patch*
Looks fine to me.
When cross-compiling though the configure script fails:
checking for "/dev/urandom"... configure: error: cannot check for file existence when cross compiling
I can fix this by passing --without-random, however there are plenty of
other opportunities for things to go wrong, as the Configure script
seems to do a lot of host-side inspection of headers/libraries.
How are other folks handling this situation?
-R
prev parent reply other threads:[~2007-07-13 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 13:49 [Buildroot] curl needs more love too Cristian Ionescu-Idbohrn
2007-07-13 14:12 ` Ralph Siemsen [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=20070713141212.GC27875@marvin.netwinder.org \
--to=ralphs@netwinder.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