[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Groff] need help resolving groff error
From: |
Ralph Corderoy |
Subject: |
Re: [Groff] need help resolving groff error |
Date: |
Thu, 10 Oct 2013 22:58:46 +0100 |
Hi Keith,
> > It looks like a mismatch between the mode used to open the temporary
> > file and the mode that's then used to map a FILE* onto it with
> > fdopen.
...
> Notwithstanding that we probably do really want O_BINARY here, my
> tests on a Win7 Home Premium VM
Now that charlie has confirmed that flipping the single O_BINARY bit on
a single call to open() has fixed the initial problem, I agree it should
be changed in the source. Debian Code Search shows lots of conditional
`#define O_BINARY 0' so the flag can be used if it doesn't exist.
Cheers, Ralph.
- [Groff] need help resolving groff error, Charlie Van Dien, 2013/10/05
- Re: [Groff] need help resolving groff error, Werner LEMBERG, 2013/10/09
- Re: [Groff] need help resolving groff error, Keith Marshall, 2013/10/09
- Re: [Groff] need help resolving groff error, Werner LEMBERG, 2013/10/09
- Re: [Groff] need help resolving groff error, Charlie Van Dien, 2013/10/09
- Re: [Groff] need help resolving groff error, Ralph Corderoy, 2013/10/10
- Re: [Groff] need help resolving groff error, Charlie Van Dien, 2013/10/10
- Re: [Groff] need help resolving groff error, Ralph Corderoy, 2013/10/10
- Re: [Groff] need help resolving groff error, Ralph Corderoy, 2013/10/11
- Re: [Groff] need help resolving groff error, Charlie Van Dien, 2013/10/13
- Re: [Groff] need help resolving groff error, Charlie Van Dien, 2013/10/10