SSH on SCO 5.0.5
Domingos Saraiva de Oliveira
I have SCO 5.0.5 Enterprise. I 'd like to install a secure telnet ( ssh
) but I don't have the C compiler.
How I can to install?
Thanks.
Domingos Saraiva
Sent via Deja.com http://www.deja.com/
Before you buy.
Geoff Bleau
Jean-Pierre Radley wrote:
> Domingos Saraiva de Oliveira propounded (on Mon, May 01, 2000 at 02:35:26PM -0300):
> | Hi.
> |
> | I have SCO 5.0.5 Enterprise. I 'd like to install a secure telnet ( ssh
> | ) but I don't have the C compiler.
> |
> | How I can to install?
>
> Get gcc from Skunkware and compile ssh.
>
> --
> JP
Probably a waste of time.
The gcc 2.9.5pl1 release and the needed binutils on the SCO site
are incompatible ( binutils still has endless references to -belf insted
of -melf )
I wasted a few days trying to get this pair installed with no joy.
--
" Bigamy is having one wife too many.
Monogamy is the same "
Geoff Bleau geo...@bellsouth.net
Jean-Pierre Radley
Robert Lipe
>The gcc 2.9.5pl1 release and the needed binutils on the SCO site
>are incompatible ( binutils still has endless references to -belf insted
>of -melf )
GCC 2.95 does not need binutils. In fact, binutils (especially the
assembler and linker) are _less_ compatible with GCC than the free SCO
native assembler and linker.
Geoff Bleau
Robert Lipe wrote:
Well - I followed the instructions on the SCO site - and installed
gcc 2.9.5 along with the Linker and Application Libraries from
the SCO cd ( all this on SCO 5.0.4 )
Then tried to compile tcp_wrappers 7.6.
Bombed - complained about a missing ' ar ' file.
When I asked back in this group ( or gcc,help ) - it was
suggested that I needed binutils - as that would be the source
of ' ar '.
When I tried to install the binutils from the SCO site - it barfed
due to all the references to -belf instead of -melf ( catch 22 ?? )
So - what is the REAL answer to be able to compile tcp_wrappers ???
G
Brian K. White
the answer is edit the makefile. you will find you almost always have to
edit the makefile. get use to it. No one is writing makefiles for the odd
case of gcc-on-OSR5. if the makefile author (actually the autoconf author)
is even aware of OSR5 they almost always have a section that is correct for
the native compiler. the other sections are correct for gcc on Linux
usually, which is not the same as gcc on OSR5.
the most complete makefile I've seen that actually has complete and correct
seperate sections for all the different possible combinations of which
compiler on which OS, is the one found in c-kermit. ... although even
there, I seem to recall having to edit that one too, to take into account
that gcc had been using -melf on osr5 up untill recently, and now it uses
-belf. or maybe it's the other way around... and I think there was some
other problem with the osr5.0.5-net-gcc-curses stanza too but I forget what.
basically you need to "man cc" "man ld" as well as "man gcc" and "man ld"
from a linux box, figure out what system your makefile is assuming, and
translate the gcc and ld options. From what you said, it's probably trying
to handle gcc on osr5, but the old gcc which had a few options modified to
be similar to the native cc. which means your makefile aspired to be better
than most, and thus perversely is one of the most non-intuitive to figure
out unless you give up all hope that any makefile should work out of the
box. If you are simply resigned to checking over every makefile for
correctness with current gcc on osr5, then you never have this problem.
do a net search for "gcc SCO" and find some pages by Robert Lipe to see some
of the main things that always need to be fixed on cc/gcc command lines
also note that that document is itself a little out of date in that it has
the -melf/-belf backwards, although then again, it is correct for the
version of gcc that is referenced in that document. that's just not
gcc-2.95. the other stuff all applies.
--
Brian K. White http://www.squonk.net/users/linut
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
Robert Lipe
>Geoff Bleau wrote:
>>
>> Robert Lipe wrote:
>>
>> > Geoff Bleau <geo...@bellsouth.net> writes:
>> >
>> > >The gcc 2.9.5pl1 release and the needed binutils on the SCO site
>> > >are incompatible ( binutils still has endless references to -belf insted
>> > >of -melf )
>> >
>> > GCC 2.95 does not need binutils. In fact, binutils (especially the
>> > assembler and linker) are _less_ compatible with GCC than the free SCO
>> > native assembler and linker.
>>
>> Well - I followed the instructions on the SCO site - and installed
>> gcc 2.9.5 along with the Linker and Application Libraries from
>> the SCO cd ( all this on SCO 5.0.4 )
That's what you should have done.
>> Then tried to compile tcp_wrappers 7.6.
>>
>> Bombed - complained about a missing ' ar ' file.
>>
>> When I asked back in this group ( or gcc,help ) - it was
>> suggested that I needed binutils - as that would be the source
>> of ' ar '.
Ar should have been installed as part of the L&L package.
>> When I tried to install the binutils from the SCO site - it barfed
>> due to all the references to -belf instead of -melf ( catch 22 ?? )
>>
>> So - what is the REAL answer to be able to compile tcp_wrappers ???
>the answer is edit the makefile. you will find you almost always have to
>edit the makefile. get use to it. No one is writing makefiles for the odd
>case of gcc-on-OSR5. if the makefile author (actually the autoconf author)
>is even aware of OSR5 they almost always have a section that is correct for
>the native compiler. the other sections are correct for gcc on Linux
>usually, which is not the same as gcc on OSR5.
The current autoconf knows how to handle this. If you're building
something that is autoconfiscated and is using an outdated one, just
rebuild the configure.in/Makefile.in's with a current autoconf.
>that gcc had been using -melf on osr5 up untill recently, and now it uses
>-belf. or maybe it's the other way around... and I think there was some
GCC until '96 used -belf. Newer GCC defaults to ELF and uses -mcoff to
flip back.
>than most, and thus perversely is one of the most non-intuitive to figure
>out unless you give up all hope that any makefile should work out of the
>box. If you are simply resigned to checking over every makefile for
>correctness with current gcc on osr5, then you never have this problem.
>do a net search for "gcc SCO" and find some pages by Robert Lipe to see some
>of the main things that always need to be fixed on cc/gcc command lines
>also note that that document is itself a little out of date in that it has
>the -melf/-belf backwards, although then again, it is correct for the
>version of gcc that is referenced in that document. that's just not
users are welcome to submit patches to the GCC doc:
http://gcc.gnu.org/install/specific.html#ix86-*-sco3.2v5*
or add entries to the SCO Programmer's FAQ at
http://www.zenez.com/cgi-bin/scoprogfaq/faq.pl
Sometimes, I wonder if we'd be doing the SCO community a favor by
deleting all the old compilers and all the old doc; it only seems
to confuse people..
Fulko Hew
> Sometimes, I wonder if we'd be doing the SCO community a favor by
> deleting all the old compilers and all the old doc; it only seems
> to confuse people..
Hear, Hear, I'd vote for that!
-------------------------------------------------------------------------------
Fulko Hew, Voice: 905-333-6000 x 6010
Senior Engineering Designer, Direct: 905-333-6010
Northrop Grumman-Canada, Ltd. Fax: 905-333-6050
777 Walkers Line, Home: fulko%fk...@wecan.com
Burlington, Ontario, Canada, L7N 2G1 Work: fu...@wecan.com
Geoff Bleau
Robert Lipe wrote:
> That's what you should have done.
>
> >> Then tried to compile tcp_wrappers 7.6.
> >>
> >> Bombed - complained about a missing ' ar ' file.
> >>
>
>
> Ar should have been installed as part of the L&L package.
>
>
That may be the core of the problem.
AR does not install on 5.0.4 when installing
the " Linker and Application Development Libraries "
I believe that is why the original suggestion to install
'binutils' was made.
I just deleted and reinstalled the Linker & Libraries package
to be sure- no 'ar' or /usr/binar or /usr/ccs/bin/ar gets installed.
Is there another option ( short of installing the DevSys ) to
get the needed packages off the SCO distribution ???
Jean-Pierre Radley
| >>
| >> When I asked back in this group ( or gcc,help ) - it was
| >> suggested that I needed binutils - as that would be the source
| >> of ' ar '.
|
I have a feeling it is not...
--
JP