mingw-msys Mailing List for MinGW - Minimalist GNU for Windows

On 25/05/2011 03:14 p.m., Andy Koppe wrote:
 > On 25 May 2011 16:05, Cesar Romani wrote:
 >> I'm using mintty 0.9.7, msys 1.0.17, less 4.4.1 on Win XP.
 >> mintty works fine with groff-1.20.1-2-msys but not with groff-mingw
 >> version 1.20.1
 >>
 >> If I do:
 >> groff -Tascii -P-c -mandoc /usr/share/man/man1/bash.1|less
 >>
 >> mintty hangs up indefinitely and you cannot proceed any further.
 >> It only works if I do:
 >> cat /usr/share/man/man1/bash.1 | groff -Tascii -P-c -mandoc | less
 >>
 >> On the cmd console groff-mingw works fine.
 >
 > This sounds a lot like an issue Keith Marshall previously reported
 > regarding building groff-mingw in rxvt and that I reproduced in
 > mintty, which suggested that it's to do with the MSYS (nee Cygwin) pty
 > implementation rather than either terminal as such. The usual
 > explanations about incompatibility between interactive native console
 > programs and ptys didn't seem to apply though, but unfortunately I
 > never got round to do any more than confirm that the issue still
 > exists with recent Cygwin.
 >
 > Right, since I can only see msys-groff in the mingw-get repository,
 > did you build mingw-groff from source? And is that with msys-less or
 > mingw-less?

Yes, I built mingw-groff from source and I'm using msys-less but the
problem happens with or without less.

Best regards,

-- 
Cesar

On 25 May 2011 16:05, Cesar Romani wrote:
> I'm using mintty 0.9.7, msys 1.0.17, less 4.4.1 on Win XP.
> mintty works fine with groff-1.20.1-2-msys but not with groff-mingw
> version 1.20.1
>
> If I do:
> groff -Tascii -P-c -mandoc /usr/share/man/man1/bash.1|less
>
> mintty hangs up indefinitely and you cannot proceed any further.
> It only works if I do:
> cat /usr/share/man/man1/bash.1 | groff -Tascii -P-c -mandoc | less
>
> On the cmd console groff-mingw works fine.

This sounds a lot like an issue Keith Marshall previously reported
regarding building groff-mingw in rxvt and that I reproduced in
mintty, which suggested that it's to do with the MSYS (nee Cygwin) pty
implementation rather than either terminal as such. The usual
explanations about incompatibility between interactive native console
programs and ptys didn't seem to apply though, but unfortunately I
never got round to do any more than confirm that the issue still
exists with recent Cygwin.

Right, since I can only see msys-groff in the mingw-get repository,
did you build mingw-groff from source? And is that with msys-less or
mingw-less?

Andy

I'm using mintty 0.9.7, msys 1.0.17, less 4.4.1 on Win XP.
mintty works fine with groff-1.20.1-2-msys but not with groff-mingw
version 1.20.1

If I do:
groff -Tascii -P-c -mandoc /usr/share/man/man1/bash.1|less

mintty hangs up indefinitely and you cannot proceed any further.
It only works if I do:
cat /usr/share/man/man1/bash.1 | groff -Tascii -P-c -mandoc | less

On the cmd console groff-mingw works fine.

Many thanks in advance,

-- 
Cesar

On 11/05/2011 06:37 a.m., Andy Koppe wrote:
 > On 11 May 2011 12:21, Chris Sutcliffe wrote:
 >> On 10 May 2011 19:33, Cesar Romani wrote:
 >>> I'm using mintty 0.9.7, msys 1.0.17, less 4.4.1, groff 1.20.1,
 >>> man 1.6-mingw-beta-1 on Win XP.
 >>> If I issue a man command, say "man bash", the output isn't sent to the
 >>> pager, but the entire page will scroll on the screen without pausing.
 >>
 >> Works fine for me in mintty 0.9.7.
 >
 > You're probably using man-msys, whereas Cesar is using man-mingw.
 > 'man-mingw' would see MSYS's pseudo terminal (pty) device, which
 > mintty is based on, as a pair of Windows pipes. Thus man-mingw thinks
 > its output is being piped somewhere instead of being displayed on a
 > terminal, which causes it to switch to non-interactive mode where it
 > just dumps the entire man page.
 >
 > See also http://code.google.com/p/mintty/issues/detail?id=56.
 >
 > Andy
 >
 >
 > ps: What's the difference between the two man versions, apart from the
 > one here?

You are right, with man-msys it works fine and I don't need to use
groff-msys. I can continue to use groff-mingw.
With rxvt it seems you'd need to use both man-msys and groff-msys.

The only difference I see is that man-msys additionally has manpath.exe
and manlint.

Regards,

-- 
Cesar

On 11 May 2011 12:21, Chris Sutcliffe wrote:
> On 10 May 2011 19:33, Cesar Romani wrote:
>> I'm using mintty 0.9.7, msys 1.0.17, less 4.4.1, groff 1.20.1,
>> man 1.6-mingw-beta-1 on Win XP.
>> If I issue a man command, say "man bash", the output isn't sent to the
>> pager, but the entire page will scroll on the screen without pausing.
>
> Works fine for me in mintty 0.9.7.

You're probably using man-msys, whereas Cesar is using man-mingw.
'man-mingw' would see MSYS's pseudo terminal (pty) device, which
mintty is based on, as a pair of Windows pipes. Thus man-mingw thinks
its output is being piped somewhere instead of being displayed on a
terminal, which causes it to switch to non-interactive mode where it
just dumps the entire man page.

See also http://code.google.com/p/mintty/issues/detail?id=56.

Andy


ps: What's the difference between the two man versions, apart from the one here?

On 10 May 2011 19:33, Cesar Romani wrote:
> I'm using mintty 0.9.7, msys 1.0.17, less 4.4.1, groff 1.20.1,
> man 1.6-mingw-beta-1 on Win XP.
> If I issue a man command, say "man bash", the output isn't sent to the
> pager, but the entire page will scroll on the screen without pausing.

Works fine for me in mintty 0.9.7.  What is your $TERM set to?

Chris

-- 
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d

I'm using mintty 0.9.7, msys 1.0.17, less 4.4.1, groff 1.20.1,
man 1.6-mingw-beta-1 on Win XP.
If I issue a man command, say "man bash", the output isn't sent to the
pager, but the entire page will scroll on the screen without pausing.

If I issue the man command on the cmd console, it works fine.

Many thanks in advance,

-- 
Cesar

I'm trying to build rsync 3.0.8 on msys 1.0.17, gcc 3.4.4, and I'm
getting the following linker error:

--------------------
...
gcc -std=gnu99 -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt
-Wno-unused-parameter  -o rsync.exe flist.o rsync.o generator.o
receiver.o cleanup.o sender.o exclude.o util.o main.o checksum.o match.o
syscall.o log.o backup.o options.o io.o compat.o hlink.o token.o
uidlist.o socket.o hashtable.o fileio.o batch.o clientname.o chmod.o
acls.o xattrs.o progress.o pipe.o params.o loadparm.o clientserver.o
access.o connection.o authenticate.o lib/wildmatch.o lib/compat.o
lib/snprintf.o lib/mdfour.o lib/md5.o lib/permstring.o lib/pool_alloc.o
lib/sysacls.o lib/sysxattrs.o  lib/inet_ntop.o lib/inet_pton.o
lib/getaddrinfo.o zlib/deflate.o zlib/inffast.o zlib/inflate.o
zlib/inftrees.o zlib/trees.o zlib/zutil.o zlib/adler32.o zlib/compress.o
zlib/crc32.o popt/findme.o  popt/popt.o  popt/poptconfig.o
popt/popthelp.o popt/poptparse.o
fu000001.o:(.idata$2+0xc): undefined reference to `_templib_a_iname'
nmth000000.o:(.idata$4+0x0): undefined reference to `__nm__h_errno'
collect2: ld returned 1 exit status
make: *** [rsync.exe] Error 1
--------------------

Many thanks in advance,

-- 
Cesar

I did some testing and found threads on the MINGW/MSYS mail lists that 
helped me figure out a fairly simple solution.  

All I needed to do was change the working directory for the current
process into the same format returned by $(cd "$BLDROOT"; pwd), 
which could be either an MSYS canonical or a mount rooted path. 

So for example, say the user set BLDROOT="C:\msys\1.0\user\joe\src" as
a system environment variable. Then the user opens a bash shell and cd's
to the src folder. 

The following bash code would work regardless of how the user got to the
src folder, some examples:

$ cd "C:\msys\1.0\home\joe"    # pwd would yield /mingw/msys/1.0/home/joe
$ cd "/c/msys/1.0/home/joe"    # pwd would yield /c/mingw/msys/1.0/home/joe
$ cd ~/src                     # pwd would yield /home/joe/src
$ cd /home/joe/src             # pwd would yield /home/joe/src

---- bash code snippet, lots of code omitted  ---------

if [[ $OSTYPE == msys ]]; then
    if (ls -d "$BLDROOT" 2>/dev/null); then
        BLDROOT=$(cd "$BLDROOT" && pwd  | tr '[:upper:]' '[:lower:]')
        cd `pwd -W`
    fi
fi

DIR1=$(cd ..; pwd) # could return either an MSYS canonical or a mount rooted path
DIR2=$(cd "$BLDROOT"; pwd) # if BLDROOT lives in MinGW or msys folder
                           # always returns a mount rooted path, else it 
                           # an MSYS canonical path

if [ "$DIR1" != "$DIR2" ]; then
   echo "$BLDROOT blah, blah blah..."
   exit 1
fi 

---- bash code snippet, lots of code omitted ---------