|
From: <rs...@ba...> - 2020-07-05 20:34:56
|
Dear Bernard and Anthony, So this looks great! I installed a Debian Jessi virtual machine and build-essential, and the build just went through, like on Ubuntu. Jessie uses gcc 4.9, which is quite old, but no problem. Bernard, I went through the assembly of the build system it’s trivial. So I’ll give you the steps, they might help you with the sudo problem on your virtual server: - first of all, Linux comes in different distributions. A distribution is a flavour with a package managements system. The key thing to understand is that binaries and libraries are made to work together in a distribution. So if you compile something you can expect it to work on the same version of the same distribution, but neither on other distribution nor even on different major-versions of the same distribution. These flavours also have slight differences in file structure and favoured apps, so everything is kind of similar but also slightly different on every distro. So if you want to look something up in the Web, add bistro-info in your query to get precise information. In your case it’s “Debian Jessie” (current Debian is “Debian Buster”, but Jessie is still reasonably recent). Your sudo problem actually has to do with a Debian idiosyncrasy I didn’t remember either. These steps might help to solve your problem (they did for me): ```` By default sudo is not installed on Debian, but you can install it. First enable su-mode: su - Install sudo by running: apt-get install sudo -y After that you would need to play around with users and permissions. Give sudo right to your own user. usermod -aG sudo yourusername Make sure your sudoers file have sudo group added. Run: visudo to modify sudoers file and add following line into it (if it is missing): # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL You need to relogin or reboot device completely for changes to take effect. ``` This is from here: https://unix.stackexchange.com/questions/354928/bash-sudo-command-not-found Second sudo apt install build-essential Seems really to be enough. Getting csound just requires Sudo apt install csound The nice thing is that Linux package managers will pull in the dependencies (e.g. tcl) automagically, and they will choose the right versions. Which is good, of course, but also means you cannot randomly mix stuff from different distributions or stuff built somewhere else. Well, and then it just unzipping Anthony’s source folder (install `unzip` if necessary: `sudo apt install unzip`), adding the Makefile to the “root” of the resulting “bolprocessor” (one level above `source`) and doing `make`. After 10 sec you should have your ./bp binary. Wonderful! I’ll attach the Debian Jessie version here as well. This one could actually work on your server ;-) |
