[OpenIndiana-discuss] stty source code
pulaskite at yahoo.com
Wed Sep 5 15:20:18 UTC 2012
I find that I am unable to convert a newline returned by a remote host to NL-CR for display in a terminal window.
So instead of:
I thought I'd try to find out why. I also found I can't actually set "-onlcr" w/ stty though I can toggle "olcuc". Some things in stty work and some don't.
I've actually modified the forth interpreter to send NL-CR and reassembled the code, so my original problem is solved. But it bugs me that things don't seem to work properly. While ttys are not used much now in the wider world, they are still heavily used as the interface to microcontrollers both for interaction and for loading new firmware.
I'm *very* resistant to having to use Linux for this and simply won't use Windows which is the predominate environment for working w/ microcontrollers. Unfortunately there's a fair bit of open source stuff that doesn't like Solaris :-( It was a good bit of work to get this far.
In view of the admin overhead, I'll probably defer working on ttymon & friends until I can setup a faster OI machine. Working on OI wasn't actually in my plans at this time.
Thanks for the pointers.
--- On Wed, 9/5/12, James Carlson <carlsonj at workingcode.com> wrote:
> From: James Carlson <carlsonj at workingcode.com>
> Subject: Re: [OpenIndiana-discuss] stty source code
> To: "Discussion list for OpenIndiana" <openindiana-discuss at openindiana.org>
> Date: Wednesday, September 5, 2012, 7:52 AM
> Reginald Beardsley wrote:
> > I've cloned the repository but find that the Makefile
> is expecting state to be set in the shell. Where would
> I find details on what I need to have set to compile just
> the things in
> > usr/src/cmd/ttymon
> > Is that possible?
> Look for the "bldenv" and "ws" scripts, part of the ON build
> tools in
> usr/src/tools. A good starting point might be:
> > I'm really not eager to take on building
> everything as my OI box is a
> dual core Atom.
> Building just a portion of the tree can be a little
> tricky. In general,
> you have to do a "make install" in usr/src/head to make sure
> that you
> have a proto area with the right header files. You
> might then be able
> to build in usr/src/cmd/ttymon, but it's very likely that
> you'll have to
> build some of the libraries on which it depends first.
> The ON build was never designed to allow builds of
> individual parts of
> the tree, except after building everything.
> An interesting (and possibly useful) project would be to
> break up the
> usr/src/cmd and usr/src/lib trees into separate projects, so
> that each
> can be built separately. Doing so, though, likely
> requires a lot of
> careful planning so that flag-day changes are still
> reasonably doable.
> If you have a really slow target machine, it might be an
> idea to work on a cross-compilation environment on a faster
> one. I'm
> not sure, though, how hard that'd be.
> Why are you hacking at stty ... ?
> James Carlson 42.703N
> 71.076W <carlsonj at workingcode.com>
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
More information about the OpenIndiana-discuss