Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 00ADE431FD0 for ; Wed, 26 Jan 2011 05:38:30 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.99 X-Spam-Level: X-Spam-Status: No, score=-0.99 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, T_MIME_NO_TEXT=0.01] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1t2Q+a3cmfYr; Wed, 26 Jan 2011 05:38:30 -0800 (PST) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 150DB431FB5; Wed, 26 Jan 2011 05:38:30 -0800 (PST) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id 437322540DE; Wed, 26 Jan 2011 23:38:29 +1000 (EST) From: Carl Worth To: Michal Sojka , Andy Wingo Subject: Re: ./configure with CC="ccache gcc" doesn't work In-Reply-To: <87mxmv4p3k.fsf@steelpick.2x.cz> References: <87zkqvnbu7.fsf@steelpick.2x.cz> <87mxmv4p3k.fsf@steelpick.2x.cz> User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.2.1 (i486-pc-linux-gnu) Date: Wed, 26 Jan 2011 23:38:29 +1000 Message-ID: <8762tb23ai.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Cc: notmuch@notmuchmail.org X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2011 13:38:31 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Thu, 20 Jan 2011 15:38:39 +0100, Michal Sojka wrot= e: > On Thu, 20 Jan 2011, Andy Wingo wrote: > > Sure. But the ccache thing is fairly common, AFAIK, and IMO notmuch's > > configure should either handle spaces in a non-absolute-path $CC or exit > > with an error in that case. Hi Andy, Thanks for pointing out the bug. I didn't notice this because I get ccache by putting a symlink in ~/bin/cc -> /usr/bin/ccache. I hadn't expected the IFS change to cause any problem like this, but there it is. > I went through configure in notmuch and it seems that there is only one > place where the value of IFS matters (the call to ldconfig), so we may > want to apply the patch bellow. On the other hand, a brief look at > Makefile reveals that there are many things that wont work if there are > spaces in filanames[1], so I'm not sure whether to care about that > single case at all. Thanks for the analysis. I've committed this change now. > [1] For example most commands in install targets contain unquoted > parameters so if DESTDIR contains a space, it wont work. I've run through and fixed all of these that I saw. And I did a quick test with: make DESTDIR=3D"/tmp/bar baz" install and it at least seems to work. I agree that this kind of thing is probably not likely to happen often. But since I did decide to invent my own build system, I feel I have an obligation to make it as "correct" as possible. =2DCarl =2D-=20 carl.d.worth@intel.com --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFNQCPV6JDdNq8qSWgRAiYnAKCNMtMjVs069slYYaLca8kIdnB8BgCdHkAI GmPYvBcvKNxOcVggcNJnQpU= =KBEy -----END PGP SIGNATURE----- --=-=-=--