Guido Draheim wrote:
> The "b" is an ansi-C requirement, however there may be some systems
> that are simply not compliant. [...] I just
> found second hand information that some DEC ultrix libc did barf
> at "b".
I did a bit of web digging, and I found first hand information in a
tex package da
> From: Akim Demaille <[EMAIL PROTECTED]>
> User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands)
>
> But the question remains open :)
I certainly recall reports of hosts where fopen (..."wb") did not work.
However, I don't recall which hosts they were.
I briefly looked around the
--- Akim Demaille <[EMAIL PROTECTED]> wrote:
> > "Earnie" == Earnie Boyd <[EMAIL PROTECTED]> writes:
>
> Earnie> Lars, just to satisfy my curiosity please send me the output
> Earnie> of `cygcheck -s -r -v'.
>
> What's this?
It is a tool developed by the Cygwin team to report on the use
Peter Eisentraut wrote:
> Akim Demaille writes:
> > Does anybody know whether using fopen (foo, "wb") is portable?
> Extremely doubtful.
The "b" is an ansi-C requirement, however there may be some systems
that are simply not compliant. AFAICS these are quite old, somewhere
in the eighties or so -
On Nov 16, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> Does anybody know whether using fopen (foo, "wb") is portable?
I recall having read about it in ``The C Primer'', when I first
learned C back in 198x (for a small value of x).
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.uni
> "Peter" == Peter Eisentraut <[EMAIL PROTECTED]> writes:
Peter> * Do not print an end-of-line at all.
!!! Of course! Thanks!
But the question remains open :)
Akim Demaille writes:
> Does anybody know whether using fopen (foo, "wb") is portable?
Extremely doubtful.
In this particular case you can work around by using open() and write()
and define O_BINARY to be 0 if not defined already.
Other possible approaches:
* Focus on avoiding getting the \r
On 16-Nov-2000, Earnie Boyd <[EMAIL PROTECTED]> wrote:
| --- Akim Demaille <[EMAIL PROTECTED]> wrote:
|
| > Does anybody know whether using fopen (foo, "wb") is portable? Gary
| > uses a test for this, but I don't know if it's really needed. A grep
| > on the packages I have at hand show this:
> "Earnie" == Earnie Boyd <[EMAIL PROTECTED]> writes:
Earnie> Lars, just to satisfy my curiosity please send me the output
Earnie> of `cygcheck -s -r -v'.
What's this? I'm looking for all the possible uname and the like
which we could include in the config.log. Currently, you have:
This
--- Akim Demaille <[EMAIL PROTECTED]> wrote:
>
> | On Thu, Nov 16, 2000 at 12:51:05PM +0100, Akim Demaille wrote:
> | :
> | : | -[FILE *f = fopen ("conftestval", "w");
> | : | +[FILE *f = fopen ("conftestval", "wb");
> | :
> | : Portable?
> |
> | Not really my cup of tea, but (from fopen(3) on
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> Sorry about that - autoconf.m4f was missing, but warnings were
Lars> supressed in the testsuite... The testsuite seems to be running
Lars> ok now that that is taken care of (got some failures in
Lars> semantics).
Thanks for the logs!
| On Thu, Nov 16, 2000 at 12:51:05PM +0100, Akim Demaille wrote:
| :
| : | -[FILE *f = fopen ("conftestval", "w");
| : | +[FILE *f = fopen ("conftestval", "wb");
| :
| : Portable?
|
| Not really my cup of tea, but (from fopen(3) on Linux):
|
| # The mode string can also include the letter ``b
On Thu, Nov 16, 2000 at 01:26:40PM +0100, Lars J. Aas wrote:
: On Thu, Nov 16, 2000 at 01:00:02PM +0100, Akim Demaille wrote:
: : Is this the only failure of the test suite?
:
: You wish. The testsuite doesn't work on Cygwin, because everything
: (with a couple of exceptions) fails...
Sorry abo
On Thu, Nov 16, 2000 at 01:00:02PM +0100, Akim Demaille wrote:
: Is this the only failure of the test suite?
You wish. The testsuite doesn't work on Cygwin, because everything
(with a couple of exceptions) fails...
Lars J
On Thu, Nov 16, 2000 at 01:00:02PM +0100, Akim Demaille wrote:
: > "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
:
: Lars> : so how come we waited till today to discover this issue?
:
: Lars> Running configure on the w32 platform hasn't really been common,
: Lars> nor is it common yet eit
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> : so how come we waited till today to discover this issue?
Lars> Running configure on the w32 platform hasn't really been common,
Lars> nor is it common yet either...
Is this the only failure of the test suite?
On Thu, Nov 16, 2000 at 12:51:05PM +0100, Akim Demaille wrote:
:
: | I think I found it - checking now:
: |
: | Index: aclang.m4
: | ===
: | RCS file: /cvs/autoconf/aclang.m4,v
: | retrieving revision 1.89
: | diff -u -r1.89 aclang.
| I think I found it - checking now:
|
| Index: aclang.m4
| ===
| RCS file: /cvs/autoconf/aclang.m4,v
| retrieving revision 1.89
| diff -u -r1.89 aclang.m4
| --- aclang.m4 2000/11/14 11:06:37 1.89
| +++ aclang.m4 2000/11/16
On Thu, Nov 16, 2000 at 12:56:54PM +0100, Lars J. Aas wrote:
: -[FILE *f = fopen ("conftestval", "w");
: +[FILE *f = fopen ("conftestval", "wb");
Yep, this was the fix...
Lars J
On Thu, Nov 16, 2000 at 12:41:53PM +0100, Akim Demaille wrote:
: > "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
:
: Lars> I'm using AC_CHECK_SIZEOF on Cygwin and have found out that the
: Lars> `conftest' file contains a \r\n after the size. The \r
: Lars> character follows the variable
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> I'm using AC_CHECK_SIZEOF on Cygwin and have found out that the
Lars> `conftest' file contains a \r\n after the size. The \r
Lars> character follows the variable into config.status (the
Lars> undefs.sed scripts) and ruins the sed scrip
I'm using AC_CHECK_SIZEOF on Cygwin and have found out that the
`conftest' file contains a \r\n after the size. The \r character
follows the variable into config.status (the undefs.sed scripts)
and ruins the sed scripts that produces config-headers (and the
config-headers become empty, consequent
22 matches
Mail list logo
