Author

Topic: Need help installing on Redhat (Read 10473 times)

sr. member
Activity: 308
Merit: 252
August 13, 2010, 02:01:32 PM
#12
Big business (Red Hat, IBM, maybe Novell too?) has spent Big Money hiring Real Lawyers, who determined that openssl's EC and EC-DSA support should not be distributed due to patent worries.

Red Hat and IBM have done extensive work and spent millions of dollars clearing a lot of open source code of patent worries, using a combination of lawyer review and patent pooling.  If, after all that, they advise against using something -- I am going to listen.

Then I suggest, going to them and asking for license. Just like SCO will give you license for Unix still for some money.

They don't sell licenses for openssl, they just avoid it, based on multiple independent legal advisors.

We should take the hint...

So how many independent legal advisors say that the other independent legal advisors are wrong? There are always at least 2 sides to the issue and you don't need to be a legal advisor to decide what works best.

When they actually start winning some courts cases (last I checked years ago, they lost), then I'll put more thought into the issue.
legendary
Activity: 1596
Merit: 1022
August 13, 2010, 01:11:19 PM
#11
Big business (Red Hat, IBM, maybe Novell too?) has spent Big Money hiring Real Lawyers, who determined that openssl's EC and EC-DSA support should not be distributed due to patent worries.

Red Hat and IBM have done extensive work and spent millions of dollars clearing a lot of open source code of patent worries, using a combination of lawyer review and patent pooling.  If, after all that, they advise against using something -- I am going to listen.

Then I suggest, going to them and asking for license. Just like SCO will give you license for Unix still for some money.

They don't sell licenses for openssl, they just avoid it, based on multiple independent legal advisors.

We should take the hint...
sr. member
Activity: 308
Merit: 252
August 13, 2010, 08:46:36 AM
#10
Big business (Red Hat, IBM, maybe Novell too?) has spent Big Money hiring Real Lawyers, who determined that openssl's EC and EC-DSA support should not be distributed due to patent worries.

Red Hat and IBM have done extensive work and spent millions of dollars clearing a lot of open source code of patent worries, using a combination of lawyer review and patent pooling.  If, after all that, they advise against using something -- I am going to listen.

Then I suggest, going to them and asking for license. Just like SCO will give you license for Unix still for some money.
sr. member
Activity: 252
Merit: 250
August 10, 2010, 01:33:55 PM
#9
distributing source code or build scripts puts you in a far better position than distributing ready-to-use binary software.
Yes, we need both binaries and sources packaged for different platforms. There are standard build scripts for many platforms:

CentOS has SRPM
Arch has AUR
FreeBSD has ports
legendary
Activity: 1596
Merit: 1022
August 09, 2010, 12:55:33 PM
#8

A build script for a particular distro would probably be safer, patent-wise.  CentOS/RHEL/Fedora do not include the patent-encumbered EC-DSA codes from OpenSSL, and anyone using bitcoin requires that.  Therefore, anyone providing builds is providing patent-encumbered software.

IANAL, but apparently, distributing source code or build scripts puts you in a far better position than distributing ready-to-use binary software.
Remember that Certicom's patent claim pertaining to ECDSA is still just a claim. I haven't seen anything that established them ownership of it since they filed back in 1999 and everything freaked out, but if anyone has an links to some hard court cases, that would be great.

Otherwise, I wouldn't worry about it because since then, a lot of the world governments and big business already use this. I don't know how well they would stand in a lawsuit against the entire planet?

Big business (Red Hat, IBM, maybe Novell too?) has spent Big Money hiring Real Lawyers, who determined that openssl's EC and EC-DSA support should not be distributed due to patent worries.

Red Hat and IBM have done extensive work and spent millions of dollars clearing a lot of open source code of patent worries, using a combination of lawyer review and patent pooling.  If, after all that, they advise against using something -- I am going to listen.
sr. member
Activity: 308
Merit: 252
August 08, 2010, 04:36:55 PM
#7

A build script for a particular distro would probably be safer, patent-wise.  CentOS/RHEL/Fedora do not include the patent-encumbered EC-DSA codes from OpenSSL, and anyone using bitcoin requires that.  Therefore, anyone providing builds is providing patent-encumbered software.

IANAL, but apparently, distributing source code or build scripts puts you in a far better position than distributing ready-to-use binary software.
Remember that Certicom's patent claim pertaining to ECDSA is still just a claim. I haven't seen anything that established them ownership of it since they filed back in 1999 and everything freaked out, but if anyone has an links to some hard court cases, that would be great.

Otherwise, I wouldn't worry about it because since then, a lot of the world governments and big business already use this. I don't know how well they would stand in a lawsuit against the entire planet?
legendary
Activity: 1596
Merit: 1022
August 08, 2010, 03:43:17 PM
#6

A build script for a particular distro would probably be safer, patent-wise.  CentOS/RHEL/Fedora do not include the patent-encumbered EC-DSA codes from OpenSSL, and anyone using bitcoin requires that.  Therefore, anyone providing builds is providing patent-encumbered software.

IANAL, but apparently, distributing source code or build scripts puts you in a far better position than distributing ready-to-use binary software.
sr. member
Activity: 252
Merit: 250
August 08, 2010, 02:16:42 PM
#5
Well, what we need are maintained binary packages for several distros. I vote for CentOS and Arch as a first step Smiley I agree to maintain them and provide space, but I'm too lazy to try to create an RPM for CentOS myself  Grin
sr. member
Activity: 308
Merit: 252
August 04, 2010, 11:26:01 PM
#4
All I have is a CentOS bitcoind that was compiled with glibc 2.5, so it won't work on the system you listed.

All I can say is that it took me all day to figure out the compiling issues for CentOS 5.5.

Perhaps I should start offering compiling solutions for various Linux distros with BTC as the cost?  Grin
newbie
Activity: 32
Merit: 0
August 04, 2010, 09:17:50 PM
#3
What version of Glibc are you using?

Goto the console and type "ldd --version" it should tell you what your OS is using, post it back here. I might have a compile that works with yours.

I actually have several linux machines setup at home and need to be able to compile on each of them.  For the one machine mentioned in my OP we have:

[[email protected] 64]# ldd --version
ldd (GNU libc) 2.3.4
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.
sr. member
Activity: 308
Merit: 252
August 04, 2010, 09:03:27 PM
#2
What version of Glibc are you using?

Goto the console and type "ldd --version" it should tell you what your OS is using, post it back here. I might have a compile that works with yours.
newbie
Activity: 32
Merit: 0
August 04, 2010, 09:00:28 PM
#1
Can someone please post in detail the steps required to install on redhat?  I've unpacked the tar file but there are dependency issues when running the executable.

/proc/version:

Linux version 2.6.9-42.0.10.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)) #1 SMP Fri Feb 16 17:13:42 EST 2007

Here's what I get:

[[email protected] ~]# cd bitcoin-0.3.8/bin/64
[[email protected] 64]# ./bitcoin
./bitcoin: error while loading shared libraries: libpangocairo-1.0.so.0: cannot open shared object file: No such file or directory
[[email protected] 64]# ./bitcoind
./bitcoind: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by ./bitcoind)
./bitcoind: /lib64/tls/libc.so.6: version `GLIBC_2.4' not found (required by ./bitcoind)
./bitcoind: /lib64/tls/libc.so.6: version `GLIBC_2.7' not found (required by ./bitcoind)

Thanks for helping me out.
Jump to: