Where do I get a package from (SUNWspro - needed for IpFilter)
Rob
and am going mad as I can't find a list of packages! I also try and search
for packages and it just turns into a nightmare.
I'm specifically looking for SUNWspro which,I believe, is trial software. I
need this in order to "make" IP Filter on Solaris 8. I don't seem to have
"cc" installed (I have cc but not where it's linked to.
/Rob.
Solaris 8 (32 bit mode) - Ultra 10 (32bit obviously)
John D Groenveld
compiler if you run 64bit. In that case, www.sun.com would be
the logical place to look for a trial copy.
John
groe...@acm.org
Orbv
have to
pay for it. If you are not willing to splash with the cash try downloading gcc
from www.sunfreeware.com.
> Solaris 8 (32 bit mode) - Ultra 10 (32bit obviously)
Are you sure? By default all U10's will run 64-bit Solaris 7 or 8.
Dave Uhring
After you download and install gcc-2.95.3 from www.sunfreeware.com, rename
/usr/ucb/cc to /usr/ucb/cc.orig, them symlink /usr/local/bin/gcc to
/usr/ucb/cc. Or you can set up an environmental variable CC=gcc. Sun's
make utility and gcc will build ipfilter.
Logan Shaw
Dave Uhring <duh...@charter.net> wrote:
>Rob wrote:
>> I'm specifically looking for SUNWspro which,I believe, is trial software.
>> I
>> need this in order to "make" IP Filter on Solaris 8. I don't seem to have
>> "cc" installed (I have cc but not where it's linked to.
>After you download and install gcc-2.95.3 from www.sunfreeware.com, rename
>/usr/ucb/cc to /usr/ucb/cc.orig, them symlink /usr/local/bin/gcc to
>/usr/ucb/cc.
Isn't /usr/ucb/cc supposed to be the way of invoking the compiler with
BSD source compatibility stuff, i.e. options to use the includes and
libraries /usr/ucbinclude and /usr/ucblib? So linking it to gcc would
be kind of a strange thing to do. It seems like it would be better to
link /usr/bin/cc to gcc.
- Logan
--
my your his her our their _its_
I'm you're he's she's we're they're _it's_
Dave Uhring
Point is well taken, but /usr/ucb/cc will still be there to grab the
unwary. Some people believe that /usr/ucb should be removed from one's
PATH. That is good if you don't need vipw or a BSD install utility. The
only place in Solaris 8 where there is a vipw is in /usr/ucb.
I have encountered quite a few sources which insisted on using cc and I'm
either too lazy or too forgetful to remember to set my environment CC=gcc
when configuring. Besides some sources don't even use the GNU configure
script, making it necessary to find CC= in every one of the Makefiles.
Perhaps I'm mistaken, but having an executable cc is at least convenient
and the symlink does that.
Steve Bellenot
>/usr/ucb/cc to /usr/ucb/cc.orig, them symlink /usr/local/bin/gcc to
>/usr/ucb/cc. Or you can set up an environmental variable CC=gcc. Sun's
>make utility and gcc will build ipfilter.
>
Moving or even Removing /usr/ucb/cc doesn't bother me, but it is
foolish to make /usr/ucb/cc point elsewhere. The next OS upgrade
will wipe out the link. You would be better off making /usr/local/bin/cc
a link to /usr/local/bin/gcc.
--
http://www.math.fsu.edu/~bellenot
bellenot <At/> math.fsu.edu
+1.850.644.7189 (4053fax)
Mike Delaney
duh...@charter.net said something similar to:
: Logan Shaw wrote:
:
: > In article <te1obh3...@corp.supernews.com>,
: > Dave Uhring <duh...@charter.net> wrote:
: >>Rob wrote:
: >>> I'm specifically looking for SUNWspro which,I believe, is trial
: >>> software. I
: >>> need this in order to "make" IP Filter on Solaris 8. I don't seem to
: >>> have "cc" installed (I have cc but not where it's linked to.
: >
: >>After you download and install gcc-2.95.3 from www.sunfreeware.com, rename
: >>/usr/ucb/cc to /usr/ucb/cc.orig, them symlink /usr/local/bin/gcc to
: >>/usr/ucb/cc.
: >
: > Isn't /usr/ucb/cc supposed to be the way of invoking the compiler with
: > BSD source compatibility stuff, i.e. options to use the includes and
: > libraries /usr/ucbinclude and /usr/ucblib? So linking it to gcc would
: > be kind of a strange thing to do. It seems like it would be better to
: > link /usr/bin/cc to gcc.
: >
: > - Logan
:
: Point is well taken, but /usr/ucb/cc will still be there to grab the
: unwary. Some people believe that /usr/ucb should be removed from one's
: PATH. That is good if you don't need vipw or a BSD install utility. The
: only place in Solaris 8 where there is a vipw is in /usr/ucb.
Creative application of aliases, shell functions, and the editing
of makefiles that assume the first install binary in the path
is BSD compatible solve those problems quite nicely (and sometimes
better than adding /usr/ucb to the path would). I've been bitten by
/usr/ucb being in the path a few times too many to ever put it in
there again, even at the end.
: I have encountered quite a few sources which insisted on using cc and I'm
: either too lazy or too forgetful to remember to set my environment CC=gcc
: when configuring. Besides some sources don't even use the GNU configure
: script, making it necessary to find CC= in every one of the Makefiles.
: Perhaps I'm mistaken, but having an executable cc is at least convenient
: and the symlink does that.
It is, but one really should give makefiles a once over before building
anyway as even the best configure script occasionally screws up, and
most things that don't come with one tend to need at least minor tweeking.
--
Mike Delaney <mde...@computer.org>
"...Microsoft follows standards. In much the same manner that fish follow
migrating caribou." "Now I have this image in my mind of a fish embracing and
extending a caribou." -- Paul Tomblin and Christian Bauernfeind in the SDM
Philip Brown
>...
>Point is well taken, but /usr/ucb/cc will still be there to grab the
>unwary. Some people believe that /usr/ucb should be removed from one's
>PATH. That is good if you don't need vipw or a BSD install utility.
Is it so hard to type /usr/ucb/vipw instead of vipw? I hope you arent using
it that often: thats what "useradd / usermod" are for.
as for "BSD install" type stuff, you have not one but two options:
a) cp /usr/ucb/install /usr/local/bin/ginstall
b) go install GNU install from the fileutils package or wherever it is.
Again, install it as "ginstall".
GNU autoconf automatically checks for the existance of "ginstall".
--
[Trim the no-bots from my address to reply to me by email!]
[ Do NOT email-CC me on posts. Pick one or the other.]
S.1618 http://thomas.loc.gov/cgi-bin/bdquery/z?d105:SN01618:@@@D
The word of the day is mispergitude