From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15934 invoked by alias); 30 Jul 2005 16:15:12 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 15921 invoked by uid 22791); 30 Jul 2005 16:15:09 -0000 Received: from bromo.msbb.uc.edu (HELO bromo.msbb.uc.edu) (129.137.3.146) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Sat, 30 Jul 2005 16:15:09 +0000 Received: by bromo.msbb.uc.edu (Postfix, from userid 501) id EE64F1DC167; Sat, 30 Jul 2005 12:11:59 -0400 (EDT) To: howarth@bromo.msbb.uc.edu, pinskia@physics.uc.edu Subject: Re: strange error on gcc 4.1.0 Cc: gcc@gcc.gnu.org, schwab@suse.de Message-Id: <20050730161159.EE64F1DC167@bromo.msbb.uc.edu> Date: Sat, 30 Jul 2005 16:15:00 -0000 From: howarth@bromo.msbb.uc.edu (Jack Howarth) X-SW-Source: 2005-07/txt/msg01255.txt.bz2 Here is another posting which describes the problem a little clearer... http://lists.apple.com/archives/darwin-development/2003/Jun/msg00000.html So gcc needs to be fixed to not misparse -bundle, when it is the first argument to gcc, as being the "-b Machine" target option. Shouldn't the fix be fairly simple? Just requiring that the code that recognizes the -b flag require a trailing space after the -b flag...otherwise it passes over it so that -bundle could be recognized? Jack