Re: Need help. Latest snapshot may be next cygwin net release.

Re: Need help. Latest snapshot may be next cygwin net release.

[Norbert Schulze]

I did not test the new cygwin1-20000524.dll but cygwin1-20000525.dll
is ok now.

Thanks
  Norbert


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Need help. Latest snapshot may be next cygwin net release.

[Vadim Egorov]

Chris Faylor <cgf@cygnus.com> writes:

> You're not providing any context.  Is this something new since 1.1.0?
> 
I don't know exactly when it happened. It worked some time ago 
(with snapshots about 1.1.0 ) - last time I was rebuilding libstdc++. 
latest libstdc++.a i found in my disk is dated May 10 - as I remember
then there was no problems.

> cgf
> 
> On Fri, May 26, 2000 at 10:11:15AM +0400, Vadim Egorov wrote:
> >Sorry, the message body seems was lost on the way.
> >
> >Chris Faylor <cgf@cygnus.com> writes:
> >
> >> I would appreciate it if any adventurous souls would try out the
> >> latest cygwin snapshot by downloading this:
> >
> >libstdc++-v3 configure hangs again. An old problem with signals.
> >This is a  piece of code which hangs and  a strace log.
> >
> >#include <unistd.h>
> >#include <signal.h>
> >#include <setjmp.h>
> >
> >static jmp_buf	env;
> >int signo = SIGSEGV;
> >
> >static void sig_handler(int sig)
> >{
> >    static sigset_t x;
> >    signal (sig, sig_handler);
> >    sigemptyset (&x);
> >    sigprocmask(SIG_SETMASK, &x, NULL);
> >
> >    longjmp(env, 1);
> >}
> >
> >int main(int argc, char * * argv)
> >{
> >    if (setjmp(env) == 0 ) 
> >    {
> >        signal(signo, sig_handler);
> >        *(char*)0 = 1;
> >    }
> >    return 0;
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 

-- 
Regards,
Vadim Egorov 


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Need help. Latest snapshot may be next cygwin net release.

[Chris Faylor]

Nevermind.  I found it.

cgf

On Fri, May 26, 2000 at 02:13:13AM -0400, Chris Faylor wrote:
>You're not providing any context.  Is this something new since 1.1.0?
>
>cgf
>
>On Fri, May 26, 2000 at 10:11:15AM +0400, Vadim Egorov wrote:
>>Sorry, the message body seems was lost on the way.
>>
>>Chris Faylor <cgf@cygnus.com> writes:
>>
>>> I would appreciate it if any adventurous souls would try out the
>>> latest cygwin snapshot by downloading this:
>>
>>libstdc++-v3 configure hangs again. An old problem with signals.
>>This is a  piece of code which hangs and  a strace log.
>>
>>#include <unistd.h>
>>#include <signal.h>
>>#include <setjmp.h>
>>
>>static jmp_buf	env;
>>int signo = SIGSEGV;
>>
>>static void sig_handler(int sig)
>>{
>>    static sigset_t x;
>>    signal (sig, sig_handler);
>>    sigemptyset (&x);
>>    sigprocmask(SIG_SETMASK, &x, NULL);
>>
>>    longjmp(env, 1);
>>}
>>
>>int main(int argc, char * * argv)
>>{
>>    if (setjmp(env) == 0 ) 
>>    {
>>        signal(signo, sig_handler);
>>        *(char*)0 = 1;
>>    }
>>    return 0;

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Need help. Latest snapshot may be next cygwin net release.

[Chris Faylor]

You're not providing any context.  Is this something new since 1.1.0?

cgf

On Fri, May 26, 2000 at 10:11:15AM +0400, Vadim Egorov wrote:
>Sorry, the message body seems was lost on the way.
>
>Chris Faylor <cgf@cygnus.com> writes:
>
>> I would appreciate it if any adventurous souls would try out the
>> latest cygwin snapshot by downloading this:
>
>libstdc++-v3 configure hangs again. An old problem with signals.
>This is a  piece of code which hangs and  a strace log.
>
>#include <unistd.h>
>#include <signal.h>
>#include <setjmp.h>
>
>static jmp_buf	env;
>int signo = SIGSEGV;
>
>static void sig_handler(int sig)
>{
>    static sigset_t x;
>    signal (sig, sig_handler);
>    sigemptyset (&x);
>    sigprocmask(SIG_SETMASK, &x, NULL);
>
>    longjmp(env, 1);
>}
>
>int main(int argc, char * * argv)
>{
>    if (setjmp(env) == 0 ) 
>    {
>        signal(signo, sig_handler);
>        *(char*)0 = 1;
>    }
>    return 0;

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Need help. Latest snapshot may be next cygwin net release.

[Vadim Egorov]

Sorry, the message body seems was lost on the way.

Chris Faylor <cgf@cygnus.com> writes:

> I would appreciate it if any adventurous souls would try out the
> latest cygwin snapshot by downloading this:

libstdc++-v3 configure hangs again. An old problem with signals.
This is a  piece of code which hangs and  a strace log.

#include <unistd.h>
#include <signal.h>
#include <setjmp.h>

static jmp_buf	env;
int signo = SIGSEGV;

static void sig_handler(int sig)
{
    static sigset_t x;
    signal (sig, sig_handler);
    sigemptyset (&x);
    sigprocmask(SIG_SETMASK, &x, NULL);

    longjmp(env, 1);
}

int main(int argc, char * * argv)
{
    if (setjmp(env) == 0 ) 
    {
        signal(signo, sig_handler);
        *(char*)0 = 1;
    }
    return 0;
}
-- 
Regards,
Vadim Egorov 


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Need help. Latest snapshot may be next cygwin net release.

[Vadim Egorov]

[-- Attachment #1: Type: text/plain, Size: 117 bytes --]

sigtest.strace.gz
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


[-- Attachment #2: sigtest.strace.gz --]
[-- Type: application/x-gzip, Size: 6095 bytes --]

Re: Need help. Latest snapshot may be next cygwin net release.

[John A. Turner]

"John A. Turner" wrote:

> unfortunately, it does not fix the problems I was seeing - I still have
> to go back to the 5/2 snapshot to get things to work
> 
> two manifestations of the problems I see are that cvs keeps thinking I
> need to log in, and makefiles that work with 5/2 and previous suddenly
> do stuff like:
> 
> ~/LANL/JTpk/990816/JTpack$ gmake distclean
> : No such file or directoryls
> '.  Stop.ile_diste to make target `../Makeutils
> 
> my mount table looks (in part) like this:
> 
> ~$ mount
> Device              Directory           Type         Flags
> E:\Local\cygwin\bin  /usr/bin            user         textmode
> E:\Local\cygwin\lib  /usr/lib            user         textmode
> E:\Local\cygwin     /                   user         textmode
> E:\Home             /home               user         textmode
> C:                  /win2k              user         textmode
> 
> I tried with /, /usr/bin, and /usr/lib as binmode just for the heck of
> it, and it didn't change anything

ok, changing to the son of snapshot 5/24 did fix both these problems

somewhat interestingly, the cvs problem was *only* fixed if I mounted
/, /usr/bin, and /usr/lib in textmode rather than binmode - my home (and
hence my .cvspass file) are in /home/turner, which is texmode, but the
sandbox in question is in /usr/local - I don't understand the implications
of this, but it doesn't matter too much to me, since I'd rather stay with
textmode mounts anywat - but I thought I'd mention it

thanks,

-John Turner

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Need help. Latest snapshot may be next cygwin net release.

[Chris Faylor]

On Thu, May 25, 2000 at 10:32:16PM -0400, John A. Turner wrote:
>unfortunately, it does not fix the problems I was seeing - I still have
>to go back to the 5/2 snapshot to get things to work

When did you download the snapshot.  DJ indicated that he'd updated it
later in the day today.

Please try this with the latest snapshot.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Need help. Latest snapshot may be next cygwin net release.

[John A. Turner]

Chris Faylor wrote:
> 
> I would appreciate it if any adventurous souls would try out the
> latest cygwin snapshot by downloading this:
> 
> ftp://sourceware.cygnus.com/pub/cygwin/snapshots/cygwin1-20000524.dll.gz

[snip]

> This snapshot should fix all of the "\r\n" line ending problems that
> were in cygwin-1.1.1.  It should also fix problems with rxvt on Windows
> 95.
> 
> Just to be clear, fixing "\r\n" line endings means that if you are in a
> directory that has been mounted using the "-t" option then makefiles
> should work as they used to in cygwin B20 and cygwin 1.1.0.  This DLL
> fixes problems with text mode reads.

[snip]

unfortunately, it does not fix the problems I was seeing - I still have
to go back to the 5/2 snapshot to get things to work

two manifestations of the problems I see are that cvs keeps thinking I
need to log in, and makefiles that work with 5/2 and previous suddenly
do stuff like:

~/LANL/JTpk/990816/JTpack$ gmake distclean
: No such file or directoryls
'.  Stop.ile_diste to make target `../Makeutils

my mount table looks (in part) like this:

~$ mount
Device              Directory           Type         Flags
E:\Local\cygwin\bin  /usr/bin            user         textmode
E:\Local\cygwin\lib  /usr/lib            user         textmode
E:\Local\cygwin     /                   user         textmode
E:\Home             /home               user         textmode
C:                  /win2k              user         textmode

I tried with /, /usr/bin, and /usr/lib as binmode just for the heck of
it, and it didn't change anything

let me know if there's anything you'd like me to try...

-John Turner

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Need help. Latest snapshot may be next cygwin net release.

[Rick Rankin]

So far, this snapshot has cleaned up the issues I was seeing.

Many thanks!

Rick
--
Rick Rankin
rick_rankin@yahoo.com

--- Chris Faylor <cgf@cygnus.com> wrote:
> I would appreciate it if any adventurous souls would try out the
> latest cygwin snapshot by downloading this:
> 
> ftp://sourceware.cygnus.com/pub/cygwin/snapshots/cygwin1-20000524.dll.gz
> 
> This file should be copied to your /bin directory.  There should also
> be a cygwin1.dll in this directory.  If there isn't, you're in the wrong
> directory.
> 
> Once it's downloaded please:
> 
>     1) Terminate all running cygwin applications
> 
>     2) In the command shell, cd to the MS-DOS equivalent of your /bin
>        directory, e.g.,
> 	d:
> 	cd cygwin\bin
> 
>     3) gzip -d cygwin1-20000524.dll.gz
> 
>     4) copy cygwin1.dll cygwin1.dll.safe
> 
>     5) copy cygwin1-20000524.dll cygwin1.dll
> 
>     6) Check any failing applications for correct operation.
> 
> This snapshot should fix all of the "\r\n" line ending problems that
> were in cygwin-1.1.1.  It should also fix problems with rxvt on Windows
> 95.
> 
> Just to be clear, fixing "\r\n" line endings means that if you are in a
> directory that has been mounted using the "-t" option then makefiles
> should work as they used to in cygwin B20 and cygwin 1.1.0.  This DLL
> fixes problems with text mode reads.
> 
> This DLL does not change anything about the way that the setup.exe
> program previously mounted your root directory.  setup.exe mounts the
> root directory as "binary".  If this is not acceptable you still have
> to mount any directory containing files with MS-DOS style line endings
> with the "-t" option.
> 
> So, if you have a directory called d:\src and it has all of your
> sources in it, and they all have the carriage-return/line-feed endings
> you have to:
> 
> 	mount -t -f d:\src /src
> 
> This will cause files in d:\src and any subdirectories of d:\src to be
> interpreted in text mode.
> 
> If you do try out this DLL, I would appreciate hearing success or failure
> reports here in the cygwin@sourceware.cygnus.com mailing list.  Do not
> send them to me personally.
> 
> If everything seems to be working well, I'll release a new version of
> the DLL over the weekend.
> 
> Christopher Faylor
> Cygwin Engineering Manager (and developer)
> Cygnus Solutions, a Red Hat company
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 


__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Need help. Latest snapshot may be next cygwin net release.

[Gary R. Van Sickle]

I see no change here from the circa 5/3 snapshot.  Example: autoconf no
longer works properly, all I get (after a successful aclocal and
automake -a) is 'NONE:0: m4: Expecting line feed in frozen file', where
everything worked fine before.  I also see the same problems reported by
Norbert Schulze.  Something's definitely out of whack still...

That said, the overall quality and usefulness of Cygwin never ceases to
amaze me.  A major 'thank you' to all who have contributed to the project.

Gary R. Van Sickle <tiberius@braemarinc.com>
Braemar Inc.
11481 Rupp Dr.
Burnsville, MN 55337


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Need help. Latest snapshot may be next cygwin net release.

[Norbert Schulze]

Chris Faylor wrote:
> I would appreciate it if any adventurous souls would try out the
> latest cygwin snapshot by downloading this:

I tried to build make-3.79

tar -xvzf make-3.79.tar.gz
cd make-3.79
./configure

When I use cygwin1-20000524.dll configure aborts with:

checking for location of SCCS get command... get
checking if system libc has GNU glob... no; using local copy
updating cache ./config.cache
creating ./config.status
sed: file conftest.hdr line 1: Unknown option to 's'
creating build.sh
sed: file conftest.s1 line 1: Extra characters after command
creating Makefile
sed: file conftest.s1 line 1: Extra characters after command
creating glob/Makefile
sed: file conftest.s1 line 1: Extra characters after command
creating i18n/Makefile
sed: file conftest.s1 line 1: Extra characters after command
creating config.h
sed: file conftest.frag line 1: Unknown option to 's'


When I use cygwin1-20000502.dll all went well.

Norbert


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Need help. Latest snapshot may be next cygwin net release.

[Jason Tishler]

Chris,

Chris Faylor wrote:
> I would appreciate it if any adventurous souls would try out the
> latest cygwin snapshot by downloading this:

I guess that you can consider me reckless because I've been using
cygwin1-20000524.dll all day already.

Anyway, it fixes the mv problem that I reported in "Strange Cygwin
1.1.1 mv Behavior."  Since I use binary mount exclusively, I probably
won't be able to comment on the text mode fixes.  Unfortunately, I
saw one bash (2.04) crash running a shell script that I have run many
times before.  When tried it again (and again) I could not get it to
crash again.

Jason

-- 
Jason Tishler
Director, Software Engineering       Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corporation         Fax:   +1 (732) 264-8798
82 Bethany Road, Suite 7             Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA                 WWW:   http://www.dothill.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Need help. Latest snapshot may be next cygwin net release.

[David Bolen]

Hmm - I still seem to have a problem with CRLF endings in a .bcrc file on a
text mount.  I also ran into similar warnings from sed while trying to
re-run ".configure" on bc.  My .bcrc was created with NT-Emacs using the
default CRLF encoding.  Manually cleaning up the file to just use LF
continues to fix the problem with this latest DLL.  Reverting back to the
1.1.0 DLL works fine with the CRLF version of the file.

(ctwd0143-db3l) ~> cat /.bcrc
scale=5
(ctwd0143-db3l) ~> bc
bc 1.05
Copyright 1991, 1992, 1993, 1994, 1997, 1998 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'.
/.bcrc 1: illegal character: ^M

(ctwd0143-db3l) ~> cygcheck `which bc`.exe
/usr/local/bin/bc.exe
  d:\bin\cygwin1.dll
    C:\WINNT\System32\ADVAPI32.DLL
      C:\WINNT\System32\ntdll.dll
      C:\WINNT\System32\KERNEL32.dll
      C:\WINNT\System32\USER32.dll
        C:\WINNT\System32\GDI32.dll
      C:\WINNT\System32\RPCRT4.dll

Use -h to see help about each section

(ctwd0143-db3l) ~> grep "%%" /bin/cygwin1.dll
%%% Cygwin dll major: 1001
%%% Cygwin dll minor: 2
%%% Cygwin dll epoch: 19
%%% Cygwin dll bad signal mask: 19005
%%% Cygwin dll old termios: 00005
%%% Cygwin api major: 0
%%% Cygwin api minor: 21
%%% Cygwin shared data: 3
%%% Cygwin dll identifier: cygwin1
%%% Cygwin mount registry: 2
%%% Cygwin cygnus registry name: Cygnus Solutions
%%% Cygwin cygwin registry name: Cygwin
%%% Cygwin program options name: Program Options
%%% Cygwin cygwin mount registry name: mounts v2
%%% Cygwin build date: Thu May 25 00:16:21 EDT 2000
%%% Cygwin snapshot date: 2000-05-24-23:55-EST
%%% Cygwin shared id: cygwin1S3-2000-05-25 00:16

(ctwd0143-db3l) ~> mount
Device              Directory           Type         Flags
d:                  /                   system       textmode
c:                  /c                  system       textmode
(ctwd0143-db3l) ~> pwd
/u/db3l

-- David

-----Original Message-----
From: Chris Faylor [ mailto:cgf@cygnus.com ]
Sent: Thursday, May 25, 2000 3:44 PM
To: cygwin@sourceware.cygnus.com
Subject: Need help. Latest snapshot may be next cygwin net release.


I would appreciate it if any adventurous souls would try out the
latest cygwin snapshot by downloading this:

ftp://sourceware.cygnus.com/pub/cygwin/snapshots/cygwin1-20000524.dll.gz

This file should be copied to your /bin directory.  There should also
be a cygwin1.dll in this directory.  If there isn't, you're in the wrong
directory.

Once it's downloaded please:

    1) Terminate all running cygwin applications

    2) In the command shell, cd to the MS-DOS equivalent of your /bin
       directory, e.g.,
	d:
	cd cygwin\bin

    3) gzip -d cygwin1-20000524.dll.gz

    4) copy cygwin1.dll cygwin1.dll.safe

    5) copy cygwin1-20000524.dll cygwin1.dll

    6) Check any failing applications for correct operation.

This snapshot should fix all of the "\r\n" line ending problems that
were in cygwin-1.1.1.  It should also fix problems with rxvt on Windows
95.

Just to be clear, fixing "\r\n" line endings means that if you are in a
directory that has been mounted using the "-t" option then makefiles
should work as they used to in cygwin B20 and cygwin 1.1.0.  This DLL
fixes problems with text mode reads.

This DLL does not change anything about the way that the setup.exe
program previously mounted your root directory.  setup.exe mounts the
root directory as "binary".  If this is not acceptable you still have
to mount any directory containing files with MS-DOS style line endings
with the "-t" option.

So, if you have a directory called d:\src and it has all of your
sources in it, and they all have the carriage-return/line-feed endings
you have to:

	mount -t -f d:\src /src

This will cause files in d:\src and any subdirectories of d:\src to be
interpreted in text mode.

If you do try out this DLL, I would appreciate hearing success or failure
reports here in the cygwin@sourceware.cygnus.com mailing list.  Do not
send them to me personally.

If everything seems to be working well, I'll release a new version of
the DLL over the weekend.

Christopher Faylor
Cygwin Engineering Manager (and developer)
Cygnus Solutions, a Red Hat company

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Need help. Latest snapshot may be next cygwin net release.

[Chris Faylor]

I would appreciate it if any adventurous souls would try out the
latest cygwin snapshot by downloading this:

ftp://sourceware.cygnus.com/pub/cygwin/snapshots/cygwin1-20000524.dll.gz

This file should be copied to your /bin directory.  There should also
be a cygwin1.dll in this directory.  If there isn't, you're in the wrong
directory.

Once it's downloaded please:

    1) Terminate all running cygwin applications

    2) In the command shell, cd to the MS-DOS equivalent of your /bin
       directory, e.g.,
	d:
	cd cygwin\bin

    3) gzip -d cygwin1-20000524.dll.gz

    4) copy cygwin1.dll cygwin1.dll.safe

    5) copy cygwin1-20000524.dll cygwin1.dll

    6) Check any failing applications for correct operation.

This snapshot should fix all of the "\r\n" line ending problems that
were in cygwin-1.1.1.  It should also fix problems with rxvt on Windows
95.

Just to be clear, fixing "\r\n" line endings means that if you are in a
directory that has been mounted using the "-t" option then makefiles
should work as they used to in cygwin B20 and cygwin 1.1.0.  This DLL
fixes problems with text mode reads.

This DLL does not change anything about the way that the setup.exe
program previously mounted your root directory.  setup.exe mounts the
root directory as "binary".  If this is not acceptable you still have
to mount any directory containing files with MS-DOS style line endings
with the "-t" option.

So, if you have a directory called d:\src and it has all of your
sources in it, and they all have the carriage-return/line-feed endings
you have to:

	mount -t -f d:\src /src

This will cause files in d:\src and any subdirectories of d:\src to be
interpreted in text mode.

If you do try out this DLL, I would appreciate hearing success or failure
reports here in the cygwin@sourceware.cygnus.com mailing list.  Do not
send them to me personally.

If everything seems to be working well, I'll release a new version of
the DLL over the weekend.

Christopher Faylor
Cygwin Engineering Manager (and developer)
Cygnus Solutions, a Red Hat company

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com