From: Tom <fivemiletom@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] mpfr error on cygwin for arm
Date: Fri, 01 Jun 2007 18:27:50 -0700 [thread overview]
Message-ID: <4660C796.70902@gmail.com> (raw)
In-Reply-To: <20070601221115.GI12010@aon.at>
Bernhard Fischer wrote:
> On Fri, Jun 01, 2007 at 01:32:06PM -0700, Tom wrote:
>> Hi Bernhard,
>>
>> Per your request, now attached the patch cygwin-3a.svndiff as an svn
>> diff to the current trunk.
>
> Well, that one applies cleanly, thanks, but you do not use the
> corrected extensions at all?
>
> How does that help with building a useable rootfs? Just curious..
This patch is only the first step. It got me past gmp and mpfr. This has
been good enough to build a cygwin toolchain with a host gdb, which in
turn has been used to compile, debug and run a kernel :).
Maybe this is also good enough for a first check-in, is it?
I see that more work is ahead of me before I can build the rootfs, and
it would be good if I can verify my understanding of what needs to be
done, using mpfr as an example:
-I need to change package/mpfr/mpfr.mk (hardcoded extensions, maybe
strip cmd).
-This package/mpfr folder is the only place where I can make changes;
anything else about the mpfr module just downloaded / configured code,
right?
next prev parent reply other threads:[~2007-06-02 1:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <465F9792.9000200@gmail.com>
[not found] ` <20070601094409.GA23984@aon.at>
2007-06-01 20:31 ` [Buildroot] mpfr error on cygwin for arm] Tom
2007-06-01 20:32 ` [Buildroot] mpfr error on cygwin for arm Tom
2007-06-01 22:11 ` Bernhard Fischer
2007-06-02 1:27 ` Tom [this message]
2007-06-02 8:41 ` Bernhard Fischer
2007-05-25 14:49 [Buildroot] ALSA for build root Rod Boyce
2007-05-25 19:23 ` [Buildroot] Package selection question Tom
2007-05-25 20:03 ` Bernhard Fischer
[not found] ` <4657D353.7030704@gmail.com>
2007-05-26 6:33 ` [Buildroot] mpfr error on cygwin for arm Tom
[not found] ` <4657D933.8060109@gmail.com>
2007-05-26 9:48 ` Bernhard Fischer
2007-05-30 3:07 ` Tom
2007-05-30 9:47 ` Bernhard Fischer
2007-05-30 16:03 ` Tom
2007-05-31 7:33 ` Tom
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=4660C796.70902@gmail.com \
--to=fivemiletom@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 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.