ccache gives winebuild errors?
Hallo, Since a couple of days make fails without giving much reason why: | make[3]: Entering directory `/usr/home/projects/wine/mywine/dlls/ddraw/tests' | WINEBUILD=../../../tools/winebuild/winebuild ../../../tools/winegcc/winegcc -mconsole ddrawmodes.o testlist.o -o ddraw_test.exe.so -L../../../libs/port -lwine_port -L../../../dlls -L../../../libs -lddraw -luser32 -lgdi32 -lkernel32 -lm | Error: ccache gcc failed. | make[3]: *** [ddraw_test.exe.so] Error 2 | make[3]: Leaving directory `/usr/home/projects/wine/mywine/dlls/ddraw/tests' | make[2]: *** [tests] Error 2 | make[2]: Leaving directory `/usr/home/projects/wine/mywine/dlls/ddraw' | make[1]: *** [ddraw] Error 2 | make[1]: Leaving directory `/usr/home/projects/wine/mywine/dlls' | make: *** [dlls] Error 2 This is after a "make clean". Wine is configured to use ccache by setting CC="ccache gcc" before the ./configure && make depend && make. After another make clean and setting CC=gcc, the make succeeds. Any idea? Rein. -- Rein Klazes rklazes(a)xs4all.nl
Rein Klazes wrote:
Hallo,
Since a couple of days make fails without giving much reason why:
| make[3]: Entering directory `/usr/home/projects/wine/mywine/dlls/ddraw/tests' | WINEBUILD=../../../tools/winebuild/winebuild ../../../tools/winegcc/winegcc -mconsole ddrawmodes.o testlist.o -o ddraw_test.exe.so -L../../../libs/port -lwine_port -L../../../dlls -L../../../libs -lddraw -luser32 -lgdi32 -lkernel32 -lm | Error: ccache gcc failed. | make[3]: *** [ddraw_test.exe.so] Error 2 | make[3]: Leaving directory `/usr/home/projects/wine/mywine/dlls/ddraw/tests' | make[2]: *** [tests] Error 2 | make[2]: Leaving directory `/usr/home/projects/wine/mywine/dlls/ddraw' | make[1]: *** [ddraw] Error 2 | make[1]: Leaving directory `/usr/home/projects/wine/mywine/dlls' | make: *** [dlls] Error 2
This is after a "make clean". Wine is configured to use ccache by setting CC="ccache gcc" before the ./configure && make depend && make.
After another make clean and setting CC=gcc, the make succeeds.
Any idea?
Rein.
Is it possible that you changed either gcc or ccache versions? Try erasing the ccache cache folder (~/.ccache, if I remeber correctly), and then running it again. Shachar -- Shachar Shemesh Lingnu Open Systems Consulting http://www.lingnu.com/
On Sun, 07 Mar 2004 01:19:50 +0200, you wrote:
Is it possible that you changed either gcc or ccache versions? Try erasing the ccache cache folder (~/.ccache, if I remeber correctly), and then running it again.
I did that, did not make a difference. Moreover ccache -s does not log a failure. After consulting the man page, I have it working now by soft linking /usr/local/bin/gcc to /usr/bin/ccache, and setting CC=gcc . So it seems something in configure/winebuild/winegcc doesn't like spaces in the $CC value. Rein. -- Rein Klazes rklazes(a)xs4all.nl
On March 7, 2004 2:35 am, Rein Klazes wrote:
So it seems something in configure/winebuild/winegcc doesn't like spaces in the $CC value.
That's correct, winegcc expects $CC to be a program without arguments. I don't think we can easily change that (well, we could but in that case we wouldn't be able to support $CC with embedded spaces, which is not good). -- Dimi.
"Dimitrie O. Paun" <dpaun(a)rogers.com> writes:
That's correct, winegcc expects $CC to be a program without arguments. I don't think we can easily change that (well, we could but in that case we wouldn't be able to support $CC with embedded spaces, which is not good).
make is using $CC the same way, so I don't think that's an issue. If $CC has embedded spaces they will need to be escaped in the makefile, and winegcc can then deal with the escapes the same way the shell does. -- Alexandre Julliard julliard(a)winehq.org
On March 7, 2004 7:37 pm, Alexandre Julliard wrote:
make is using $CC the same way, so I don't think that's an issue. If $CC has embedded spaces they will need to be escaped in the makefile, and winegcc can then deal with the escapes the same way the shell does.
This seems like real low priority however. It's a corner case that's not worth worrying about at this point. There are much better workarouds that don't depend on this (rather strange) trick. -- Dimi.
"Dimitrie O. Paun" <dpaun(a)rogers.com> writes:
This seems like real low priority however. It's a corner case that's not worth worrying about at this point. There are much better workarouds that don't depend on this (rather strange) trick.
Escaping the spaces is really low priority I agree, especially since it probably doesn't work with configure anyway. Supporting CC="ccache gcc" is more important IMO, and seems pretty trivial to do. -- Alexandre Julliard julliard(a)winehq.org
participants (4)
-
Alexandre Julliard -
Dimitrie O. Paun -
Rein Klazes -
Shachar Shemesh