Baslinux mailing list

[sindi keesan <keesan AT sdf.lonestar.org>]

Perhaps it would be easier to install the earlier version of IRAF on a 
smaller linux - Slackware 4.0 (or Basiclinux 3.40, which uses the same 
library but a newer kernel).

David, do you want to try helping Paul with the above?

Maybe he could start over on the laptop, without qemu, in a 1GB or 2GB 
partition (would that be enough to expand IRAF into, with a few 100MB for 
the dependencies in linux?).  That would be one layer less of complexity 
without the emulator.  You can look up which packages contain which 
libraries and install only the parts you need, which are often only 10% of 
a package.

The laptop has a 4GB hard drive.

We are planning to install DOS and 2 or 3 linuxes on our 750MB drive.

Is there an older qemu binary around that does not need glibc 2.3?

On Thu, 27 Apr 2006, Paul Makinen wrote:


David Moberg wrote:
> > I downloaded and unpacked it, but I don't know how to make it work.

Paul wrote:

> Thanks for trying...
>
> As it turns out, FITS is not what I would call "turnkey software"...I
> installed the Cygwin version on my desktop, and then I had to run the
> IRAF sham install routine ./install -n about six times before I got
> it right...  The worst of the problems is that the directory
> structure used by the install routine is different from that
> advertised in the install documentation....and you have to make some
> intelligent guesses as to where the DS9 FITS display package should go...
>
> Anyway, I did eventually get it up and running, but unfortunately,
> the specific piece of layered software I need to kick off the
> analysis process (one of the STECF routines) refuses to compile under
> Cygwin...but there are fedora, suse, and hpux  binaries. And, as it
> turns out, 99 dollars will buy a version of everything compiled under Cygwin

As David said, there is a Slackware 4.0 older binary.  Try installing that 
and once you figure it out, maybe later you can get the newer binary 
working too, with later glibc.


> > For a package that is this large and complex, wouldn't it be better to
> > start with a large distribution and gradually remove unnecessary
> > packages from the working setup?
>
>
> I think there may be non-obvious dependencies among the packages, so
> I'm not sure how easy this is going to be in practice...
>
> -p
>
>
>
> > David
> > _______________________________________________
> > BasLinux mailing list
> > http://lists.ibiblio.org/mailman/listinfo/baslinux
>
>
> _______________________________________________
> BasLinux mailing list
> http://lists.ibiblio.org/mailman/listinfo/baslinux

keesan AT sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org