I can't get to install.
Questions and Answers :
Unix/Linux :
I can't get to install.
Message board moderation
| Author | Message |
|---|---|
|
cummingspatrick Send message Joined: 23 Dec 04 Posts: 15 Credit: 850,862 RAC: 0 
|
I'm trying to follow the instructions on how to install on the site, but I get this: $ _autosetup Bootstrapping configure script and makefiles: Provide an AUTOMAKE_VERSION environment variable, please Provide an AUTOCONF_VERSION environment variable, please Provide an AUTOMAKE_VERSION environment variable, please Provide an AUTOCONF_VERSION environment variable, please Done, now run ./configure ./configure -C to enable caching ./configure --enable-maintainer-mode to enable maintainer depedencies $ ./configure ksh: ./configure: not found What are the errors and why configure is not there. My OS is OpenBSD 3.8 and I use all the latest versions if that can help. ID: 255018 ·  |
 Jim-R.  Send message Joined: 7 Feb 06 Posts: 1494 Credit: 194,148 RAC: 0 
|
I'm sorry I'm not familiar with openbsd, I'm a linux (slackware) user, but I'll try to help. It looks like from your error messages that you need to tell it what version of automake you have. First you need to look in your documentation to find out what version you have then set the environment variable to that version. Usually when one part of a script like this fails the rest will fail also. So since the automake version variable was not set it did not create an actual configure script. I see you are using ksh, while I use bash so you may have to check on the particular syntax to use but if I were doing this in bash I would say: export AUTOMAKE_VERSION=3.1.24 (whatever your actual version is) I think in ksh the syntax is: SET AUTOMAKE_VERSION 3.1.24 (Again whatever your actual version is) Again if you are not familiar with setting environment variables in ksh you should check the documentation for ksh. btw, if you wanted to temporarily switch to bash for your shell, the first one I gave *will* work. Then type your autosetup command again. If you still have problems, let us know and we'll try until we get it right! Jim Some people plan their life out and look back at the wealth they've had. Others live life day by day and look back at the wealth of experiences and enjoyment they've had. ID: 255044 · |
|
cummingspatrick Send message Joined: 23 Dec 04 Posts: 15 Credit: 850,862 RAC: 0
|
bash-3.00$ _autosetup Bootstrapping configure script and makefiles: /usr/local/share/aclocal/pkg.m4:5: warning: underquoted definition of PKG_CHECK_MODULES run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending-aclocal Done, now run ./configure ./configure -C to enable caching ./configure --enable-maintainer-mode to enable maintainer depedencies ID: 255078 · |
|
Jim-R. Send message Joined: 7 Feb 06 Posts: 1494 Credit: 194,148 RAC: 0
|
bash-3.00$ _autosetup Ok, without checking the website mentioned and having a copy of the file mentioned I'm only guessing, but it sounds like there is a mistake in a preprocessor macro file. That's the "pkg.m4" file mentioned in your output line. You should be able to open the file in a text editor and look on line 5. You should see the "PKG_CHECK_MODULES" and the "underquoted definition" sounds like there's just a set of quote marks missing. You could probably check the web page or fire up your info program with the line just above the web address to get the right way to use the statement in the file mentioned. Check it out and if you're not sure about it post the first say 10 lines of the file (it says the error is on line 5) and we can take a look at it. Jim /Edit Just to mention, the actual *error* may be on a previous line. I have seen this several times in "c" code that where the error is reported is just where the compiler (or macro preprocessor in your case) runs into something it chokes on because of the error. Jim Some people plan their life out and look back at the wealth they've had. Others live life day by day and look back at the wealth of experiences and enjoyment they've had. ID: 255085 · |
|
cummingspatrick Send message Joined: 23 Dec 04 Posts: 15 Credit: 850,862 RAC: 0
|
Here is the file. BTW, thanks for your help so far! dnl PKG_CHECK_MODULES(GSTUFF, gtk+-2.0 >= 1.3 glib = 1.3.4, action-if, action-not) dnl defines GSTUFF_LIBS, GSTUFF_CFLAGS, see pkg-config man page dnl also defines GSTUFF_PKG_ERRORS on error AC_DEFUN(PKG_CHECK_MODULES, [ succeeded=no if test -z "$PKG_CONFIG"; then AC_PATH_PROG(PKG_CONFIG, pkg-config, no) fi if test "$PKG_CONFIG" = "no" ; then echo "*** The pkg-config script could not be found. Make sure it is" echo "*** in your path, or set the PKG_CONFIG environment variable" echo "*** to the full path to pkg-config." echo "*** Or see http://www.freedesktop.org/software/pkgconfig to get pkg-config." ------------------------------------------ EDIT: FULL VERSION HERE: http://66.131.120.154:81/pkg.m4 ID: 255091 · |
|
Jim-R. Send message Joined: 7 Feb 06 Posts: 1494 Credit: 194,148 RAC: 0
|
Here is the file. BTW, thanks for your help so far! Let me do a little digging. I may need to see the whole file, but let me see what I can find out first. (I'll be honest with you I'm not that familiar with the m4 language!) I'll be back with *something* in just a few Jim Some people plan their life out and look back at the wealth they've had. Others live life day by day and look back at the wealth of experiences and enjoyment they've had. ID: 255092 · |
|
Jim-R. Send message Joined: 7 Feb 06 Posts: 1494 Credit: 194,148 RAC: 0
|
Here is the file. BTW, thanks for your help so far! Ok, found something that might help. Before you do anything, make a backup of this file. (copy it to for instance "pkg.m4.bak") Now edit the original file and put square brackets "[]" around the "PKG_CHECK_MODULES" on what looks like line 4 so that it reads AC_DEFUN([PKG_CHECK_MODULES], [ What I found is there is a new version that is stricter on "underquoted definitions" and that was one of the examples they gave. I'll keep reading while you try that. Jim Some people plan their life out and look back at the wealth they've had. Others live life day by day and look back at the wealth of experiences and enjoyment they've had. ID: 255101 · |
|
cummingspatrick Send message Joined: 23 Dec 04 Posts: 15 Credit: 850,862 RAC: 0
|
That seems to work. Also configure is now running, no errors so far. THANKS A LOT!!! ID: 255109 · |
|
Jim-R. Send message Joined: 7 Feb 06 Posts: 1494 Credit: 194,148 RAC: 0
|
That seems to work. Also configure is now running, no errors so far. Good to hear it. Any time. Jim Jim Some people plan their life out and look back at the wealth they've had. Others live life day by day and look back at the wealth of experiences and enjoyment they've had. ID: 255111 · |
Dotsch  Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0 
|
My OS is OpenBSD 3.8 and I use all the latest versions if that can help. I recommend you to test your seti app against the reference WU. I had a lot of problems with the correctness of the computed results under OpenBSD. Btw. on the third party site (boinc.berkeley.edu/download_other.php) are binaries for OpenBSD i386 available for download. ID: 255150 · |
|
cummingspatrick Send message Joined: 23 Dec 04 Posts: 15 Credit: 850,862 RAC: 0
|
New problems already. Boinc is installed succesfully. However, it seems that the boinc server for seti does not hold a binary for the seti client on openbsd. It seems like I will have to build my own. I downloaded the source from the seti site. When I try to run _autosetup I get this: ------------------------------------------------------ $ _autosetup Bootstrapping configure script and makefiles: Checking version of 'make' >= 3.79... make: unknown option -- - usage: make [-BeiknPqrSst] [-D variable] [-d flags] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable] [NAME=value] [target ...] failed. (0) Checking version of 'gmake' >= 3.79... succeeded. (3.80) Checking version of 'm4' >= 1.4... m4: unknown option -- - usage: m4 [-gs] [-d flags] [-t macro] [-o file] [-Dname[=val]] [-Uname] [-I dirname...] failed. (0) Couldn't find a new-enough version of 'm4', please install one! ------------------------------------------------------- At first I thought that my version of m4 was not the good version or was incompatible. I checked the version and it was the latest. I installed the m4 package and installed it again from the source. M4 installed succesfully, but I get the same message! ID: 255261 · |
|
Jim-R. Send message Joined: 7 Feb 06 Posts: 1494 Credit: 194,148 RAC: 0
|
New problems already. Boinc is installed succesfully. However, it seems that the boinc server for seti does not hold a binary for the seti client on openbsd. It seems like I will have to build my own. I downloaded the source from the seti site. When I try to run _autosetup I get this: Ok, I see this: make: unknown option -- - This looks like something is trying to pass an option to make, from the "-" in the error message however whatever option it is trying to pass does not get added to the command line. Right now I don't have a clue to what would be needed there. I'd have to look at the package to see. In the meantime, there *is* a freebsd port http://www.freebsd.org/cgi/ports.cgi?query=boinc-setiathome&stype=all I am not sure but I think there is a binary and source release. I didn't actually dl it to see what it is, but it has "source" and "download" so I'm assuming the "download" package is the binary. BTW, the info doesn't mention you have to build it. You might try this first (matter of fact it is newer than the standard version we are running (ours=4.02 freebsd=4.07). If you can't get this up and running, let me know here and we'll try to get your source compiled and running. Jim Some people plan their life out and look back at the wealth they've had. Others live life day by day and look back at the wealth of experiences and enjoyment they've had. ID: 255271 · |
|
cummingspatrick Send message Joined: 23 Dec 04 Posts: 15 Credit: 850,862 RAC: 0
|
Dear Jim, from your answer I am not sure exactly what I should do. Are you suggesting that I find a way to install from a binary? I'm not to sure about this, because I already have to boinc client running, I just lack the seti client, but all the binaries I've seen include both. So I guess I'll have to uninstall boinc, right? I'm not too sure about running the binairies cause there is nothing that proves me that they would run better. Wouldn't there be a way to debug why the _autosetup gives error? I feel so sorry that I don't have more knowledge in softwares! (/is a hardware freak) Also I saw that you suggested freebsd binairies? Do you mean that they would run well in openbsd? ID: 255279 · |
|
Dotsch Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0
|
I'm not to sure about this, because I already have to boinc client running, I just lack the seti client, but all the binaries I've seen include both. So I guess I'll have to uninstall boinc, right? I'm not too sure about running the binairies cause there is nothing that proves me that they would run better. The OpenBSD binaries on the third party site are well tested, and know to running stable on several systems. ID: 255287 · |
|
Jim-R. Send message Joined: 7 Feb 06 Posts: 1494 Credit: 194,148 RAC: 0
|
Dear Jim, Yse, I'm suggesting trying the binaries. They are well tested as Dotsch pointed out. I know because I'm a volunteer tester also, even though my tagline doesn't say it. (If they weren't running properly we'd have heard about them long ago! Funny when something works you don't hear a peep but when something breaks all h*** breaks loose!) The thing to do would be to download the binary and put it in the seti project directory then follow the directions that are included with the binary or are present on the web pages. This usually just means adding an xml file that tells boinc which application to use, instead of using the default application. This approach would be less trouble and get you going faster than getting the source compiled. Before you start seti running, go into your preferences and set your "connect every X days" to 0.1 days. That will let you only download one wu. As soon as it starts crunching, set your project tab to "no new work". Crunch that wu and return it. Then you can check for any errors. (This step is needed any time you install a new seti application.) If there are no errors reported, then you can get new work and crunch another couple of wu's, watching your messages tab regularly for any error messages. If you haven't seen any errors in four or five wu's you can turn it loose and let it crunch for a couple days checking your returned wu's again for any errors. If by this time you haven't seen any errors you're good to go. If it doesn't work out for you, just post here again and I'll keep watching. then we can try to get your source to compile. Jim Some people plan their life out and look back at the wealth they've had. Others live life day by day and look back at the wealth of experiences and enjoyment they've had. ID: 255324 · |
|
cummingspatrick Send message Joined: 23 Dec 04 Posts: 15 Credit: 850,862 RAC: 0
|
Hi all, I've restarted to try to work on this. I dumped the source installs, and I am trying to use the binairies from http://www.lb.shuttle.de/apastron/boincDown.shtml . However, it seems like they where made on openbsd 3.6. I use the 3.8 version. The user that made them tells in a txt file that I should use some special librairies that he provides. He provides two files called "libcurl.so.3.0" and "libstdc++.so.33.0". When I first tried to run the boinc_client, it gave me this: boinc_client: can't load library 'libssl.so.9.0' then, I tried to add this (as specified and the informative txt file): LD_LIBRARY_PATH=/usr/boinc/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH to the .profile file in the home directory of the seti user (/usr/seti), and it gave me this instead: boinc_client: can't load library 'libcrypto.so.11.0' because I use openbsd 3.8 my file is called libcrypto.so.12.0 how can I work around all of this? ID: 263149 · |
|
Jim-R. Send message Joined: 7 Feb 06 Posts: 1494 Credit: 194,148 RAC: 0
|
Hi all, I've restarted to try to work on this. I dumped the source installs, and I am trying to use the binairies from http://www.lb.shuttle.de/apastron/boincDown.shtml . However, it seems like they where made on openbsd 3.6. I use the 3.8 version. The user that made them tells in a txt file that I should use some special librairies that he provides. He provides two files called "libcurl.so.3.0" and "libstdc++.so.33.0". When I first tried to run the boinc_client, it gave me this: The libraries that the program are compiled with have to be the same ones that are on the machine it runs on. This is a very common problem when running programs from different releases. The fix is simple, just install the older version libraries, but install them in a different directory to the one where your files are located. That way you can add a line in the library path statement as you did for the other libs to point to this directory. Then if the program you are running needs the ver. 12 of the libs it gets it from one directory but if it needs the ver. 11 libs it reads the other. Now if and only *if* there are no links named "libcrypto.so" or anything that are pointing to the libcrypto.so.12.0, (if this is a standalone file) then it would be possible to just copy this file to your lib directory and forget it. However many libraries use a shortened version of the name to make it easier to do minor version upgrades without recompiling the programs every time. BTW, on my system there is a libcrypto.so.0 and libcrypto.so that are symlinks to the actual library file. Since the program is calling for the older version you may be able to put it in the directory and it will run fine, but if it is calling for one of the link names you will have to put at least the links in a separate directory or they will mess up your already installed links, making them point to an older version and possibly breaking already running programs. (If you have /usr/lib and /usr/local/lib in your library path already then just put them in a directory in your lib path that is not the one your original ones are and you won't have to modify your library path. If yours are in /usr/lib, put the others in /usr/local/lib. Jim Some people plan their life out and look back at the wealth they've had. Others live life day by day and look back at the wealth of experiences and enjoyment they've had. ID: 263165 · |
|
cummingspatrick Send message Joined: 23 Dec 04 Posts: 15 Credit: 850,862 RAC: 0
|
How can I get the old librairies? What would I need to add to my .profile for the seti user? ID: 263175 · |
|
Jim-R. Send message Joined: 7 Feb 06 Posts: 1494 Credit: 194,148 RAC: 0
|
How can I get the old librairies? What would I need to add to my .profile for the seti user? This is a good question since I've done a search of the internet and cannot find that library as a separate package. I guess the best way of getting it would be to get the 3.6 version of openbsd and extract just the library files. Since you already have your boinc/lib directory in the library path, just put them there and you won't have to change anything in your profile. Jim Some people plan their life out and look back at the wealth they've had. Others live life day by day and look back at the wealth of experiences and enjoyment they've had. ID: 263192 · |
|
cummingspatrick Send message Joined: 23 Dec 04 Posts: 15 Credit: 850,862 RAC: 0
|
Alright, that seemed to help quite a bit. Now I get this: $ boinc_client 2006-03-17 00:10:21 [---] Starting BOINC client version 5.2.15 for i386-unknown-openbsd3.8 2006-03-17 00:10:21 [---] libcurl/7.15.1 OpenSSL/0.9.7g zlib/1.2.3 2006-03-17 00:10:21 [---] Data directory: /usr/boinc 2006-03-17 00:10:21 [SETI@home] Found app_info.xml; using anonymous platform 2006-03-17 00:10:21 [---] Processor: 1 i386 Intel Pentium/MMX ("GenuineIntel" 586-class) 2006-03-17 00:10:21 [---] Memory: 63.54 MB physical, 384.00 MB virtual 2006-03-17 00:10:21 [---] Disk: 15.75 GB total, 14.59 GB free 2006-03-17 00:10:21 [SETI@home] Computer ID: not assigned yet; location: ; project prefs: default 2006-03-17 00:10:21 [---] No general preferences found - using BOINC defaults 2006-03-17 00:10:21 [---] Remote control not allowed; using loopback address And then it just sits there. Forever. ID: 263212 · |
©2025 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.