Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
ncurses 5.7 and terminal fun
26 views
Skip to first unread message
Lewis Rosenthal
Jun 28, 2012, 12:49:46 AM6/28/12
to
Hi, all...
Finally got my build system working again, but bumped into these issues
tonight when cobbling together less 4.4.3:
1. Running less.exe yields a common message (common at least in a Google
search):
WARNING: terminal is not fully functional
Setting TERM=os2 doesn't resolve this, even though os2 is present under
/usr/share/terminfo. However, it does seem to like xterm and rxvt. Thus,
I'm not really sure where it's grabbing the terminal defs.
Using xterm or rxvt results in the window session shrinking to about
20x25 from 80x25, so that's not even a real workaround. Of course, I can
just ignore the message, but I'm thinking that there should be some way
to set the TERM in the Makefile (unless I'm being too presumptuous in
thinking that there really isn't any harm in locking OS/2 users into a
single terminal environment - I guess some people would launch less from
an xterm under OS/2).
2. (Annoying) For some reason, likely related to my lack of experience
building on anything besides Linux, where one gets spoiled by the
config/make/install routine except for building very old or very new
stuff on (conversely) very old or very new OSes or with very old or very
new tools, I am have a real time of trying to *not* link tinfo5.dll
dynamically. I really want to build less as a package usable with only
libc065 (building with gcc 4.4.6) as a dependency.
Any thoughts/pointers/tips (including "don't quit your day job") are
welcome!
Thanks!!
--
Lewis
-------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE, CWTS
Rosenthal & Rosenthal, LLC www.2rosenthals.com
Need a managed Wi-Fi hotspot? www.hautspot.com
visit my IT blog www.2rosenthals.net/wordpress
-------------------------------------------------------------
--- Posted via news://freenews.netfront.net/ - Complaints to ne...@netfront.net ---
Finally got my build system working again, but bumped into these issues
tonight when cobbling together less 4.4.3:
1. Running less.exe yields a common message (common at least in a Google
search):
WARNING: terminal is not fully functional
Setting TERM=os2 doesn't resolve this, even though os2 is present under
/usr/share/terminfo. However, it does seem to like xterm and rxvt. Thus,
I'm not really sure where it's grabbing the terminal defs.
Using xterm or rxvt results in the window session shrinking to about
20x25 from 80x25, so that's not even a real workaround. Of course, I can
just ignore the message, but I'm thinking that there should be some way
to set the TERM in the Makefile (unless I'm being too presumptuous in
thinking that there really isn't any harm in locking OS/2 users into a
single terminal environment - I guess some people would launch less from
an xterm under OS/2).
2. (Annoying) For some reason, likely related to my lack of experience
building on anything besides Linux, where one gets spoiled by the
config/make/install routine except for building very old or very new
stuff on (conversely) very old or very new OSes or with very old or very
new tools, I am have a real time of trying to *not* link tinfo5.dll
dynamically. I really want to build less as a package usable with only
libc065 (building with gcc 4.4.6) as a dependency.
Any thoughts/pointers/tips (including "don't quit your day job") are
welcome!
Thanks!!
--
Lewis
-------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE, CWTS
Rosenthal & Rosenthal, LLC www.2rosenthals.com
Need a managed Wi-Fi hotspot? www.hautspot.com
visit my IT blog www.2rosenthals.net/wordpress
-------------------------------------------------------------
--- Posted via news://freenews.netfront.net/ - Complaints to ne...@netfront.net ---
dic...@his.com
Jun 28, 2012, 5:33:36 AM6/28/12
to
On Thursday, June 28, 2012 12:49:46 AM UTC-4, Lewis Rosenthal wrote:
> 2. (Annoying) For some reason, likely related to my lack of experience
> building on anything besides Linux, where one gets spoiled by the
> config/make/install routine except for building very old or very new
> stuff on (conversely) very old or very new OSes or with very old or very
> new tools, I am have a real time of trying to *not* link tinfo5.dll
> dynamically. I really want to build less as a package usable with only
> libc065 (building with gcc 4.4.6) as a dependency.
tinfo (tinfo5.dll) is an optional split-out of low-level stuff from ncurses
> 2. (Annoying) For some reason, likely related to my lack of experience
> building on anything besides Linux, where one gets spoiled by the
> config/make/install routine except for building very old or very new
> stuff on (conversely) very old or very new OSes or with very old or very
> new tools, I am have a real time of trying to *not* link tinfo5.dll
> dynamically. I really want to build less as a package usable with only
> libc065 (building with gcc 4.4.6) as a dependency.
(ncurses5.dll). portable applications should always check for both cases.
Lewis Rosenthal
Jun 28, 2012, 8:27:22 AM6/28/12
to
On 06/28/12 05:33 am, dic...@his.com thus wrote :
Thanks for the follow-up.
If I run the exe while booted from a partition which does not have
tinfo5.dll in libpath, the app won't run, so it's definitely linked
dynamically.
PMDLL says that less.exe is looking for:
libc065
tinfo5
gcc446 (which is rather odd)
tinfo5.dll is looking for urpo.dll, which PMDLL says can't be loaded,
though I'm not seeing a problem with this (or with gcc446, as the
alternate install definitely does not have a full gcc install).
So, what would I pass to the compiler to have the executable check for
both cases?
TIA
If I run the exe while booted from a partition which does not have
tinfo5.dll in libpath, the app won't run, so it's definitely linked
dynamically.
PMDLL says that less.exe is looking for:
libc065
tinfo5
gcc446 (which is rather odd)
tinfo5.dll is looking for urpo.dll, which PMDLL says can't be loaded,
though I'm not seeing a problem with this (or with gcc446, as the
alternate install definitely does not have a full gcc install).
So, what would I pass to the compiler to have the executable check for
both cases?
TIA
Dave Yeo
Jun 28, 2012, 11:08:04 AM6/28/12
to
For tinfo5.dll you'll have to check your ncurses install for a static
version of the lib and if one doesn't exist, rebuild ncurses with
configure --disable-shared --enable-static.
In theory -bstatic should link it statically, in practice the simplest
is to move the import lib out of the way which will force linking the
static version.
btw, sometimes set TERM=ansi seems to work better then TERM=os2
Dave
Trevor Hemsley
Jun 28, 2012, 12:53:41 PM6/28/12
to
On Thu, 28 Jun 2012 04:49:46 UTC in comp.os.os2.programmer.porting, Lewis
Rosenthal <lgros...@2-de-sp-am-2rosenthals.com> wrote:
> WARNING: terminal is not fully functional
TERM=ansi-color-3
Rosenthal <lgros...@2-de-sp-am-2rosenthals.com> wrote:
> WARNING: terminal is not fully functional
works for me
--
Trevor Hemsley, Brighton, UK
Trevor dot Hemsley at ntlworld dot com
Lewis Rosenthal
Jun 30, 2012, 8:53:04 PM6/30/12
to
On 06/28/12 11:08 am, Dave Yeo thus wrote :
Thank you, thank you, thank you!
:-)
:-)
Lewis Rosenthal
Jun 30, 2012, 8:59:43 PM6/30/12
to
On 06/28/12 12:53 pm, Trevor Hemsley thus wrote :
I just had another interesting path discovery today, after Nick's EMX
build of ssh kept complaining that it couldn't find my terminal setup.
In that case, UNIXROOT was really confusing it (I know that it *used* to
work right), and since it is EMX and not gcc and doesn;t seem to
understand the kLibc path rewriters - or symlinks - , I actually had to
move my %ETC%/ssh directory (C:\MPTN\ETC\ssh) to %UNIXROOT%/etc/ssh
(J:\etc\ssh) to satisfy its curiosity.
BTW, I just checked, and neither ansi nor ansi-color-3 seems to work for
this build of less. I'll need to poke around a bit mor eto find out
where it's getting lost looking for terminfo.
Cheers/2
> On Thu, 28 Jun 2012 04:49:46 UTC in comp.os.os2.programmer.porting, Lewis
> Rosenthal <lgros...@2-de-sp-am-2rosenthals.com> wrote:
>
>> WARNING: terminal is not fully functional
>
> TERM=ansi-color-3
>
> works for me
>
And thank you, too, Trevor!
> Rosenthal <lgros...@2-de-sp-am-2rosenthals.com> wrote:
>
>> WARNING: terminal is not fully functional
>
> TERM=ansi-color-3
>
> works for me
>
I just had another interesting path discovery today, after Nick's EMX
build of ssh kept complaining that it couldn't find my terminal setup.
In that case, UNIXROOT was really confusing it (I know that it *used* to
work right), and since it is EMX and not gcc and doesn;t seem to
understand the kLibc path rewriters - or symlinks - , I actually had to
move my %ETC%/ssh directory (C:\MPTN\ETC\ssh) to %UNIXROOT%/etc/ssh
(J:\etc\ssh) to satisfy its curiosity.
BTW, I just checked, and neither ansi nor ansi-color-3 seems to work for
this build of less. I'll need to poke around a bit mor eto find out
where it's getting lost looking for terminfo.
Cheers/2
Dave Yeo
Jul 1, 2012, 1:15:26 AM7/1/12
to
Lewis Rosenthal wrote:
> On 06/28/12 12:53 pm, Trevor Hemsley thus wrote :
>> On Thu, 28 Jun 2012 04:49:46 UTC in comp.os.os2.programmer.porting, Lewis
>> Rosenthal<lgros...@2-de-sp-am-2rosenthals.com> wrote:
>>
>>> WARNING: terminal is not fully functional
>>
>> TERM=ansi-color-3
>>
>> works for me
>>
> And thank you, too, Trevor!
>
> I just had another interesting path discovery today, after Nick's EMX
> build of ssh kept complaining that it couldn't find my terminal setup.
> In that case, UNIXROOT was really confusing it (I know that it *used* to
> work right), and since it is EMX and not gcc and doesn;t seem to
> understand the kLibc path rewriters - or symlinks - , I actually had to
> move my %ETC%/ssh directory (C:\MPTN\ETC\ssh) to %UNIXROOT%/etc/ssh
> (J:\etc\ssh) to satisfy its curiosity.
UNIXROOT was introduced back in the EMX days. This causes conflicts as
> On 06/28/12 12:53 pm, Trevor Hemsley thus wrote :
>> On Thu, 28 Jun 2012 04:49:46 UTC in comp.os.os2.programmer.porting, Lewis
>> Rosenthal<lgros...@2-de-sp-am-2rosenthals.com> wrote:
>>
>>> WARNING: terminal is not fully functional
>>
>> TERM=ansi-color-3
>>
>> works for me
>>
> And thank you, too, Trevor!
>
> I just had another interesting path discovery today, after Nick's EMX
> build of ssh kept complaining that it couldn't find my terminal setup.
> In that case, UNIXROOT was really confusing it (I know that it *used* to
> work right), and since it is EMX and not gcc and doesn;t seem to
> understand the kLibc path rewriters - or symlinks - , I actually had to
> move my %ETC%/ssh directory (C:\MPTN\ETC\ssh) to %UNIXROOT%/etc/ssh
> (J:\etc\ssh) to satisfy its curiosity.
there are EMX ports built to rely on UNIXROOT and now klibc ports also
rely on UNIXROOT. And while EMX and klibc are close to source
compatible, they are not binary compatible. Really klibc and especially
the yum/rpm crew should have chose another variable.
>
> BTW, I just checked, and neither ansi nor ansi-color-3 seems to work for
> this build of less. I'll need to poke around a bit mor eto find out
> where it's getting lost looking for terminfo.
can probably be changed by a configure argument but ideally less should
be patched to look in %ETC%. (lots of EMX ports used \emx\etc or
x:\emx\etc.)
Dave
0 new messages