- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- BOINC, SETI@home v. gcc 3.4.3 on Tru64 V5.1B
Operating System - Tru64 Unix
1748089
Members
5058
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-26-2005 12:07 PM
тАО12-26-2005 12:07 PM
BOINC, SETI@home v. gcc 3.4.3 on Tru64 V5.1B
Starting with the latest "stable" source kit
(boinc_stable-cvs-2005-12-12.zip), and with
a bit of fiddling with client/hostinfo_unix.C
("#error Need to specify a sysconf() define to
obtain memory size"), I managed to build the
basic BOINC client on Tru64 V5.1B using gcc
3.4.3.
Starting with the latest nightly SETI-BOINC
client kit
(seti_boinc-client-cvs-2005-12-26.zip),
the build failed with a lot of spewage
involving what looked like complaints about
bad declarations.
If anyone has built a SETI-BOINC client under
similar conditions, what was the source used?
(And where can I get it?)
(boinc_stable-cvs-2005-12-12.zip), and with
a bit of fiddling with client/hostinfo_unix.C
("#error Need to specify a sysconf() define to
obtain memory size"), I managed to build the
basic BOINC client on Tru64 V5.1B using gcc
3.4.3.
Starting with the latest nightly SETI-BOINC
client kit
(seti_boinc-client-cvs-2005-12-26.zip),
the build failed with a lot of spewage
involving what looked like complaints about
bad declarations.
If anyone has built a SETI-BOINC client under
similar conditions, what was the source used?
(And where can I get it?)
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-27-2005 07:53 AM
тАО12-27-2005 07:53 AM
Re: BOINC, SETI@home v. gcc 3.4.3 on Tru64 V5.1B
Steven,
Go to this site:
http://boinc.berkeley.edu/download_other.php
Vic
Go to this site:
http://boinc.berkeley.edu/download_other.php
Vic
There are 10 kinds of people, one that understands binary and one that doesn't.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-27-2005 04:32 PM
тАО12-27-2005 04:32 PM
Re: BOINC, SETI@home v. gcc 3.4.3 on Tru64 V5.1B
> http://boinc.berkeley.edu/download_other.php
Yes, but it's old stuff, and I was actually
looking toward doing this on VMS, so getting
a build to work is more important than
getting a working executable.
Also, my modified client/hostinfo_unix.C
gets the physical memory size right, and
includes the CPU type in the item.
client_state.xml(pre-fab) excerpts:
Hewlett-Packard
alpha
1073741824.000000
1073741824.000000
client_state.xml(mine) excerpts:
HP (DEC)
Alpha EV4.5 (21064)
402653184.000000
1073741824.000000
This is on an AlpSta 200 4/233 with 384MB of
memory. (This matches the one
for Linux.)
Also, mine starts like this:
urt# client/boinc_client
2005-12-27 23:01:41 [---] Starting BOINC client version 5.2.14 for alpha-dec-osf5.1
instead of:
urt# client/boinc_client.sh
inst emulated pid=110987 va=0x1400026fd pc=0x12006a6d4 inst=0x38700005
2005-12-27 23:09:03 [---] Starting BOINC client version 4.32 for alpha-dec-osf5.1
(The script sets LD_LIBRARY_PATH as required
to use the non-default shared libraries.)
I like mine better. The reported CPU speed
numbers are also higher, perhaps because of
the newer GCC, but I can't prove that.
The build problem for the SETI client
appears to have been caused by multiple
defects in the generated "config.h". I
edited the thing, and it seemed to work
better. (I haven't looked at the "configure"
mess to see what actually went wrong there.)
So, I guess I'm happy, more or less.
Yes, but it's old stuff, and I was actually
looking toward doing this on VMS, so getting
a build to work is more important than
getting a working executable.
Also, my modified client/hostinfo_unix.C
gets the physical memory size right, and
includes the CPU type in the
client_state.xml(pre-fab) excerpts:
client_state.xml(mine) excerpts:
This is on an AlpSta 200 4/233 with 384MB of
memory. (This
for Linux.)
Also, mine starts like this:
urt# client/boinc_client
2005-12-27 23:01:41 [---] Starting BOINC client version 5.2.14 for alpha-dec-osf5.1
instead of:
urt# client/boinc_client.sh
inst emulated pid=110987
2005-12-27 23:09:03 [---] Starting BOINC client version 4.32 for alpha-dec-osf5.1
(The script sets LD_LIBRARY_PATH as required
to use the non-default shared libraries.)
I like mine better. The reported CPU speed
numbers are also higher, perhaps because of
the newer GCC, but I can't prove that.
The build problem for the SETI client
appears to have been caused by multiple
defects in the generated "config.h". I
edited the thing, and it seemed to work
better. (I haven't looked at the "configure"
mess to see what actually went wrong there.)
So, I guess I'm happy, more or less.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP