Wendy Smoak wrote:
> I've compiled Subversion 1.3.0 on a single-cpu HP-UX box with the
> usual ./configure, make, make install. That box has the C compiler
> from HP on it, and I don't see gcc anywhere. There were some
> warnings, but no errors and it's been working fine since January.
>
> Now I'd like to get Subversion installed on a different HP-UX box. I
> will not be able to compile it on this box because we're only licensed
> for a single CPU the HP C compiler.
I see that you are making good progress in the other discussion
thread. But I wanted to comment here on this point.
The svn program that you compiled successfully on one HP-UX machine
and have been using could simply be copied to the other HP-UX machine.
You shouldn't need to recompile the binary for every machine. Your
license for the compiler applies to the compiler but not to the
resulting executables. The resulting executables are yours and you
are allowed to copy them to the other machine.
There are some assumptions in saying this though. The machines need
to be newer or the same in operating sytem and must be the same
architecture. That is, if you compiled on HP-UX 11.11 then it will
run on other HP-UX 11.11 machines or on newer HP-UX 11.23 machines.
But if you compiled on HP-UX 11.23 then it will not run on HP-UX 11.11
because that 11.11 will lack the newer libraries present on 11.23.
And the architecture is wither hppa or ia64 in this context. You said
HP-UX 11.23 ia64 in the subject and if both machines are that then
things should work fine.
In most cases the executables that you generated on one machine could
simply be copied to the other machine.
svnserve
svnlook
svn
svnadmin
svnversion
svndumpfilter
Hope this helps,
Bob
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 27 19:20:14 2006