public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rick Mann <rmann@latencyzero.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Should I be able to build cross gcc 4.x on Cygwin?
Date: Fri, 14 Dec 2007 00:35:00 -0000	[thread overview]
Message-ID: <312A4C08-1E67-4732-A5E4-C1C8BADFE4FB@latencyzero.com> (raw)
In-Reply-To: <38838301-426B-4654-9523-108844F2AF17@latencyzero.com>

Brian, Tim, Ted: Thank you for your help.

I seem to be building GCC now under Cygwin. However, it's going VERY  
slowly. The desktops we have here are generations behind my MacBook  
Pro, it appears.

This is really a newlib question, but traffic seems light on that list.

How can i get the combined build to not build multilib versions of  
newlib, but rather, just one version that matches the targeted  
processor?

Is it enough to specify

--disable-multilib

or must I do something in addition?

TIA,
Rick

  reply	other threads:[~2007-12-14  0:35 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 [this message]
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

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=312A4C08-1E67-4732-A5E4-C1C8BADFE4FB@latencyzero.com \
    --to=rmann@latencyzero.com \
    --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).