From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Legoll Subject: Re: Binutils build failure on MIPS Date: Tue, 13 Sep 2016 16:36:07 +0200 Message-ID: References: <87h9dxukjm.fsf@gnu.org> <20160526165952.GA6576@solar> <87zirajjbk.fsf@gnu.org> <20160531193337.GA22008@solar> <87h9ddksi4.fsf_-_@gnu.org> <87ziqy3c4j.fsf@gnu.org> <87y43qu8yw.fsf@netris.org> <87r39hc1kz.fsf@netris.org> <87bn0b1two.fsf@gnu.org> <8760q3opyl.fsf@gnu.org> <878tuwyg13.fsf@gnu.org> <874m5k9pev.fsf_-_@gnu.org> <87zinc3r4b.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44827) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bjopq-0001yk-Lu for guix-devel@gnu.org; Tue, 13 Sep 2016 10:37:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bjopl-0004Vn-Gr for guix-devel@gnu.org; Tue, 13 Sep 2016 10:37:17 -0400 In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: David Craven Cc: Guix-devel On Tue, Sep 13, 2016 at 4:27 PM, David Craven wrote: > I highly doubt that binutils uses python, and I'm not sure why you > think that this is a filename - so why would unix filename matching > apply in this instance? I know it's not exactly the same, but python fnmatch is probably doing (almost) the same as bash's, and bash switch/case may also use fnmatching, that was for illustration purpose. And now after reading a bit of man bash: A case command first expands word, and tries to match it against each pattern in turn, using the same matching rules as for pathname expansion So "-*-" will match "--", "-gnu-", etc... but neither "-" nor ""... > There must be a match somewhere... Maybe, I report my findings as I go, and I've still not looked everywhere... ;-) But that looked sufficiently suspicious that I wanted to shared my findings... > Either mips64*el-*-linux means any cpu model or you've missed a part > of the matching code. I remember GCC having that spread out over > three parts of a file. I'll look harder -- Vincent Legoll