RE: BugView updated.

RE: BugView updated.

[Sergey Okhapkin]

David Coe wrote:
> The principle of CYGWIN_NOTTY seem a good idea. Although of course it is
> possible to re-port back to gnu-win32 all those old unix apps (less,
> ncftp, micro emacs, emacs -nw, beav, elvis) it would be a shame to lose
> the ability to launch their existing native console-direct
> implementations from the same command window.

Re-porting to gnu-win32 seems to me the best solution - you're able to run 
direct-console applications in a console only, but re-ported - in a console 
(with the same functionality), in a telnet session, in Xterm window and via 
communication port/modem. What is better?-)

>
> Unless I'm doing something wrong though, CYGWIN_NOTTY is not doing quite
> the thing I would expect (at least on NT4). Setting it before launching
> bash is fine - I get a cygwin environment that allows console direct but
> not pseudo-tty. Setting it within bash, however, does not switch to
> allow launching of console direct apps; in fact, even things like ls no
> longer produce output!!

Bash started without CYGWIN_NOTTY creates control tty threads and redirects 
standard handles of a childs to a pipes, connected to ctty. But childs do 
not makes connection to ctty because CYGWIN_NOTTY is set. There is no way 
to fall back to notty mode. At least, for a now... The main troubles are in 
standard handles redirection.

>
> Have you also made some changes to the reporting and use of ownership?
> Ls -l now reports usernames rather than numerical IDs. There is, for

There was a bug in /etc/passwd reading code, but you had to see usernames 
with this bug. I never had such a problem.

> example, some impact (which I don't yet understand) on the operation of
> the command line in mc-4.0 which works fine (with a # prompt) using your
> cygwin.dll from 06 Jul but only works under an Administrator account
> using the 10 Jul dll. From a User account it gives (correctly) a $
> prompt but (incorrectly) will launch nothing from it ... just like with
> the unpatched B18 cygwin.dll.

Try to remove <cr>s from /etc/passwd. If it will not help, remove shell 
fields from /etc/passwd and set environment variable SHELL to /bin/sh.

> Anyway, it's all very exciting.

Thank You!

--
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia
Looking for a job

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: BugView updated.

[David Coe]

Sergey Okhapkin wrote:
> 
> Re-porting to gnu-win32 seems to me the best solution - you're able to run
> direct-console applications in a console only, but re-ported - in a console
> (with the same functionality), in a telnet session, in Xterm window and via
> communication port/modem. What is better?-)

It depends on whether the re-port can be done easily (and reliably);
tcsh and tclsh come to mind as not (yet) being available under gnu-win32
TMK. Also whether (without stable configuration management and more
general exercising of a central code/patch repository) you would dare
trust your life / business on the resulting apps; rcs, cvs and even tar
come to mind as apps I would currently prefer the distributed binaries.
 
> Try to remove <cr>s from /etc/passwd. If it will not help, remove shell
> fields from /etc/passwd and set environment variable SHELL to /bin/sh.

The first did the job. It seems as if mkpasswd and mkgroup write
<cr/lf>'s irrespective of the mount flag. Thanks!

One further point on rxvt - it seems to be only possible to run one
concurrent xterm session. Is this a function of not incrementing the
ttydev/ptydev numbers?

-- 
Dr David Coe			     \=\
58 Fairlawn Drive, East Grinstead     \=\   Tel +44 1342 326860
West Sussex, RH19 1NT, United Kingdom  \=\  Fax +44 1342 316019
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: BugView updated.

[Mumit Khan]

Sergey,

Thanks for all the great work you're putting into winsup, and putting up
the patched cygwin DLL and libcygwin.a!

The only caveat is that I need to have a patched source tree (for various 
reasons, the least of which is that I never work on Win32 box, rather use 
linux and have some local modifications), I still would love to get a 
complete diff since b18 release.

I hand patched most of your patches available from your site, and looks
like the only piece I'm missing is the one that add 'rusage' handling.
Hopefully someone on the mailing list already has this patch?

Anybody out there managed to create a patch with respect to b18? Don't
tell me I'm the only who builds everything from source ;-?

Regards
Mumit -- khan@xraylith.wisc.edu
http://www.xraylith.wisc.edu/~khan/
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: BugView updated.

[Chris Faylor]

In article < 9707140307.AA18207@modi.xraylith.wisc.edu >,
Mumit Khan  <khan@xraylith.wisc.edu> wrote:
>Sergey,
>
>Thanks for all the great work you're putting into winsup, and putting up
>the patched cygwin DLL and libcygwin.a!
>
>The only caveat is that I need to have a patched source tree (for various 
>reasons, the least of which is that I never work on Win32 box, rather use 
>linux and have some local modifications), I still would love to get a 
>complete diff since b18 release.
>
>I hand patched most of your patches available from your site, and looks
>like the only piece I'm missing is the one that add 'rusage' handling.
>Hopefully someone on the mailing list already has this patch?
>
>Anybody out there managed to create a patch with respect to b18? Don't
>tell me I'm the only who builds everything from source ;-?

No.  I build from source, too, but I think that Sergey is constrained by
the fact that some of the code is actually part of the Cygnus development
tree and Cygnus doesn't want to release their stuff yet.
-- 
http://www.bbc.com/	cgf@bbc.com			"Strange how unreal
VMS=>UNIX Solutions	Boston Business Computing	 the real can be."
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: BugView updated.

[Mumit Khan]

cgf@bbc.com (Chris Faylor) writes:
> No.  I build from source, too, but I think that Sergey is constrained by
> the fact that some of the code is actually part of the Cygnus development
> tree and Cygnus doesn't want to release their stuff yet.
> -- 

Too bad. If this is true, that pretty much guarantees that I wouldn't be 
able to use these promising fixes to winsup till the next beta release. 

Any comment from the Cygnus folks? Any chance of a alpha snapshot?

Mumit
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Beta 19 status

[Geoffrey Noer]

> Any comment from the Cygnus folks? Any chance of a alpha snapshot?

I'm especially time contrainted right now so the beta 19 release will be
the next thing to be done on my end.  I am working on it as I write but it
may be several weeks until it's ready for release.  There are quite a few
mods to test, both inside winsup and out:

* new winsup pty support
* much better signals/exceptions support
* lots and lots of misc. winsup fixes although I'm sure plenty of bugs
	remain
* PE format change -- better compatibility with MS compiler/linker
* better g++ template support (g++ had some problems in beta 18)
* new resource compiler
* switch to bfd-based assembler
* dlltool fixes
* gdb GUI fixes

The timeframe depends mostly on how time consuming the other stuff I'm
doing for Cygnus ends up being and how many problems I run into during
testing.  My current plan is to have it done by mid-August or earlier but
that may slip.  I may well make an alpha snapshot first but this won't be
until shortly before the release.

Cheers,

Geoffrey Noer
noer@cygnus.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Beta 19 status

[Tim Iverson]

I just noticed the gdb GUI comment.  Does this currently work for remote
debug sessions over a serial line?  Also, how GUI is it?  Some folks here
have become quite spoiled by the nice GUIs presented by Microsoft's and
Boarlund's debuggers -- is it as GUI as those?

Thanks,

- Tim

\f
+----------------
| From: Geoffrey Noer <noer@cygnus.com>
| Subject: Beta 19 status
| To: khan@xraylith.wisc.edu (Mumit Khan)
| Date: Tue, 15 Jul 1997 20:17:11 -0700 (PDT)
| Cc: cgf@bbc.com, gnu-win32@cygnus.com, noer@cygnus.com
| 
| I'm especially time constrainted right now so the beta 19 release will be
| may be several weeks until it's ready for release.  There are quite a few
...
| * gdb GUI fixes
...
| Geoffrey Noer
| noer@cygnus.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Beta 19 status

[Luke Diamand]

Hi!


Tim Iverson writes:
 > I just noticed the gdb GUI comment.  Does this currently work for remote
 > debug sessions over a serial line?  Also, how GUI is it?  Some folks here
 > have become quite spoiled by the nice GUIs presented by Microsoft's and
 > Boarlund's debuggers -- is it as GUI as those?

Tcp/ip works fine, but the serial line seemed to be broken on Win32
for the target I was using (remote-rdp), although it's ok on linux.

How GUI is it, you ask?

For a first release it's pretty good. It puts up the source code and 
higlights the line you're at, you can double-click to set/clear 
breakpoints and examine data.

The most irritating feature is that the GUI freezes while waiting for
the target - so you can't interrupt it.

It is not (IMO) as visually appealing as Microsoft's GUI - but as is
ever the case, you do get a grown-up debugger - not the mickey-mouse
thing that Microsoft fob off on us.

Cheers!
Luke Diamand

-- 
Advanced Telecommunications Modules Ltd
Cambridge
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: BugView updated.

[Mike Bernson]

Mumit Khan wrote:
> 
> Sergey,
> 
> Thanks for all the great work you're putting into winsup, and putting up
> the patched cygwin DLL and libcygwin.a!
> 
> The only caveat is that I need to have a patched source tree (for various
> reasons, the least of which is that I never work on Win32 box, rather use
> linux and have some local modifications), I still would love to get a
> complete diff since b18 release.
> 
> I hand patched most of your patches available from your site, and looks
> like the only piece I'm missing is the one that add 'rusage' handling.
> Hopefully someone on the mailing list already has this patch?
> 
> Anybody out there managed to create a patch with respect to b18? Don't
> tell me I'm the only who builds everything from source ;-?
> 
> Regards
> Mumit -- khan@xraylith.wisc.edu
> http://www.xraylith.wisc.edu/~khan/
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".
If you find a place place let me known......

I am glad to see that I am not the only one that is missing rusage
fill function.

I would like to be able to check all my patches up to date.

I will be will to make a stab at this but i need a few copies of patched
version of winsup files.

I can create a inbound ftp area on my machine here. But only a have
a ISDN 64k line so anonymous ftp is out. I think that my ISP will
give me space < 5meg on his machine for WEB pages.

I could check into this if enough people want the sources. Also
everyone that help in keeping the source in sync would be granted
access.

I would like to see a way to have better controlled way to handle 
fixes that sergey is will (nice) to give us. Since Cygnus is not
keep a current sanpshot of the gnutools I would like to see one 
created.

This is not to say I would want Sergey to spend time keeping a 
snapshot instead of fix stuff. The snapshot could be handle by
some user. Again I would be will to try to start this up.

I would like to keep a patch file to go from Clean b18 release to
what the current snapshot. Also I would like to keep patch files to
go from snapshot to snap shot.

There a number of issuse that need to be worked out.

If enough people want to see this happen I can create a mailing
list to talk about getting things setup. I would like to see this
as a seprate list from gun-win32 so that we do not bother user that
do not care about this and to get thing going faster. (smaller list
work faster)\x18

I last note. I do not care about assign copyright to Me or cygnus. I
just do not want to deal with copyright that will not allow use to 
use the code or restrict it more then cygnus has.
\x18
\x18\x18
\x18
\x18\x03
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: BugView updated.

[Mumit Khan]

Mike Bernson <mike@mbsun.mlb.org> writes:
> 
> I would like to be able to check all my patches up to date.
> 
> I will be will to make a stab at this but i need a few copies of patched
> version of winsup files.

I finally took the plunge and patched up winsup with all of Sergey's
fixes. It built ok on my linux box, but haven't had to chance to test
it yet. I'll keep you posted. 

If it does work, I'll put it up for ftp as a diff to b18 pristine. 

So far, the only missing piece (after Sergey found his rusage stuff) are
some references to timezone related stuff (eg., tzname). I'll work around
it for now.

Mumit
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: BugView updated.

[Hmmmz]

On Tue, 15 Jul 1997, Mike Bernson wrote:

> I would like to see a way to have better controlled way to handle 
> fixes that sergey is will (nice) to give us. Since Cygnus is not
> keep a current sanpshot of the gnutools I would like to see one 
> created.

I just got around to reading my email (Solaris is not an easy OS to live
with *curestowhomeverworksatsun*), I don't know if anyone here has enough
bandwidth or resources to set one up, but what about setting up a
cvs/cvsup/rcs server to hold b18 with all its patches? I know that cvsup
works nicely for the FreeBSD kernel sources, but that's a different
enviroment.  Just a suggestion.

- alex

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Beta 19 status

[Geoffrey Noer]

We just imported bash 2.01 into our local sources so it will be included
in beta 19.  I haven't seen any problems with it yet and having working
job control is great.

I've appended the beginnings of the history doc with changes since b18.
It isn't all there yet, but for those of you who are curious...  Also
my current best guess is that beta 19 will be out in September.

A fair amount of work is being done on the Win32 side of things right now
(converting gcc to default to not linking in the cygwin.dll, handling
.exe extensions better during the build process, etc...).  So beta 19
will happen as soon as everything settles down a little.

-- 
Geoffrey Noer
noer@cygnus.com

--------------------------------------

@item Release Beta 19 (Probably September 1997)

This is a major release.  The new cygwin.dll is still
backwards-compatible with previously linked applications but
contains significant changes.

The PE format definition now matches Microsoft's more closely.
This should allow better interoperability with other vendors'
development tools.  This change invalidates all previously
built object (.o) and static library (.a) files so be sure to
delete/rebuild old .o and .a files you are using!

@subsection Changes in specific tools:

We have upgraded some of the utilities.  GNU-Win32 now includes
bash 2.01, textutils 1.22, and gawk 3.0.3.  Bash under Cygwin32 now
includes working job control among other improvements.

Ian Lance Taylor wrote a resource compiler called "windres".
It can be used to compile windows resources from a textual rc file
into a COFF file.  The sources for it are part of the binutils
package.

@subsection Changes in the Cygwin32 API (cygwin.dll):

Old symlinks are also invalidated by this release.  The "system"
attribute is now used to mark symlinks which significantly speeds
up fstat and other file related calls.  Either recreate old ones or
set their "system" attribute flag so they will be recognized properly.

The following is now supported:

* pseudo-ttys

The following calls have been added:

* ptsname, grantpt, unlockpt
* login, logout, ttyslot
* wait3, wait4
* setitimer, getitimer
* cfg(s)eti(o)speed
* initgroups (stub), getgroups
* sexecve, sexecl, sexecle, sexeclp, sexeclpe, sexecv, sexecp, sexecvpe
* pause
* getpgid, killpg
* strlwr, strupr
* ftime
* fpathconf

The bsearch call has been rewritten.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

RE: Beta 19 status

[Sergey Okhapkin]

Geoffrey Noer wrote:
> .exe extensions better during the build process, etc...).  So beta 19
> will happen as soon as everything settles down a little.

Signals handling is incompatible with Windows95 :-( The only way I know for 
a now to run cygnus tools stable on W95 is to disable all the signal (and 
job control) support. Any ideas/suggestions?

window.cc:

void
window_init ()
{
  DWORD tid;
  HANDLE hThread;

  u->self->hwnd = NULL;
> if (get_os_type () == win95)
>   return;
  window_started = CreateEvent (NULL, TRUE, FALSE, NULL);
  hThread = CreateThread (NULL, 0, (LPTHREAD_START_ROUTINE) Winmain,
							NULL, 0, &tid);

Sorry, I have no ideas how to avoid random crashes with the diagnostics 
like "sh.exe causes the general protection error in module USER.EXE"... 
sigh :-)

--
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia
Looking for a job

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Beta 19 status

[Geoffrey Noer]

Greetings,

I guess I should know better even hinting at dates before beta 19 is
completely finished.  :-(  You should know that I am delaying the
release for a variety of reasons -- in a nutshell, some things have not
progressed enough and other things have progressed too much such that it
will take more time to get a new gnu-win32 to a releasable stage.  That's
life I guess.

That said, the Cygwin32 library (cygwin.dll) has made a lot of progress
since the last release as those of you using Sergey's cygwin.dlls have
seen.  For now, my current plan is to make a new cygwin.dll and its sources
available soon that can be added to beta 18 to make beta 18.5.

Finally, just a heads up so you know we haven't been slacking off :-).
Cygnus has just announced a new IDE called Cygnus Foundry (see the link
from the main Cygnus Web page http://www.cygnus.com for more information).
I will let you all know how this will play with future gnu-win32 beta
releases when I can...

Best regards,

Geoffrey Noer
noer@cygnus.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Beta 19 status

[Bartlee A. Anderson]

Dear Geoffrey,
Any chance for a b19 for Christmas?
Thanks,
	Bart

Geoffrey Noer wrote:
> 
> Greetings,
> 
> I guess I should know better even hinting at dates before beta 19 is
> completely finished.  :-(  You should know that I am delaying the
> release for a variety of reasons -- in a nutshell, some things have not
> progressed enough and other things have progressed too much such that it
> will take more time to get a new gnu-win32 to a releasable stage.  That's
> life I guess.
> 
> That said, the Cygwin32 library (cygwin.dll) has made a lot of progress
> since the last release as those of you using Sergey's cygwin.dlls have
> seen.  For now, my current plan is to make a new cygwin.dll and its sources
> available soon that can be added to beta 18 to make beta 18.5.
> 
> Finally, just a heads up so you know we haven't been slacking off :-).
> Cygnus has just announced a new IDE called Cygnus Foundry (see the link
> from the main Cygnus Web page http://www.cygnus.com for more information).
> I will let you all know how this will play with future gnu-win32 beta
> releases when I can...
> 
> Best regards,
> 
> Geoffrey Noer
> noer@cygnus.com
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".

-- 
Bartlee A. Anderson     System Test (Interfaces-Tools-Automation-ISDN)
Rockwell International                    Electronic Commerce Division
300 Bauman Ct.                                banders@ecd.rockwell.com
MS 933-605      Opinions my own, not Rockwell's   VOICE (630) 227-8975
Wood Dale, IL 60191                               FAX   (630) 227-9771
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Beta 19 status

[Geoffrey Noer]

Bartlee A. Anderson wrote:
> 
> Any chance for a b19 for Christmas?

Soon, I hope, but it's vacation time for me now until the end of the
year.  I really will let people know when I have a hard date to announce.
The "Coolview" dll from Sergey (see project web pages for link) has a lot
of the improvements to Cygwin32 that will be in b19 so that's worth
checking out for now.

I can say that the longer it takes for it to come out, the higher quality
the release will be but that might not be much consolation.  :-)

Happy holidays all!

Geoffrey Noer
noer@cygnus.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".