If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):
From - Tue May 2 05:18:21 2000
Path: news.randori.com!hermes.visi.com!news-out.visi.com!news-out.transit.remarq.com.MISMATCH!sn-xit-03!supernews.com!sn-inject-01!corp.supernews.com!not-for-mail
From: "Brian K. White" <linut@squonk.net>
Newsgroups: comp.unix.sco.misc
Subject: Re: SSH on SCO 5.0.5
Date: Tue, 02 May 2000 03:10:11 -0400
Organization: Albany Burner Control
Lines: 78
Message-ID: <390E7F53.D62240DB@squonk.net>
References: <390DC05E.C616D676@barroco.com.br> <20000501220810.E26677@jpradley.jpr.com> <390E525B.35E22B6A@bellsouth.net> <sgsljtej1g226@corp.supernews.com> <390E5BD8.3FB6582C@bellsouth.net>
X-Complaints-To: newsabuse@supernews.com
X-Mailer: Mozilla 4.7 [en] (X11; I; SCO_SV 3.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cache-Post-Path: firth.squonk.net!unknown@dialup-079.squonk.net
X-Cache: nntpcache 2.3.3 (see http://www.nntpcache.org/)
Xref: news.randori.com comp.unix.sco.misc:59283
X-Mozilla-Status: 8010
X-Mozilla-Status2: 00000000
Geoff Bleau wrote:
>
> Robert Lipe wrote:
>
> > Geoff Bleau <geoffb@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 )
>
> 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
>
> --
> " Bigamy is having one wife too many.
> Monogamy is the same "
>
> Geoff Bleau geoffb@bellsouth.net
>
> http://www.flsoft.com
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
Enter your email address for automatic notification of new posts here
(be sure to whitelist 'feedburner.com' if you use spam filtering)
| Views for this page | ||||
|---|---|---|---|---|
| Today | This Week | This Month | This Year | Overall |
| 2 | 5 | 13 | 13 | 2,382 |
/Bofcusm/339.html copyright 1997-2004 (various authors) All Rights Reserved
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Click here to add your comments