README: fix dependencies

[AndreiCherniaev]

Tested in Ubuntu 24. Fix err:

config.status: error: Something went wrong bootstrapping makefile fragments
    for automatic dependency tracking.  If GNU make was not used, consider
    re-running the configure script with MAKE="gmake" (or whatever is
    necessary).  You can also try re-running configure with the
    '--disable-dependency-tracking' option to at least be able to build
    the package (albeit without support for automatic dependency tracking).
See 'config.log' for more details

[AsciiWolf]

Looks good!

[AsciiWolf]

Suggested change

	will configure the build to install the files into /home/user/predict folder.
	will configure the build to install the files into $HOME/predict folder.

[AndreiCherniaev]

Main question is. Install the files into /home/user/gpredict folder or predict folder?

[AndreiCherniaev]

@AsciiWolf any news?

[AsciiWolf]

Sorry, but I am not sure what the correct folder is. This is a question for @csete.

[AndreiCherniaev]

@AsciiWolf can I ask you to approve my commit? Well, we have question /home/user/gpredict vs /home/user/predict but this question is out of my commit... I don't change path by my commit...

[AsciiWolf]

Sorry, but I am not able to. This is something @csete (or someone else with correct permissions) have to do.

[csete]

I just tried building on the latest Kubuntu 25.04 using the existing instructions and dependency list and it builds without errors. So, I don't understand where the error that you see comes from.

I have fixed the directory name, though.

[AndreiCherniaev]

Kubuntu 25.04

Do you start instruction on clean distro?

[AndreiCherniaev]

@csete please apply my commit

[AndreiCherniaev]

3. @csete do you have GitHub successor? Please have, your project is important for community

[csete]

@csete please apply my commit

The purpose with the build instructions in the readme was to provide as simple instructions as possible for people who are not familiar with the build system. Making that proposed change increases the risk of people making a typing error and the build time for a single threaded build is really not that long.

[AndreiCherniaev]

@csete please apply my commit

The purpose with the build instructions in the readme was to provide as simple instructions as possible for people who are not familiar with the build system. Making that proposed change increases the risk of people making a typing error and the build time for a single threaded build is really not that long.

simple instructions should be make -j$(( $(nproc) + 1)) not make, don't ask people to wait more just for fun. make can be better in systems with many CPUs but not enough RAM but this is very rare case and people who works with such systems well know what they did. Casual user should use make -j$(( $(nproc) + 1)) to enjoy last version of gpredict as soon as possible. You also can check another software build instructions and in most cases you will find make -j$(( $(nproc) + 1)) which is main stream... Let's use make -j$(( $(nproc) + 1))

[AndreiCherniaev]

Kubuntu 25.04 using the existing instructions and dependency list

clean Ubuntu 25.04 fails, I have checked now. Please check one more time with clear Ubuntu 25.04. I don't think Kubuntu 25.04 is differents from Ubuntu 25.04 in default dependency, I think you use instance which already contains some dependency. Please apply my commit

[csete]

I have now tested on a clean install of Xubuntu 25.04 and 25.10 daily snapshot and I still cannot see any problems with the existing dependency list. I have also checked the build dependencies in the Debian and Ubuntu package configurations and these too use automake and autoconf.

[AndreiCherniaev]

I have now tested on a clean install of Xubuntu 25.04 and 25.10 daily snapshot and I still cannot see any problems with the existing dependency list. I have also checked the build dependencies in the Debian and Ubuntu package configurations and these too use automake and autoconf.

But why I got it in Ubunti 25.04?

q@ubuntu-desktop:~/gpredict$ make
Command 'make' not found, but can be installed with: