From: Sebastien Barre <Sebastien.Barre@utc.fr>
To: Charles Wilson <cwilson@ee.gatech.edu>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Compiling Perl under b20.1
Date: Mon, 08 Mar 1999 05:43:00 -0000 [thread overview]
Message-ID: <4.1.19990308113609.016b8c00@mail.club-internet.fr> (raw)
In-Reply-To: < 36E37A18.A15F8524@ece.gatech.edu >
At 02:19 08/03/99 -0500, Charles Wilson wrote:
>WOW! You haven't been working on this all day, have you?
Both of us :)
>Let me summarize, and see if I've got this straight:
>(1) according to Earnie Boyd (but contradicted by Pierre Humblet)
[...]
>all of your tests were either CYGWIN=binmode or
>CYGWIN=________, not CYGWIN=nobinmode, you really weren't changing anything
>here.
Sadly. I should have used nobinmode. I'll try.
>Okay, digging into the stat.t code: You failed tests 18-20 and 26 in stat.t.
>Tests 18-20 are testing (readable by owner?) (writeable by owner?) and
(executable by
>owner) after doing a chmod 0700. I can't remember if I was building perl
>under the Administrator account or under my normal NT user account. But,
the "everything
>created by a member of the Administrators group belongs to the group, not
>the user" NTism may be the culprit here.
Yes, seems to me too, but I thought 'ntea' could solve this (see other
email "'ntea' CHECK please).
>My conclusions are the same as yours:
> (1) Earnie is right ==> binmode has no effect
> (2) binary mounted / text mounted don't affect the build, only the runtime
>behavior and tests. Why is another question.
OK for me at this time (+ a free headache).
______________________________________________________________
Sebastien Barre http://www.hds.utc.fr/~barre/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Sebastien Barre <Sebastien.Barre@utc.fr>
To: Charles Wilson <cwilson@ee.gatech.edu>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Compiling Perl under b20.1
Date: Wed, 31 Mar 1999 19:45:00 -0000 [thread overview]
Message-ID: <4.1.19990308113609.016b8c00@mail.club-internet.fr> (raw)
Message-ID: <19990331194500.-AgA5yUd9bv20CQi51tp29aC0crxXlwHyjfyg4Yu8SE@z> (raw)
In-Reply-To: <36E37A18.A15F8524@ece.gatech.edu>
At 02:19 08/03/99 -0500, Charles Wilson wrote:
>WOW! You haven't been working on this all day, have you?
Both of us :)
>Let me summarize, and see if I've got this straight:
>(1) according to Earnie Boyd (but contradicted by Pierre Humblet)
[...]
>all of your tests were either CYGWIN=binmode or
>CYGWIN=________, not CYGWIN=nobinmode, you really weren't changing anything
>here.
Sadly. I should have used nobinmode. I'll try.
>Okay, digging into the stat.t code: You failed tests 18-20 and 26 in stat.t.
>Tests 18-20 are testing (readable by owner?) (writeable by owner?) and
(executable by
>owner) after doing a chmod 0700. I can't remember if I was building perl
>under the Administrator account or under my normal NT user account. But,
the "everything
>created by a member of the Administrators group belongs to the group, not
>the user" NTism may be the culprit here.
Yes, seems to me too, but I thought 'ntea' could solve this (see other
email "'ntea' CHECK please).
>My conclusions are the same as yours:
> (1) Earnie is right ==> binmode has no effect
> (2) binary mounted / text mounted don't affect the build, only the runtime
>behavior and tests. Why is another question.
OK for me at this time (+ a free headache).
______________________________________________________________
Sebastien Barre http://www.hds.utc.fr/~barre/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-03-08 5:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-06 10:41 Earnie Boyd
1999-03-06 12:07 ` Charles Wilson
[not found] ` < 36E18AF6.A967D7DA@ece.gatech.edu >
1999-03-07 15:33 ` Sebastien Barre
1999-03-07 23:19 ` Charles Wilson
[not found] ` < 36E37A18.A15F8524@ece.gatech.edu >
1999-03-08 5:43 ` Sebastien Barre [this message]
1999-03-31 19:45 ` Sebastien Barre
1999-03-08 5:43 ` 'ntea' CHECK please (was Re: Compiling Perl) Sebastien Barre
1999-03-31 19:45 ` Sebastien Barre
1999-03-31 19:45 ` Compiling Perl under b20.1 Charles Wilson
1999-03-08 0:07 ` Charles Wilson
[not found] ` < 36E38547.482A019A@ece.gatech.edu >
1999-03-08 5:43 ` Sebastien Barre
1999-03-31 19:45 ` Sebastien Barre
1999-03-31 19:45 ` Charles Wilson
1999-03-31 19:45 ` Sebastien Barre
1999-03-31 19:45 ` Charles Wilson
1999-03-31 19:45 ` Earnie Boyd
-- strict thread matches above, loose matches on Subject: below --
1999-03-07 18:53 Earnie Boyd
1999-03-31 19:45 ` Earnie Boyd
1999-03-05 6:22 Steven Zeil
1999-03-31 19:45 ` Steven Zeil
1999-03-04 18:06 Allan Peda
[not found] ` < 36DF49C5.BDE486B0@interport.net >
1999-03-05 8:06 ` Sebastien Barre
1999-03-05 13:13 ` Charles Wilson
[not found] ` < 36E048F5.9B384A50@ece.gatech.edu >
1999-03-06 2:49 ` Sebastien Barre
1999-03-06 10:27 ` Charles Wilson
[not found] ` < 36E1739A.BEC6F38C@ece.gatech.edu >
1999-03-07 15:33 ` Sebastien Barre
1999-03-07 22:26 ` Charles Wilson
1999-03-31 19:45 ` Charles Wilson
1999-03-31 19:45 ` Sebastien Barre
1999-03-31 19:45 ` Charles Wilson
1999-03-31 19:45 ` Sebastien Barre
1999-03-31 19:45 ` Charles Wilson
1999-03-31 19:45 ` Sebastien Barre
1999-03-31 19:45 ` Allan Peda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4.1.19990308113609.016b8c00@mail.club-internet.fr \
--to=sebastien.barre@utc.fr \
--cc=cwilson@ee.gatech.edu \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).