Custom Query (5409 matches)
Results (37 - 39 of 5409)
| Ticket | Resolution | Summary | Owner | Reporter | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| #6710 | fixed | --with-system-premake is broken | |||||||||||||||||||||||||||||||||||||||||
| Description |
As reported on Phab:D3127 A made a mistake was made when adding a the Patch by sera:
|
||||||||||||||||||||||||||||||||||||||||||
| #766 | fixed | ./update-workspaces.sh fails while linking a dir | |||||||||||||||||||||||||||||||||||||||||
| Description |
When running ./update-workspaces.sh from inside the build/workspaces dir, I get the following error: /home/henner/src/0ad/libraries/spidermonkey-tip/src/build-release/config/nsinstall -R system_wrappers_js ../dist /home/henner/src/0ad/libraries/spidermonkey-tip/src/build-release/config/nsinstall: cannot make symbolic link /home/henner/src/0ad/libraries/spidermonkey-tip/src/build-release/dist/system_wrappers_js: File exists make[2]: * [export] Error 1 make[2]: Leaving directory `/home/henner/src/0ad/libraries/spidermonkey-tip/src/build-release/config' make[1]: * [export] Error 2 make[1]: * Waiting for unfinished jobs.... make[1]: Leaving directory `/home/henner/src/0ad/libraries/spidermonkey-tip/src/build-release' make: * [default] Error 2 ERROR: SpiderMonkey build failed Removing the link and running the script again does not solve the problem. Any ideas? |
||||||||||||||||||||||||||||||||||||||||||
| #6637 | fixed | .cargo directory created off user's home dir | |||||||||||||||||||||||||||||||||||||||||
| Description |
when building 0ad a .cargo directory containing a zero length .package-cache file is created from the user's home directory. This is being run on a non-debian based system (slackware) so apt is not used or present. Is there a way to prevent this directory being created outside of the extracted source tree? I test the build in an overlayfs chroot and everything else is created in the expected location. the build script is virtually the same as the one at https://slackbuilds.org/slackbuilds/15.0/games/0ad/0ad.SlackBuild updated for v 0.0.26-alpha and also uses https://slackbuilds.org/slackbuilds/15.0/games/0ad/disable-root-check.patch to allow root to create the package (as is standard for slackware packages) |
||||||||||||||||||||||||||||||||||||||||||
