On Wed, Sep 20, 2017 at 4:29 PM, Michael Niedermayer <mich...@niedermayer.cc> wrote: > > On Tue, Sep 19, 2017 at 04:54:16PM -0700, Jacob Trimble wrote: > > Signed-off-by: Jacob Trimble <modma...@google.com> > > --- > > configure | 16 ++++++++-------- > > 1 file changed, 8 insertions(+), 8 deletions(-) > > breaks build with ccache > > ./configure --cc='ccache gcc' > ccache gcc is unable to create an executable file. > If ccache gcc is a cross-compiler, use the --enable-cross-compile option. > Only do this if you know what cross compiling means. > C compiler test failed. > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Let us carefully observe those good qualities wherein our enemies excel us > and endeavor to excel them, by avoiding what is faulty, and imitating what > is excellent in them. -- Plutarch > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel >
But without this, you can't have a compiler path that has a space in it. Plus, AFAIK, there is no way to escape the space through a bash variable. Meaning there is no way for $cc to have an escaped space in it. Is this just something that won't be supported? _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
