Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] cannot find patches for mpfr package when buildroot
Date: Wed, 24 Jun 2009 22:41:18 +0200	[thread overview]
Message-ID: <87prct2wlt.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <693969.74850.qm@web53508.mail.re2.yahoo.com> (jing han's message of "Wed\, 24 Jun 2009 07\:40\:28 -0700 \(PDT\)")

>>>>> "jing" == jing han <jing_han_66@yahoo.com> writes:

 jing> Hi All,

 jing> I experienced a problem when I make MIPS64 environment. Even if
 jing> I disabled mpfr package, When I make, I still encountered the
 jing> following error:

It gets built (for the host) because it's needed by the toolchain.

 jing> --10:11:10--  http://www.mpfr.org/mpfr-2.4.1/patches
 jing> Resolving www.mpfr.org... failed: Temporary failure in name resolution.
 jing> --10:11:30--  http://buildroot.net/downloads/sources//patches
 jing> Resolving buildroot.net... 140.211.167.224
 jing> Connecting to buildroot.net|140.211.167.224|:80... connected.
 jing> HTTP request sent, awaiting response... 404 Not Found
 jing> 10:11:30 ERROR 404: Not Found.

mpfr.org is down. We have a fallback system where it will then try to
download from buildroot.net instead if that fails - Unfortunately this
doesn't work because the patch file is simply called patches on
mpfr.org and we rename it after download to mpfr-2.4.1.patch after
downloading.

I have fixed it by adding a patches -> mpfr-2.4.1.patch symlink on
buildroot.net - So it should work now.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2009-06-24 20:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 14:40 [Buildroot] cannot find patches for mpfr package when buildroot jing han
2009-06-24 20:41 ` Peter Korsgaard [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=87prct2wlt.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