seti@home build under NetBSD

Questions and Answers : Unix/Linux : seti@home build under NetBSD
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Eddie Cottongim Project Donor
Volunteer tester

Send message
Joined: 15 Sep 01
Posts: 26
Credit: 6,146,461
RAC: 2,006
United States
Message 1977194 - Posted: 26 Jan 2019, 20:22:54 UTC

First, I hope this is an appropriate place for these questions.

I haven't seen much discussion or recent documentation on building seti@home, so I thought I'd post my trials and tribulations here.. they may help someone.

I'm trying to build with NetBSD's pkgsrc system. The effect of this is that boinc and s@h are building out of the following places:

/usr/pkgsrc/wip/boinc-git/work/boinc
/usr/pkgsrc/wip/seti-boinc/work/seti-boinc

I know that for building it is recommended to have BOINC and seti built under the same directory.. hard to do with the package system.

First I built BOINC (7.14.2 ). Attempting the seti@home build (SVN 3997), I get through configuration and the first problem is here:

===> Skipping vulnerability checks.
WARNING: No /var/db/pkg/pkg-vulnerabilities file found.
WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'.
===> Building for seti-boinc-3997nb20190121
/usr/bin/make all-recursive
Making all in client
c++ -DHAVE_CONFIG_H -I. -I.. -O2 -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -I/usr/include -I/usr/include/openssl -fPIC -DPIC -DHAVE_CONFIG_H -I.. -O2 -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -O2 -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -I/usr/include -I/usr/include/openssl -DHAVE_CONFIG_H -DTEXT_UI -DNDEBUG -DCLIENT -I../db -I../client -I../client/win_build -I/usr/pkgsrc/wip/boinc-git/work/boinc -I/usr/pkgsrc/wip/boinc-git/work/boinc/api -I/usr/pkgsrc/wip/boinc-git/work/boinc/lib -I/usr/pkgsrc/wip/boinc-git/work/boinc/sched -I/usr/pkgsrc/wip/boinc-git/work/boinc/db -I/usr/pkgsrc/wip/boinc-git/work/boinc/clientgui/mac -pthread -O2 -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -I/usr/include -I/usr/include/openssl -MT seti_boinc-main.o -MD -MP -MF .deps/seti_boinc-main.Tpo -c -o seti_boinc-main.o `test -f 'main.cpp' || echo './'`main.cpp
In file included from main.cpp:40:0:
../sah_config.h:784:23: fatal error: std_fixes.h: No such file or directory
compilation terminated.

From earlier posts, I see that std_fixes.h is a BOINC file, and often this problem is that the seti@home autoconfig didn't find BOINC. But looking at the command line we have: "-I/usr/pkgsrc/wip/boinc-git/work/boinc/lib" as well as several other directories in boinc-git, so I think seti@home found my BOINC.

poweredge# ls -la /usr/pkgsrc/wip/boinc-git/work/boinc/lib/std_fixes.h
-rw-r--r-- 1 root wheel 3105 Dec 8 11:30 /usr/pkgsrc/wip/boinc-git/work/boinc/lib/std_fixes.h

So, c++ (5.5.0) is being pointed at the directory with std_fixes.h but not finding it. Any ideas?
ID: 1977194 · Report as offensive

Questions and Answers : Unix/Linux : seti@home build under NetBSD


 
©2020 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.