From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Date: Fri, 01 Jun 2007 18:27:50 -0700 Subject: [Buildroot] mpfr error on cygwin for arm In-Reply-To: <20070601221115.GI12010@aon.at> References: <465F9792.9000200@gmail.com> <20070601094409.GA23984@aon.at> <46608246.5060008@gmail.com> <20070601221115.GI12010@aon.at> Message-ID: <4660C796.70902@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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?