Skip to content
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

Make install failing #5690

Closed
MoiseRousseau opened this issue Jul 17, 2024 · 12 comments · Fixed by #5828
Closed

Make install failing #5690

MoiseRousseau opened this issue Jul 17, 2024 · 12 comments · Fixed by #5828

Comments

@MoiseRousseau
Copy link

MoiseRousseau commented Jul 17, 2024

Describe the bug
make install target fail because some examples does not have that target

Steps To Reproduce

./_autosetup
./configure --disable-client --disable-manager --enable-apps --prefix=$HOME/install
make
make install

Expected behavior
No error

System Information

  • OS: Ubuntu 24.04 in a LXD container
  • BOINC Version: Release 8.0.2 from Github

Additional context
Fixed adding a dummy install target in:

  • boinc-client_release-8.0-8.0.2/samples/condor/Makefile
  • boinc-client_release-8.0-8.0.2/samples/multi_thread/Makefile

For example:

install:
	echo "Dummy install"
@bjauny
Copy link
Contributor

bjauny commented Sep 30, 2024

Hey there, I'll be glad to tackle this.

EDIT: just to be clear: you want a real install happening or is a placeholder enough?

@bjauny
Copy link
Contributor

bjauny commented Sep 30, 2024

I have the following message while building/installing:

fatal: No names found, cannot describe anything.

It comes from the git describe call in generate_svn_version.sh. Is it normal? Should I ignore it?

@AenBleidd
Copy link
Member

@bjauny, you should follow this manual to build BOINC: https://github.com/BOINC/boinc/wiki/Building-boinc-on-unix

@bjauny
Copy link
Contributor

bjauny commented Sep 30, 2024

OK, it seems the error comes from the fact that my fork doesn't have any tag matching server_release/*. I will have a mock install ready by tomorrow for Hacktoberfest, but is it enough or a real install is needed for this issue?

@AenBleidd
Copy link
Member

@bjauny, build it with

./configure --disable-client --disable-manager --enable-apps --disable-server

There should not be this error then.

@bjauny
Copy link
Contributor

bjauny commented Sep 30, 2024

Sorry to be a pain, but it's still here. Tail of the log follows.

To be clear on the environment/setup:

  • WSL2 on W11 (Ubuntu)
  • installed the listed pre-requisites in the Wiki
  • forked the repo and cloned locally
  • ./_autosetup
  • ./configure --disable-client --disable-manager --enable-apps --disable-server --prefix=$HOME/install
  • make

Apart from the git describe failing, everything is OK.

make[2]: Entering directory '/home/bjauny/git/boinc/doc'
make[3]: Entering directory '/home/bjauny/git/boinc/doc'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/home/bjauny/git/boinc/doc'
make[2]: Leaving directory '/home/bjauny/git/boinc/doc'
make[2]: Entering directory '/home/bjauny/git/boinc'
cd . && sh generate_svn_version.sh
fatal: No names found, cannot describe anything.
make[2]: Leaving directory '/home/bjauny/git/boinc'
make[1]: Leaving directory '/home/bjauny/git/boinc'

@AenBleidd
Copy link
Member

ok, just ignore it then. this is not the actual error of this ticker.

bjauny added a commit to bjauny/boinc that referenced this issue Oct 1, 2024
@AenBleidd AenBleidd linked a pull request Oct 1, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from Backlog to Done in Client/Manager Oct 1, 2024
@MoiseRousseau
Copy link
Author

MoiseRousseau commented Oct 3, 2024

Thanks for tackling this.

My ultimate objective of this was to create a deb package for BOINC server. I also have to add the following instructions for an app to be run after installation:

PYVER=$(python -c "import sys; print(f'{sys.version_info[0]}.{sys.version_info[1]}')")

mv ./packaging/lib/python$PYVER/site-packages/ ./packaging/lib/python$PYVER/dist-packages
sed -i 's/\/root\/boinc-client_release-8.0-8.0.2/\/usr\/share\/boinc-server-maker/g' ./packaging/lib/python3.10/dist-packages/boinc_path_config.py
mv ./packaging/libexec/boinc-server-maker/* ./packaging/usr/share/boinc-server-maker/
mv ./packaging/share/boinc-server-maker/* ./packaging/usr/share/boinc-server-maker/
cp ./boinc-client_release-8.0-${VERSION}/db/*.sql ./packaging/usr/share/boinc-server-maker/db/
cp -r ./boinc-client_release-8.0-${VERSION}/html/project.sample ./packaging/usr/share/boinc-server-maker/html/
cp ./boinc-client_release-8.0-${VERSION}/sched/pshelper ./packaging/usr/share/boinc-server-maker/sched/

Note my packaging directory is the installation target directory. This could be the hard drive root /.

Maybe open a new issue ?

@AenBleidd
Copy link
Member

@MoiseRousseau, BOINC Server is a complex product, and majority of the Projects who install it, do some customization of it.
Making a package (DEB, RPM or any other) in this case is useless.
We currently support only BOINC client and BOINC Manager to be packaged (see: https://boinc.berkeley.edu/linux_install.php).

@MoiseRousseau
Copy link
Author

@AenBleidd I did not meant to create an official Deb package. But just to report the steps to have a working BOINC server installation. For example, the current installation installs components in non standard path, python library in a folder that is not on PYTHONPATH, or lacks the sql script to interact with the database. So I was unable to create a simple test project.

@AenBleidd
Copy link
Member

@MoiseRousseau
Copy link
Author

@AenBleidd I already succeeded make it working with the install target and the steps and I sent you. Just reporting what I have done for other people to reproduce if they need

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants