Re: [ccache] Old code ccache hit always come back unless CCACHE_DISABLE is used

2012-06-07 Thread g . esp
- Mail original - De: g esp g@free.fr À: Joel Rosdahl j...@rosdahl.net Cc: ccache@lists.samba.org Envoyé: Mardi 5 Juin 2012 22:48:48 Objet: Re: [ccache] Old code ccache hit always come back unless CCACHE_DISABLE is used - Mail original - De: Joel Rosdahl j

Re: [ccache] Old code ccache hit always come back unless CCACHE_DISABLE is used

2012-06-02 Thread Joel Rosdahl
On 1 June 2012 12:12, g@free.fr wrote: On the no-fPIE case, using CCACHE_CPP2=1 change compilation to work. Any next recompilation even without CCACHE_CPP2=1 result in cache hit. Yes, so this means that the compiler has a bug. You should be able to reproduce it by running these two

Re: [ccache] Old code ccache hit always come back unless CCACHE_DISABLE is used

2012-06-01 Thread g . esp
- Mail original - De: Joel Rosdahl j...@rosdahl.net À: g esp g@free.fr Cc: ccache@lists.samba.org Envoyé: Mercredi 30 Mai 2012 19:53:31 Objet: Re: [ccache] Old code ccache hit always come back unless CCACHE_DISABLE is used On 30 May 2012 09:14, g@free.fr wrote: I had

[ccache] Old code ccache hit always come back unless CCACHE_DISABLE is used

2012-05-30 Thread g . esp
I had in the past an issue compiling util-linux-2.18 lscpu that was worked around adding '-fPIE -pie' to CFLAGS. The issue is that now with any new and fixed util-linux package, this workaround can't be removed or old compilation issue come back, unless CCACHE_DISABLE is used. Using the CFLAGS