On 22 September 2012 11:43, Joel Rosdahl j...@rosdahl.net wrote:
On 18 September 2012 18:21, Eitan Adler li...@eitanadler.com wrote:
I needed the following patch for ccache to build with clang.
[...]
-all_cppflags = @DEFS@ @extra_cppflags@ -DSYSCONFDIR=$(sysconfdir) -I.
-I$(srcdir) $(CPPFLAGS
~ ]%clang -Wall -Wextra b.c
[9852 eitan@radar ~ ]%/usr/local/bin/clang -I. -I. -Wall -Wextra b.c
[9853 eitan@radar ~ ]%/usr/local/bin/clang -I. -I. -Wall -Wextra -c b.c
[9854 eitan@radar ~ ]%
[9856 eitan@radar ~ ]%b.c
#include stdio.h
int main(void) {
return 0;
}
--
Eitan Adler
On 23 September 2012 12:31, Joel Rosdahl j...@rosdahl.net wrote:
On 23 September 2012 14:40, Eitan Adler li...@eitanadler.com wrote:
After some more experimentation this seems to only happen under ccache
OK. Then this is another instance of
https://bugzilla.samba.org/show_bug.cgi?id=8118
are
passed.
Awesome! Thanks!
--
Eitan Adler
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman/listinfo/ccache
to disable caching when particular flags are present
so it should be a one-line fix.
I'd rather off-by-default rather than on. ccache should be
conservative about it can cache if it doesn't know (or at least warn
for unknown plugins).
--
Eitan Adler
is for the simple /bin/bash option.
The followup to this discussion indicates that /bin/sh seems to be
sufficient (I need to check this myself when I get a chance).
checkbashims sees nothing wrong.
--
Eitan Adler
___
ccache mailing list
ccache@lists.samba.org
https
have to modify the upstream default
except in extreme cases. This makes things confusing for the users and
results in weird questions on the mailing lists.
--
Eitan Adler
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman
false. /usr/local/bin or /opt/bin might be the correct location.
if the script is intended to be POSIX shell,
then /bin/sh is the correct answer.
Agreed.
using env is just stupid.
only if you don't care about portability.
POSIX env absolute path
--
Eitan Adler
On 11 November 2012 00:46, Mike Frysinger vap...@gentoo.org wrote:
On Saturday 10 November 2012 00:41:52 Eitan Adler wrote:
On 10 November 2012 00:41, Mike Frysinger wrote:
if the script is written in bash and is intended to be, then
/bin/bash is the correct answer.
Absolutely false. /usr
what's wrong with that command. gcc isn't supposed to
rely on the PATH to find cc1, but presumably it's something environmental.
Can you get a ktrace (or strace) of what gcc is doing with and without CCACHE ?
--
Eitan Adler
___
ccache mailing list
ccache
On 12 November 2012 13:00, Eitan Adler li...@eitanadler.com wrote:
On 12 November 2012 06:03, Andrew Stubbs a...@codesourcery.com wrote:
Running sh -x test.sh shows that the gcc command producing the error:
+ CCACHE_DISABLE=1 gcc -c test1.c -o reference_test1.o -O -O
gcc: error trying to exec
On 12 November 2012 13:11, Eitan Adler li...@eitanadler.com wrote:
On 12 November 2012 13:04, Mike Frysinger vap...@gentoo.org wrote:
yes, when people tell you forcing asinine behavior is wrong, you label them
trolls. i guess that's how you win arguments.
Claiming that systems without /bin
' and not
'gcc' or 'clang'. IMHO this use case is the most important.
Why can't you ask the compiler via cc --version or the like?
--
Eitan Adler
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman/listinfo/ccache
that existing disk
caching does not help you?
--
Eitan Adler
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman/listinfo/ccache
14 matches
Mail list logo
