Re: Mash for Linux + Notes

• To: emase@uclink4.berkeley.edu, openmash-users@gumby.CS.Berkeley.EDU
• Subject: Re: Mash for Linux + Notes
• From: Marcia Perry (ITG staff) <mperry@george.lbl.gov>
• Date: Thu, 10 Feb 2000 11:00:32 -0800 (PST)

Hi All,
I've built mash on Solaris without doing 'make install' for
Tcl/Tk.  I built Tcl/Tk, Otcl in my $HOME directory and left
the libs and binaries where they were built.  As long as I
specified the correct paths to Tcl/Tk in the Otcl, TclCL,
and mash ./configure command line, all was ok.  So, it's a
matter of consistency and correct pathnames not installation
in a 'standard' place (like /usr/local or /usr/bin...).

About osfcn.h--I think it just includes unistd.h, which
would explain why replacing #include <osfcn.h> with
#include <unistd.h> fixes stuff.

Any more insights are quite welcome--

Marcia

• Prev by Date: Mash under Linux
• Next by Date: Paced transmission code
• Prev by thread: Mash for Linux - Alternative Notes (Errata)
• Next by thread: Mash under Linux
• Index(es):
  • Date
  • Thread