Closed SamTechnologeek closed 11 years ago
@r4d2 @jdiez17 Deployed is built on stable branch. Might be worth merging sometime in the future.
@SamTechnologeek which deployable do you use? .deb or .rpm? I'll build the one you require from master branch, and you can try that :)
@Mause .deb of course!
P.O.S file sharing site, but here, try this; http://www.filedropper.com/dcputoolchain-01a7c902d41-linux
That is build on master branch, so if master has a fix for it, it should be in that
Actually the way that TOOLCHAIN_KERNELS (and other similar variables) work for deployable builds is that it gets embedded as the default path into the binary, but is still overriddable. In non-deployed versions, it does not include these paths into the executables as the build does not know where it expects to be installed. The environment variables can be used to override these paths in both deployable and non-deployable versions, however, since the non-deployed versions never have a default path to start with, they require the environment variable to be set.
@Mause that worked perfectly! Thanks :) @hach-que Thanks for your explanation, It 's now clearer to me how the toolchain variables work now.
The TOOLCHAIN_KERNELS environment variable required by the dcpu toolchain linker (dtld) is either never set; or unset at shutdown/log out, I can't remember if it was set the first time I installed it though. I have the latest version of the deployed version. Ubuntu Linux 12.04, Kernel Linux 3.2.0-35-generic-pae.