From: Andy Wingo <wingo@oblong.com>
To: notmuch@notmuchmail.org
Subject: ./configure with CC="ccache gcc" doesn't work
Date: Wed, 19 Jan 2011 17:24:57 +0100 [thread overview]
Message-ID: <m3ei8897za.fsf@oblong.com> (raw)
Hello,
On my Fedora 13 x86-64 system,
$ env | grep CC
CC=ccache gcc
$ ./configure --prefix=/usr --libdir=/usr/lib64
[...]
Checking for getline... No (will use our own instead).
Checking for strcasestr... No (will use our own instead).
Checking for rpath support... No (nothing to worry about).
Checking for -Wl,--as-needed... No (nothing to worry about).
[... success ...]
The replacement strcasestr later causes build errors:
CXX -O2 lib/directory.o
In file included from lib/notmuch-private.h:41,
from lib/directory.cc:22:
/usr/include/string.h:371: error: new declaration ‘const char* strcasestr(const char*, const char*)’
compat/compat.h:46: error: ambiguates old declaration ‘char* strcasestr(const char*, const char*)’
But if I export CC=gcc, things succeed:
Checking for getline... Yes.
Checking for strcasestr... Yes.
Checking for rpath support... Yes.
And the build goes fine.
I think the problem occurs due to the IFS setting in configure. Not
sure what the right solution is; I am not married to having ccache in the
environment. It's simply that this is what has worked in the past. If
there is a better option for using ccache I'm happy to switch, as long
as it's globally applicable.
Happy hacking,
Andy
next reply other threads:[~2011-01-19 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 16:24 Andy Wingo [this message]
2011-01-20 9:50 ` ./configure with CC="ccache gcc" doesn't work Michal Sojka
2011-01-20 12:40 ` Andy Wingo
2011-01-20 14:38 ` Michal Sojka
2011-01-26 13:38 ` Carl Worth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ei8897za.fsf@oblong.com \
--to=wingo@oblong.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).