From: Emmanuel Riou <riou.emmanuel@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] mpfr-2.4.1.patch not found
Date: Thu, 24 Sep 2009 15:40:39 +0100 [thread overview]
Message-ID: <4ABB84E7.9070001@gmail.com> (raw)
In-Reply-To: <87r5tw63jp.fsf@macbook.be.48ers.dk>
Peter Korsgaard wrote:
>>>>>> "Austin" == Austin Foxley <austinf@cetoncorp.com> writes:
>
> Austin> On 09/23/2009 11:12 PM, Ormund Williams wrote:
> >> /bin/sh: ./../dl/mpfr-2.4.1.patch: No such file or directory
> >> make: *** [.../buildroot/output/toolchain/mpfr-2.4.1/.unpacked] Error 1
> >>
> >> Where is this patch suppose to come from?
>
> Austin> http://www.mpfr.org/mpfr-2.4.1/mpfr-2.4.1.patch I would think, but that gives me
> Austin> a 404 currently.
>
> http://www.mpfr.org/mpfr-2.4.1/patches to be exact, but we rename that
> unlucky filename to mpfr-2.4.1.patch after downloading (see mpfr.mk).
>
> It's on the mirror as well:
>
> http://buildroot.net/downloads/sources/mpfr-2.4.1.patch
>
I have just experienced the problem. It looks like this is a relative
path issue actually:
When you look at mpfr.mk the patch command is the following:
( cd $(MPFR_DIR); patch -p1 -N -Z < $(MPFR_PATCH_SOURCE); )
with MPFR_PATCH_SOURCE:=$(DL_DIR)/$(MPFR_PATCH_FILE) which is replaced
in my case by ./dl/mpfr-2.4.1.patch where it should be an absolute path.
Emmanuel.
next prev parent reply other threads:[~2009-09-24 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 6:12 [Buildroot] mpfr-2.4.1.patch not found Ormund Williams
2009-09-24 6:36 ` Austin Foxley
2009-09-24 6:38 ` Austin Foxley
2009-09-24 10:27 ` Peter Korsgaard
2009-09-24 14:40 ` Emmanuel Riou [this message]
[not found] ` <4ABB81D2.4060602@gmail.com>
2009-09-24 15:19 ` Peter Korsgaard
2009-09-24 15:32 ` Emmanuel Riou
2009-09-24 18:54 ` Ormund Williams
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=4ABB84E7.9070001@gmail.com \
--to=riou.emmanuel@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.