-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ccache compilation issues? #550
Comments
That cause looks plausible to me, maybe we have to be more careful passing the build command somewhere. Thanks for reporting it, hopefully we can fix it quickly. |
Cool, thanks! |
I haven't come across this, despite doing a lot of compilation. Do you think it is related to audiostream or your particular cpp lib? |
Not sure - I'll have another go at testing this when I can and will get On 10 January 2016 at 22:54, Alexander Taylor [email protected]
|
Please run your build with |
I think I actually saw that and other weird things with |
Sorry for never coming back on this. I ended up writing some custom code to disable ccache for a couple of my own cython recipes. Closing for now as seems like it might have just been me... Thanks! |
Hey guys, the new ccache compilation route causes me issues... I haven't tried to step through the code to see exactly what's going on but have included some error messages below in case you can spot anything obvious...
My problem is that i get an error when linking a bunch of compiled c++ ".o" files for one of the packages I'm including in my android distribution.
The P4A call I'm using to set off compilation looks like this:
The command executed by P4A that's going wrong looks like this:
The error message is:
If I roll back to before the ccache changes were made, e.g. 9916cb5 then I don't have this problem anymore...
Other calls to ccache that I can see were executed by P4A look like this - but the problem call above is missing the gcc part - is that the cause?
Thanks
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: