From: Kai Ruottu <karuottu@mbnet.fi>
To: gcc-help@gcc.gnu.org
Subject: Re: Should I be able to build cross gcc 4.x on Cygwin?
Date: Sun, 16 Dec 2007 19:34:00 -0000 [thread overview]
Message-ID: <47657F8B.3060304@mbnet.fi> (raw)
In-Reply-To: <312A4C08-1E67-4732-A5E4-C1C8BADFE4FB@latencyzero.com>
Rick Mann wrote:
> How can i get the combined build to not build multilib versions of
> newlib, but rather, just one version that matches the targeted processor?
The weirdest thing here is this "reinventing the wheel" !
I understood newlib already being built for the $target on MacOS X. But
for some very peculiar reason it should be reproduced for just
the same $target on Cygwin....
What will happen next ?
o the results will be compared, file by file and if there is any
difference, one of the produced GCCs outputs bad code... But which one?
This can be a good test for the "equivalency" or "similarity" of
the two GCCs on different hosts.
o the results will NOT be compared, any differences are taken as "host
dependencies", of course a Cygwin-hosted GCC produces
different code for the $target than a MacOS X hosted one... (Does
someone really believe this?)
What will the up-to-date "software engineering" books say about this
wheel-reinvention? I read my "Pressman" ("A practitioner's approach")
over 10 years ago, so I don't remember any advices for reinventions in
these things :(
I myself would TRUST that newlib done on MacOS X and would keep ONLY
that on both hosts. If some day there would be some
bugs found, the MacOS X hosted GCC would be sued or the newlib
sources.... Maybe then trying the Cygwin hosted GCC to produce
the same newlib sources would come in question.
prev parent reply other threads:[~2007-12-16 19:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 22:57 Rick Mann
2007-12-11 23:07 ` Ted Byers
2007-12-12 0:34 ` Brian Dessent
2007-12-12 2:23 ` Ted Byers
2007-12-12 2:07 ` Tim Prince
2007-12-12 22:32 ` Rick Mann
2007-12-12 23:04 ` Brian Dessent
2007-12-12 23:16 ` Rick Mann
2007-12-12 23:48 ` Brian Dessent
2007-12-13 0:02 ` Rick Mann
2007-12-13 0:06 ` Brian Dessent
2007-12-13 3:43 ` Rick Mann
2007-12-14 0:35 ` Rick Mann
2007-12-14 0:44 ` Brian Dessent
2007-12-14 0:57 ` Ted Byers
2007-12-14 2:35 ` Rick Mann
2007-12-16 19:34 ` Kai Ruottu [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=47657F8B.3060304@mbnet.fi \
--to=karuottu@mbnet.fi \
--cc=gcc-help@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).