From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Third Newsgroups: gmane.emacs.devel Subject: Re: Build failure in nsterm.m Date: Wed, 30 Jun 2021 19:41:27 +0100 Message-ID: References: <0e7829db-19fc-36b3-8be5-1e582e2b9a95@gmx.at> <0f96081c-5bd4-7076-2f83-decb2bcbb785@gmx.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26249"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jun 30 20:53:54 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lyfLN-0006eR-VE for ged-emacs-devel@m.gmane-mx.org; Wed, 30 Jun 2021 20:53:54 +0200 Original-Received: from localhost ([::1]:59538 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lyfLM-00061m-Ty for ged-emacs-devel@m.gmane-mx.org; Wed, 30 Jun 2021 14:53:52 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47518) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lyf9V-00026M-Mi for emacs-devel@gnu.org; Wed, 30 Jun 2021 14:41:37 -0400 Original-Received: from outbound.soverin.net ([116.202.126.228]:39003) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lyf9S-0006pd-Hr for emacs-devel@gnu.org; Wed, 30 Jun 2021 14:41:36 -0400 Original-Received: from smtp.soverin.net (unknown [10.10.3.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by outbound.soverin.net (Postfix) with ESMTPS id 7361A331; Wed, 30 Jun 2021 18:41:30 +0000 (UTC) Original-Received: from smtp.soverin.net (smtp.soverin.net [159.69.232.138]) by soverin.net DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=idiocy.org; s=soverin; t=1625078490; bh=l6X27bsP9dvabFBvLmQnSGPmrtouitbeanICKyurdO0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LHyHqa/BWoevq2bC5r7vGHui7s8WHZDYO/Vif8zvRcgiMQ8FRlvI1K5ODhKFL+4zX 8Gc9hYiQxnhqaLCjowfV13iv8xt14efhMIzGM1B1Kg32eORcGLY9vHZ/XDDG3ADCZS 7I11pwP3kgI+/+abbj4L49sKvE1Blq3LzU9BX/pgfLw9KUH+D/ktNZ70No8aI6VeCB P6xLQoa/iJOSyoho8dNsbQNuG5dMprf8pVA3tA4VUXnHJObd0kBlLJaYCrQbG5Ta35 rcYr0SA9jOFqm13Q6MXjwI3L3sYuXsKQ1vIktov5hE65/QDj+QjzHmKQFozUGsXPMa zXpUgMgZQMyiQ== Original-Received: by breton.holly.idiocy.org (Postfix, from userid 501) id A9327202CD8CA0; Wed, 30 Jun 2021 19:41:27 +0100 (BST) Mail-Followup-To: Alan Third , martin rudalics , emacs-devel Content-Disposition: inline In-Reply-To: <0f96081c-5bd4-7076-2f83-decb2bcbb785@gmx.at> Received-SPF: pass client-ip=116.202.126.228; envelope-from=alan@idiocy.org; helo=outbound.soverin.net X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:271090 Archived-At: On Wed, Jun 30, 2021 at 09:38:16AM +0200, martin rudalics wrote: > > I've pushed a fix. I think this is a shorthand way of writing an ObjC > > array that GCC doesn't understand. > > It's fixed now. Thanks! > > I'm using a version of GNUstep built from git and I can no longer > > build Emacs with GCC at all, > > In which sense does it fail? configure fails to find GNUstep requirements. There's a script to source which sets up the environment for GNUstep builds, but it makes no difference. The only thing that allows it to continue is to use "CC=clang". I imagine it's my build environment, but I followed the GNUstep instructions from their wiki and I can't work out how to get it to work. I should probably ask them. > > only clang, so these sorts of things slip > > through quite easily. > > > > I'm not sure why GCC doesn't work, I'm sure it's not the Emacs code > > that's at fault, so I have to assume that the GNUstep devs have given > > up waiting for GCC to catch up. > > Maybe we should drop a note about this somewhere. I'd rather be sure it's not just me being useless before making any official notice. -- Alan Third