From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15227 invoked by alias); 24 Oct 2012 17:25:08 -0000 Received: (qmail 15211 invoked by uid 22791); 24 Oct 2012 17:25:06 -0000 X-SWARE-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from toast.topped-with-meat.com (HELO topped-with-meat.com) (204.197.218.159) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 24 Oct 2012 17:25:02 +0000 Received: by topped-with-meat.com (Postfix, from userid 5281) id AA6E52C0A5; Wed, 24 Oct 2012 10:25:01 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Steve Ellcey Cc: Andreas Schwab , "Joseph S. Myers" , Subject: Re: [patch, mips] Fix stubs files for hard float vs. soft float In-Reply-To: Steve Ellcey's message of Wednesday, 24 October 2012 10:12:41 -0700 <1351098761.15035.52.camel@ubuntu-sellcey> References: <1350342376.2044.41.camel@ubuntu-sellcey> <1350948702.15035.5.camel@ubuntu-sellcey> <1351023590.15035.14.camel@ubuntu-sellcey> <20121023213216.B0F222C0A2@topped-with-meat.com> <1351030448.15035.25.camel@ubuntu-sellcey> <20121023224821.DA5B52C09F@topped-with-meat.com> <1351095503.15035.45.camel@ubuntu-sellcey> <1351098761.15035.52.camel@ubuntu-sellcey> Message-Id: <20121024172501.AA6E52C0A5@topped-with-meat.com> Date: Wed, 24 Oct 2012 17:25:00 -0000 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.0 cv=LtfpOghc c=1 sm=1 a=-COW8kBwH0IA:10 a=Z6MIti7PxpgA:10 a=kj9zAlcOel0A:10 a=hOe2yjtxAAAA:8 a=14OXPxybAAAA:8 a=MSnT7BQQMx0A:10 a=MX9npHgWb2UHpq_e7nQA:9 a=CjuIK1q_8ugA:10 a=WkljmVdYkabdwxfqvArNOQ==:117 X-IsSubscribed: yes Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org X-SW-Source: 2012-10/txt/msg00067.txt.bz2 There is a completely generic pattern rule near the top of Makefile that handles this. What must be missing is the dependency on that configure script. The config.status target in Makeconfig is where that dependency should be. The usual method to debug this sort of thing is to copy verbatim the text of the dependency list into the ... place in: foo:=$(shell echo>&2 'XXX ...') and then look for the XXX on stderr to see the expansion. If it omits any configure fragments that are getting run by configure, then figure out where the expansion is going wrong. You can slice up the nested variable expansions to print out intermediate values via debugging hacks as above to figure out why it's not right. Thanks, Roland