From: Andy Wingo <wingo@oblong.com>
To: Michal Sojka <sojkam1@fel.cvut.cz>
Subject: Re: ./configure with CC="ccache gcc" doesn't work
References: <m3ei8897za.fsf@oblong.com> <87zkqvnbu7.fsf@steelpick.2x.cz>
Date: Thu, 20 Jan 2011 13:40:01 +0100
In-Reply-To: <87zkqvnbu7.fsf@steelpick.2x.cz> (Michal Sojka's message of "Thu,
 	20 Jan 2011 10:50:08 +0100")
Message-ID: <m339on7nq6.fsf@oblong.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: notmuch@notmuchmail.org
Precedence: list

Hi Michal,

On Thu 20 Jan 2011 10:50, Michal Sojka <sojkam1@fel.cvut.cz> writes:

> Hmm, the IFS thing in configure seems annoying in this case. But you can
> create a little script containing
>
>   exec ccache gcc "$@"
>
> and set CC to the name of the script, cannot you?

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.

And, oddly enough, the $CC does succeed in compiling, modulo this build
error -- so it seems that the $IFS isn't actually providing any benefit
in this case.  (If the IFS did its job, I would expect to see an error
like "ccache gcc: command not found" or something.)

Andy