Er, I haven't followed this too closely since it seemed to be derailing over
spelling but Solaris 10 is free. I haven't tried an x86 install as I have
Sun machines but I'd guess they install just as painlessly.
http://www.sun.com/software/solaris/get.jsp
> -----Original Message-----
> From: slug@nks.net [mailto:slug@nks.net] On Behalf Of Levi Bard
> Sent: Wednesday, March 01, 2006 9:59 AM
> To: slug@nks.net
> Subject: Re: [SLUG] OT: OpenSalarus
>
> > <snip>
> > > Since we had a working C compiler, we decided to install Galeon,
> > > Tosha's browser of choice. This required us to get much newer
> > > versions of the GTK+ libraries than the ones that had been installed.
> > > After chasing down all the requisites (glib, atk, pango, ...), we
> > > began compiling them. Unfortunately, no matter what we did, we were
> > > unable to get the GTK+ configure script to see that pango was
> > > installed, even by passing it the path. While it was perhaps not
> > > Solaris's fault that we couldn't build GTK+, the fact that there was
> > > only a poor selection of ancient software available for install
> > > certainly was, and this was the last straw for us. For crying out
> > > loud, we could have installed Slackware 8 and had the same currency of
> > > software, except it would have worked out of the box without a lot of
> > > futzing. We never got around to actually looking at or building the
> > > actual OpenSolaris source, because we were hoping for a usable system
> > > first. If you've actually read down this far, go get yourself a
> > > cookie; you've earned it.
> >
> > If you were using gcc to compile, you'll notice it'll link stuff that
> may not
> > be found at runtime. Solaris has a pretty basic list of runtime stuff
> > available. You might want to try `crle` (I think) and add stuff
> > like /usr/local/lib and maybe /opt/lib to your runtime linker path for
> stuff
> > installed from SFW. (Make sure you include /lib and /usr/lib first, as
> if
> > you don't include them in the list of paths you'll end up stuff not
> > finding /lib and /usr/lib...)
>
> Yeah, we actually found instructions for setting up the paths and
> everything for gcc, and we were able to build and install several of
> the libs. configure for the package that failed would see pango
> version whatever; there was some particular extension that it wanted,
> and after going back to pango and checking that we'd built it (and
> rebuilding/reinstalling just in case), the the build system still
> wouldn't use it. There was some alternative, but I forget what it was
> now and in any case, it didn't work either. This isn't really a
> problem with Solaris per se, but had it had a decent selection of
> software, or at least recentish libraries, we wouldn't have had to
> deal with it.
>
> --
> Debianista!
> http://www.gnu.org/philosophy/no-word-attachments.html
>
> -----------------------------------------------------------------------
> This list is provided as an unmoderated internet service by Networked
> Knowledge Systems (NKS). Views and opinions expressed in messages
> posted are those of the author and do not necessarily reflect the
> official policy or position of NKS or any of its employees.
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:26:21 EDT