Re: Unsufficient number of semaphores in a set

[Corinna Vinschen]

On May 19 02:08, Krzysztof Duleba wrote:
> Hello
> 
> I expreience strange Cygwin behaviour when I try to create a big semaphore
> set. I wrote a simple test case as following:
> [...]
> My Cygwin returns:
> 
> $ echo 59|./semtest
> ok
> 
> $ echo 60|./semtest
> ok
> 
> $ echo 61|./semtest
> 22; Invalid argument
> 
> 
> 
> On my friend's Linux box:
> 
> $ echo 61|./semtest
> ok
> $ echo 250|./semtest
> ok
> $ echo 251|./semtest
> 22; Invalid argument
> 
> 
> In /usr/include/cygipc/sys one can find
> 
> #define SEMMSL  32  /* <= 512 max num of semaphores per id */
> 
> It's obviously not the case. How can I have Cygwin allowing semaphore set
> of size 250?

First question:  Are you using cygipc or cygserver?

If you're using cygipc, somebody else will have to answer your question.

If you're using cygserver, the include files in /usr/include/cygipc
are irrelevant.  Look into /usr/include/sys.  If you want to change
the values, reading /usr/share/doc/Cygwin/cygserver.README will help.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader  mailto:[EMAIL PROTECTED]
Red Hat, Inc.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

tcsh 4k problem

[Kai Tomerius]

Hi,
I just encountered a problem with tcsh scripts with a size >4k. 
Admittedly, I don't run the latest version of tcsh, but I've searched 
the archives and didn't see this problem being fixed. Sorry if I missed 
something ...

Cheers,
Kai
The following script does pretty much nothing except for printing the 
parameters given to it; it's meant to demonstrate the problem:
-
#!/bin/tcsh -f

set f = ( )
while ( $# )
  set f = ( $f $1 )
  shift
end
foreach i ( $f )
  set x = 
"---"
  echo $i
end
-

This works. If you start duplicating the line "set x = ..." line, the 
script ceases to work as soon as the size exceeds (about) 4k (command 
shell output):
-
> ./x a b c
a
b
c
> ll x
-rwxrwxrwx1 tom  Kein 4097 May 19 10:32 x
> ./x a b c
a
b
c

...
> ./x a b c
a
Badly placed ()'s.
> ll x
-rwxrwxrwx1 tom  Kein 4098 May 19 10:33 x
-
The problem disappears again if I add a sufficiently high number of 
empty lines in front of the foreach statement.

Here is what cygcheck -s says:
-
Cygwin Win95/NT Configuration Diagnostics
Current System Time: Wed May 19 10:38:14 2004
Windows XP Professional Ver 5.1 Build 2600
Path:x:\bin
   E:\Programme\Cygwin\usr\local\bin
   E:\Programme\Cygwin\bin
   E:\Programme\Cygwin\bin
   E:\Programme\Cygwin\home\tom\bin
   c:\WINDOWS\system32
   c:\WINDOWS
   c:\WINDOWS\System32\Wbem
   E:\Programme\Cygwin\usr\X11R6\bin
Output from E:\Programme\Cygwin\bin\id.exe (nontsec)
UID: 1003(tom) GID: 513(Kein)
513(Kein)
Output from E:\Programme\Cygwin\bin\id.exe (ntsec)
UID: 1003(tom) GID: 513(Kein)
544(Administratoren)  545(Benutzer)
SysDir: C:\WINDOWS\System32
WinDir: C:\WINDOWS
HOME = `E:\Programme\Cygwin\home\tom'
LD_LIBRARY_PATH = `'
PWD = `/home/tom/temp'
USER = `tom'
Use `-r' to scan registry
c:  hd  NTFS8189Mb  47% CP CS UN PA FC
d:  hd  FAT32   2043Mb  20% CPUN   TRANSFER
e:  hd  NTFS8189Mb  70% CP CS UN PA FC Data
f:  hd  NTFS   19720Mb  14% CP CS UN PA FC Backup
r:  net NTFS   110168Mb  11% CP CSPADATA
s:  net NTFS   117796Mb 100% CP CS UN PA FC DATEN
t:  net NTFS   117796Mb 100% CP CS UN PA FC DATEN
x:  hd  FAT   63Mb   1% CPUN   RAMDisk
z:  cd   N/AN/A   

E:\Programme\Cygwin  / 
system  binmode
C:   /c
system  binmode
E:\Programme\Cygwin/bin  /usr/bin  
system  binmode
E:\Programme\Cygwin/lib  /usr/lib  
system  binmode
E:\Programme\Cygwin\usr\X11R6\lib\X11\fonts  /usr/X11R6/lib/X11/fonts  
system  binmode
./cygdrive 
system  binmode,cygdrive

Not Found: awk
Found: E:\Programme\Cygwin\bin\bash.exe
Found: E:\Programme\Cygwin\bin\cat.exe
Found: E:\Programme\Cygwin\bin\cp.exe
Found: E:\Programme\Cygwin\bin\cpp.exe
Found: E:\Programme\Cygwin\bin\find.exe
Found: E:\Programme\Cygwin\bin\gcc.exe
Found: E:\Programme\Cygwin\bin\gdb.exe
Found: E:\Programme\Cygwin\bin\grep.exe
Found: E:\Programme\Cygwin\bin\ld.exe
Found: E:\Programme\Cygwin\bin\ls.exe
Found: E:\Programme\Cygwin\bin\make.exe
Found: E:\Programme\Cygwin\bin\mv.exe
Found: E:\Programme\Cygwin\bin\rm.exe
Found: E:\Programme\Cygwin\bin\sed.exe
Found: E:\Programme\Cygwin\bin\sh.exe
Found: E:\Programme\Cygwin\bin\tar.exe
 232k 2004/01/14 E:\Programme\Cygwin\usr\local\bin\cygutil.dll
5126k 2004/01/13 E:\Programme\Cygwin\usr\local\bin\cygxerces-c24.dll
  61k 2003/08/09 E:\Programme\Cygwin\bin\cygbz2-1.dll
   7k 2003/10/19 E:\Programme\Cygwin\bin\cygcrypt-0.dll
 842k 2003/09/30 E:\Programme\Cygwin\bin\cygcrypto-0.9.7.dll
 645k 2003/04/11 E:\Programme\Cygwin\bin\cygcrypto.dll
  22k 2003/10/17 E:\Programme\Cygwin\bin\cygcygipc-2.dll
 380k 2002/07/24 E:\Programme\Cygwin\bin\cygdb-3.1.dll
 831k 2003/09/20 E:\Programme\Cygwin\bin\cygdb-4.1.dll
 487k 2002/07/24 E:\Programme\Cygwin\bin\cygdb_cxx-3.1.dll
1080k 2003/09/20 E:\Programme\Cygwin\bin\cygdb_cxx-4.1.dll
 155k 2004/01/07 E:\Programme\Cygwin\bin\cygexpat-0.dll
  71k 2004/01/13 E:\Programme\Cygwin\bin\cygexslt-0.dll
 131k 2003/10/28 E:\Programme\Cygwin\bin\cygfontconfig-1.dll
  45k 2001/04/25 E:\Programme\Cygwin\bin\cygform5.dll
  35k 2002/01/09 E:\Programme\Cygwin\bin\cygform6.dll
  48k 2003/08/09 E:\Programme\Cygwin\bin\cygform7.dll
 361k 2003/10/25 E:\Programme\Cygwin\bin\cygfreetype-6.dll
  28k 2003/07/20 E:\P

[OT] RE: Problems listing tasks under cygwin.

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of Brian Dessent
> Sent: 18 May 2004 19:34

> Dave Korn wrote:
> 
> >   Actually, SYSTEM has higher privileges in general than 
> root.  It may well
> > be impossible to kill some tasks belonging to system 
> because they may not
> > allow full access even to users with admin rights.  The 
> error message may be
> > misleading, and maybe it should be saying "Access denied".
> 
> FYI, you can kill SYSTEM processes as a regular user administrator
> account using Process Explorer from sysinternals.com.  I 
> haven't checked
> but I believe the program installs a helper driver that runs as SYSTEM
> to perform these actions as proxy for the user.  A lot of the
> sysinternals tools do something like that it seems.

  Yep.  A quick check with PEView shows that procexp.exe contains two binary
resources, RCDRIVERNT and RCDRIVER9X; the ..NT one clearly contains a .sys
driver file that creates a device.  Interesting functions it links against
include  ZwOpenProcess, KeDetachProcess and KeAttachProcess, and
ZwOpenProcessToken.  Looks like it attaches a thread into the process to be
killed and I'd guess it then gives access rights to the token allowing the
gui process to get at it.

[ObCygwin]  Sysinternals' tools are invaluable for diagnosing cygwin
problems just as much as windoze problems.  Trouble with access perms for
your cron daemon service?  See what's going on with tokenmon.  Trouble with
file access?  Filemon will show you what files are involved.  Need lofs
functionality?  Use HandleEx or ProcExp.  And so on!


cheers, 
  DaveK
-- 
Can't think of a witty .sigline today


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: [OT] RE: Problems listing tasks under cygwin.

[Brian Dessent]

Dave Korn wrote:

> [ObCygwin]  Sysinternals' tools are invaluable for diagnosing cygwin
> problems just as much as windoze problems.  Trouble with access perms for
> your cron daemon service?  See what's going on with tokenmon.  Trouble with
> file access?  Filemon will show you what files are involved.  Need lofs
> functionality?  Use HandleEx or ProcExp.  And so on!

Although I'd still like to know why using ProcExp to list the handles*
of any running Cygwin process causes the CPU to peg to 100%, and not
come down until cygwin1.dll is unloaded, i.e. kill all running cygwin
tasks and services.  I've had to train myself when using ProcExp to
never accidently click on any Cygwin process, otherwise I have to go
through the annoying process of closing all rxvt's and stopping all
cygservices in order to get an idle CPU again...  I've seen this
reported to the list before but it got no replies.  It started several
notches back in the 1.5 series when there were a large number of changes
to the signal handling code, IIRC.

[*] It could be listing DLLs that causes it, but I don't want to find
out at the moment.

Brian

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: tcsh 4k problem

[Corinna Vinschen]

On May 19 10:59, Kai Tomerius wrote:
> Hi,
> 
> I just encountered a problem with tcsh scripts with a size >4k. 
> Admittedly, I don't run the latest version of tcsh, but I've searched 
> the archives and didn't see this problem being fixed. Sorry if I missed 
> something ...

Known problem if the file has CRLF line endings.  Convert to LF line
endings (e.g. with dos2unix).

Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader  mailto:[EMAIL PROTECTED]
Red Hat, Inc.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

FYI: GNU Smalltalk 2.1.5 on Cygwin

[tuin01]

Concerning Cygwin dll: 1.5.9 (Complete install may 16, 2004)
GNU Smalltalk version 2.1.5
Windows XP (v 5.1) Professional SP1.

In directory where I've unpacked the smalltalk source package. 
./configure

changed following files.
1.  smalltalk-2.1.5/i18n/i18n.c
- added  #include 
2. libgst/Makefile
changed  -lgmp to /lib/libgmp.la in these lines

libgst_la_LIBADD=libgst_la_LIBADD = $(top_builddir)/lib-src/library.la 
$(LIBSIGSEGV) \
${top_builddir}/libltdl/libltdlc.la 
${top_builddir}/snprintfv/snprintfv/libsnprintfvc.la -lreadline 
/lib/libgmp.la

libgst_la_DEPENDENCIES = $(top_builddir)/lib-src/library.la $(LIBSIGSEGV) 
\
${top_builddir}/libltdl/libltdlc.la 
${top_builddir}/snprintfv/snprintfv/libsnprintfvc.la -lreadline 
/lib/libgmp.la

ran
make
make install

gst must be up and running.

Patrick.

I'll try and get 2.1.7 running, but has problem finding Glibc which is not 
available on cygwin. 

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: Cygwin's chmod +X

[Chris January]

> I noticed while creating a bash script to backup my parents outlook &
> mydocuments folers, that WindowsXP does not recognize a "superuser" as
> being allowed access to a users folders!

You can only access a folder if you have been given permission (in the ACL)
unless you open it in backup mode. You can only change the ACL if you are
the owner of the folder. If you are an Administrator you can take ownership
of the folder and change the permissions. What you actually want to do is
change the owner of these folders to the Administrators group and then:
Before backing up:
cacls * /t /e /g yourusername:F
After backing up:
cacls * /t /e /r yourusername
or something like that...

In Local Security Policy you can change the default owner of objects created
by members of the Administrators group to Administrators by changing the
"System Object: Default owner for objects created by members of the
administrator group option" in Local Policies/Security Options.

Chris


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

[gert_de_boer]

Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a
Windows 2003 server.

As an example of what happens:

$ echo hallo | mutt -s new_test [EMAIL PROTECTED]
Error sending message, child exited 127 (Exec error.).
Could not send the message.

The error is exactly the same as when I have a wrong 'sendmail' defined in
my .muttrc on a server where cygwin runs without any problem.  However I
defined it correct:
set sendmail=/usr/sbin/ssmtp

Executing ssmtp on its own delivers an empty mail at [EMAIL PROTECTED],
so the error is not there.

It all works without any problem on Windows XP and Windows 2000.

So it seems something has changed in Windows 2003: for some reason mutt
cannot trigger ssmtp to do its job.

Something similar seems to happen between the CYGWIN cron service and the
scripts it is supposed to start. Nothing happens, but if I look in the
eventviewer I see the following order of events:

PID 3188: (myaccount) RELOAD (tabs/myaccount)

PID 3392: (myaccount) CMD (/home/myaccount/bin/test_mail.sh)

PID 3392: (CRON) error (can't switchuser context)

So it is just an idea of mine that somehow (some) programs are not able to
start others, due to some rigid security settings.

BTW, all the above is done as with a group account with administrator
rights on the server.

Gert de Boer

gert de boer at ch schindler com

cygcheck.out:
(See attached file: cygcheck.out):

cygcheck.out
Description: Binary data
--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

[Buchbinder, Barry (NIH/NIAID)]

If I remember correctly (I have not played with mutt for quite a while),
mutt can connect directly to a IMAP or POP server.  So might you be able to
eliminate the use of ssmtp and have mutt send mail directly to the place
that ssmtp sends it?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 19, 2004 7:53 AM
To: [EMAIL PROTECTED]
Subject: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a
Windows 2003 server.

As an example of what happens:

$ echo hallo | mutt -s new_test [EMAIL PROTECTED]
Error sending message, child exited 127 (Exec error.).
Could not send the message.

The error is exactly the same as when I have a wrong 'sendmail' defined in
my .muttrc on a server where cygwin runs without any problem.  However I
defined it correct:
set sendmail=/usr/sbin/ssmtp

Executing ssmtp on its own delivers an empty mail at [EMAIL PROTECTED],
so the error is not there.

It all works without any problem on Windows XP and Windows 2000.

So it seems something has changed in Windows 2003: for some reason mutt
cannot trigger ssmtp to do its job.

Something similar seems to happen between the CYGWIN cron service and the
scripts it is supposed to start. Nothing happens, but if I look in the
eventviewer I see the following order of events:

PID 3188: (myaccount) RELOAD (tabs/myaccount)

PID 3392: (myaccount) CMD (/home/myaccount/bin/test_mail.sh)

PID 3392: (CRON) error (can't switchuser context)

So it is just an idea of mine that somehow (some) programs are not able to
start others, due to some rigid security settings.

BTW, all the above is done as with a group account with administrator
rights on the server.

Gert de Boer

gert de boer at ch schindler com

cygcheck.out:
(See attached file: cygcheck.out):

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: [OT] RE: Problems listing tasks under cygwin.

[Brian Ford]

On Wed, 19 May 2004, Brian Dessent wrote:

> Although I'd still like to know why using ProcExp to list the handles*

Nope, it is DLLs.

> of any running Cygwin process causes the CPU to peg to 100%, and not
> come down until cygwin1.dll is unloaded, i.e. kill all running cygwin
> tasks and services.  I've had to train myself when using ProcExp to
> never accidently click on any Cygwin process, otherwise I have to go
> through the annoying process of closing all rxvt's and stopping all
> cygservices in order to get an idle CPU again...

I don't quite see that.  Only the process being explored runs away.
After killing it, all is normal.

> I've seen this reported to the list before but it got no replies.

IIRC, I think I was the first to report it and you were the only one who
replied.  I haven't tried to fix it yet.

> It started several notches back in the 1.5 series when there were a
> large number of changes to the signal handling code, IIRC.

Agreed.

> [*] It could be listing DLLs that causes it, but I don't want to find
> out at the moment.

It's not that destructive as it only affects the process being explored.
Note that the DLLs are not able to be listed, though.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

[Luc Hermitte]

* On Wed, May 19, 2004 at 09:16:11AM -0400, Buchbinder, Barry (NIH/NIAID) <[EMAIL 
PROTECTED]> wrote:
> If I remember correctly (I have not played with mutt for quite a
> while), mutt can connect directly to a IMAP or POP server.  So might
> you be able to eliminate the use of ssmtp and have mutt send mail
> directly to the place that ssmtp sends it?

IMAP and POP3 protocols are meant to import emails.
SMTP is meant to export (/send) them.

I do use mutt with ssmtp to send messages like this one and I read my
email directly on an IMAP server.

Unfortunatelly, I can't help much. I use XP and every thing is working
fine. ssmtp is used to send the emails to a local STMP server (Hamster),
which then relays my messages to the SMTP servers of my ISP.

The only times I get the error
> Error sending message, child exited 127 (Exec error.).
> Could not send the message.
is when Hamster is not running -- as ssmtp can't reach the SMTP server
it must send the messages to.

But I'm not sure it is of any help here.

-- 
Luc Hermitte

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

[Brian Ford]

On Wed, 19 May 2004, gert_de_boer wrote:

> Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a
> Windows 2003 server.
>
> As an example of what happens:
>
> $ echo hallo | mutt -s new_test [EMAIL PROTECTED]
> Error sending message, child exited 127 (Exec error.).
> Could not send the message.
>
> The error is exactly the same as when I have a wrong 'sendmail' defined in
> my .muttrc on a server where cygwin runs without any problem.  However I
> defined it correct:
> set sendmail=/usr/sbin/ssmtp
>
> Executing ssmtp on its own delivers an empty mail at [EMAIL PROTECTED],
> so the error is not there.
>
> It all works without any problem on Windows XP and Windows 2000.
>
> So it seems something has changed in Windows 2003: for some reason mutt
> cannot trigger ssmtp to do its job.
>
> Something similar seems to happen between the CYGWIN cron service and the
> scripts it is supposed to start. Nothing happens, but if I look in the
> eventviewer I see the following order of events:
>
> PID 3188: (myaccount) RELOAD (tabs/myaccount)
>
> PID 3392: (myaccount) CMD (/home/myaccount/bin/test_mail.sh)
>
> PID 3392: (CRON) error (can't switchuser context)
>
> So it is just an idea of mine that somehow (some) programs are not able to
> start others, due to some rigid security settings.
>
> BTW, all the above is done as with a group account with administrator
> rights on the server.

Please read the Windows 2003 Server section of
/usr/share/doc/Cygwin/openssh.README and see if that helps.  I know it
sounds weird, but trust me, it is relevant.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

libtool dll linking problem

[Gerrit P. Haase]

Hallo cygwin,

Libtool tries to link:

sh ./libtool --mode=link g++ -avoid-version -rpath /usr/lib
-no-undefined -o libdbxml-1.2.la
ANTLRUtil.lo ASTFactory.lo ASTNULLType.lo ASTRefCount.lo BaseAST.lo
BitSet.lo CharBuffer.lo CharScanner.lo CommonAST.lo
CommonASTWithHiddenTokens.lo CommonHiddenStreamToken.lo
CommonToken.lo InputBuffer.lo LLkParser.lo
MismatchedCharException.lo MismatchedTokenException.lo
NoViableAltException.lo NoViableAltForCharException.lo Parser.lo
RecognitionException.lo String.lo Token.lo TokenBuffer.lo
TokenStreamBasicFilter.lo TokenStreamHiddenTokenFilter.lo
TokenStreamSelector.lo TreeParser.lo db_rdbt.lo Buffer.lo
Container.lo Cursor.lo Database.lo Document.lo HighResTimer.lo ID.lo
IDS.lo IndexSpecification.lo Indexer.lo Key.lo KeyStatistics.lo
Log.lo Name.lo QueryContext.lo QueryExpression.lo QueryPlan.lo
ReferenceCounted.lo Results.lo Statistics.lo Syntax.lo
SyntaxManager.lo TransactedContainer.lo UTF8.lo UpdateContext.lo
Value.lo VariableBindings.lo XmlQueryExpression.lo XPathLexer.lo
XPathParser.lo XPathProjectionTreeParser.lo
XPathSelectionTreeParser.lo XmlContainer.lo XmlDocument.lo
XmlException.lo XmlIndexSpecification.lo XmlNamespace.lo
XmlQueryContext.lo XmlResults.lo XmlUpdateContext.lo XmlValue.lo
XmlModify.lo Modify.lo /usr/lib/libdb_cxx-4.2.la
/usr/lib/libpathan.la -lxerces-c

g++ -shared /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/crtbegin.o
.libs/ANTLRUtil.o .libs/ASTFactory.o .libs/ASTNULLType.o
.libs/ASTRefCount.o .libs/BaseAST.o .libs/BitSet.o .libs/CharBuffer.o
.libs/CharScanner.o .libs/CommonAST.o .libs/CommonASTWithHiddenTokens.o
.libs/CommonHiddenStreamToken.o .libs/CommonToken.o .libs/InputBuffer.o
.libs/LLkParser.o .libs/MismatchedCharException.o
.libs/MismatchedTokenException.o .libs/NoViableAltException.o
.libs/NoViableAltForCharException.o .libs/Parser.o
.libs/RecognitionException.o .libs/String.o .libs/Token.o
.libs/TokenBuffer.o .libs/TokenStreamBasicFilter.o
.libs/TokenStreamHiddenTokenFilter.o .libs/TokenStreamSelector.o
.libs/TreeParser.o .libs/db_rdbt.o .libs/Buffer.o .libs/Container.o
.libs/Cursor.o .libs/Database.o .libs/Document.o .libs/HighResTimer.o
.libs/ID.o .libs/IDS.o .libs/IndexSpecification.o .libs/Indexer.o
.libs/Key.o .libs/KeyStatistics.o .libs/Log.o .libs/Name.o
.libs/QueryContext.o .libs/QueryExpression.o .libs/QueryPlan.o
.libs/ReferenceCounted.o .libs/Results.o .libs/Statistics.o
.libs/Syntax.o .libs/SyntaxManager.o .libs/TransactedContainer.o
.libs/UTF8.o .libs/UpdateContext.o .libs/Value.o
.libs/VariableBindings.o .libs/XmlQueryExpression.o .libs/XPathLexer.o
.libs/XPathParser.o .libs/XPathProjectionTreeParser.o
.libs/XPathSelectionTreeParser.o .libs/XmlContainer.o
.libs/XmlDocument.o .libs/XmlException.o .libs/XmlIndexSpecification.o
.libs/XmlNamespace.o .libs/XmlQueryContext.o .libs/XmlResults.o
.libs/XmlUpdateContext.o .libs/XmlValue.o .libs/XmlModify.o
.libs/Modify.o  /usr/lib/libdb_cxx-4.2.dll.a /usr/lib/libpathan.dll.a
-lxerces-c -L. -L/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1
-L/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../.. -lstdc++ -lgcc -lcygwin
-luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/crtend.o
-o .libs/libdbxml-1.2.dll.a

/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/crtbegin.o(.text+0x0):crtstuff.c: multiple 
definition of `___do_sjlj_init'
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/crtbegin.o(.text+0x0):crtstuff.c: first defined 
here

Info: resolving xercesc_2_4::XMLUni::fgXercescDefaultLocale   by linking to 
__imp___ZN11xercesc_2_46XMLUni22fgXercescDefaultLocaleE (auto-import)
Info: resolving xercesc_2_4::XMLPlatformUtils::fgMemoryManagerby linking to 
__imp___ZN11xercesc_2_416XMLPlatformUtils15fgMemoryManagerE (auto-import)
Info: resolving xercesc_2_4::XMLPlatformUtils::fgTransServiceby linking to 
__imp___ZN11xercesc_2_416XMLPlatformUtils14fgTransServiceE (auto-import)
Info: resolving xercesc_2_4::XMLUni::fgWFXMLScanner   by linking to 
__imp___ZN11xercesc_2_46XMLUni14fgWFXMLScannerE (auto-import)
Info: resolving xercesc_2_4::XMLUni::fgXercesScannerName   by linking to 
__imp___ZN11xercesc_2_46XMLUni19fgXercesScannerNameE (auto-import)
Info: resolving xercesc_2_4::XMLUni::fgSAX2CoreValidation   by linking to 
__imp___ZN11xercesc_2_46XMLUni20fgSAX2CoreValidationE (auto-import)
Info: resolving xercesc_2_4::XMLUni::fgSAX2CoreNameSpaces   by linking to 
__imp___ZN11xercesc_2_46XMLUni20fgSAX2CoreNameSpacesE (auto-import)
Info: resolving xercesc_2_4::XMLUni::fgXercesLoadExternalDTD   by linking to 
__imp___ZN11xercesc_2_46XMLUni23fgXercesLoadExternalDTDE (auto-import)
Info: resolving xercesc_2_4::XMLUni::fgXercesSchema   by linking to 
__imp___ZN11xercesc_2_46XMLUni14fgXercesSchemaE (auto-import)
collect2: ld returned 1 exit status
make: *** [libdbxml-1.2.la] Error 1


Why this: -o .libs/libdbxml-1.2.dll.a ?
What the heck is libtool doing here?


Gerr

RE: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

[Buchbinder, Barry (NIH/NIAID)]

Sorry for the noise.

-Original Message-
From: Luc Hermitte [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 19, 2004 10:09 AM
To: [EMAIL PROTECTED]
Subject: Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited
127'

* On Wed, May 19, 2004 at 09:16:11AM -0400, Buchbinder, Barry (NIH/NIAID)
<[EMAIL PROTECTED]> wrote:
> If I remember correctly (I have not played with mutt for quite a
> while), mutt can connect directly to a IMAP or POP server.  So might
> you be able to eliminate the use of ssmtp and have mutt send mail
> directly to the place that ssmtp sends it?

IMAP and POP3 protocols are meant to import emails.
SMTP is meant to export (/send) them.

I do use mutt with ssmtp to send messages like this one and I read my
email directly on an IMAP server.

Unfortunatelly, I can't help much. I use XP and every thing is working
fine. ssmtp is used to send the emails to a local STMP server (Hamster),
which then relays my messages to the SMTP servers of my ISP.

The only times I get the error
> Error sending message, child exited 127 (Exec error.).
> Could not send the message.
is when Hamster is not running -- as ssmtp can't reach the SMTP server
it must send the messages to.

But I'm not sure it is of any help here.

-- 
Luc Hermitte

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

[Mark Bohlman]

[EMAIL PROTECTED] wrote:

Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a
Windows 2003 server.
As an example of what happens:
$ echo hallo | mutt -s new_test [EMAIL PROTECTED]
Error sending message, child exited 127 (Exec error.).
Could not send the message.
The error is exactly the same as when I have a wrong 'sendmail' defined in
my .muttrc on a server where cygwin runs without any problem.  However I
defined it correct:
set sendmail=/usr/sbin/ssmtp
Executing ssmtp on its own delivers an empty mail at [EMAIL PROTECTED],
so the error is not there.
It all works without any problem on Windows XP and Windows 2000.
So it seems something has changed in Windows 2003: for some reason mutt
cannot trigger ssmtp to do its job.
Something similar seems to happen between the CYGWIN cron service and the
scripts it is supposed to start. Nothing happens, but if I look in the
eventviewer I see the following order of events:
PID 3188: (myaccount) RELOAD (tabs/myaccount)
PID 3392: (myaccount) CMD (/home/myaccount/bin/test_mail.sh)
PID 3392: (CRON) error (can't switchuser context)
So it is just an idea of mine that somehow (some) programs are not able to
start others, due to some rigid security settings.
BTW, all the above is done as with a group account with administrator
rights on the server.
Gert de Boer
gert de boer at ch schindler com
cygcheck.out:
(See attached file: cygcheck.out):
I had a similar problem on Win2K until I checked the 
/etc/ssmtp/ssmtp.conf file and found an improper setting.  Also check 
the ~/.muttrc file for correct settings.  Fixing this got rid of the 
same error message on my system.  See also /usr/share/doc/mutt-xxx.README.
Hope this helps.
-- Mark

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: tail and win file handling

[Paul Haas]

Larry Hall wrote:

> the file deleted by "rm" isn't deleted really until it's closed, which
> won't happen until 'tail' ends.  This is the way Windows works.  There's
> not much to be done about it (at least not in Cygwin).  Believe me,
> we've tried.

Here is a really ugly kludge to deal with a really ugly file system.

I'm sure I read about this sort of kludge before, so the idea is certainly
not original.

---Cut here--
#!/usr/bin/perl -w
# this acts sort of like tail -f, but doesn't keep the
# open.  It is designed for non-unix systems where open files
# can't be deleted.
# It mindlessly shows the last 512 bytes of the file on startup
# rather than the last 10 lines.
#
#  Paul Haas, May 19, 2004
my $file = shift;
open(TF,$file) || die "Reading $file $!";
seek(TF,-512,2);
@lines=;
my $curpos=tell(TF);
close(TF);
print @lines;
sleep 1;
while(-r $file ) {
  open(TF,$file) || die "Rereading $file $!";
  seek(TF,$curpos,0);
  @lines=;
  $curpos = tell(TF);
  print @lines;
  close(TF);
  sleep 1;
}


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Question concerning SSHD on CYGWIN

[Igor Pechtchanski]

Wrong list.  Please see  for
details.  In the meantime, I've redirected this to the correct one.
Please remove cygwin-patches from further discussion on this topic unless
you actually submit a patch to Cygwin.
Igor

On Wed, 19 May 2004, Kleinert, Marcel wrote:

> Hello,
>
> For a internal prototype we are using cygwin on a windows 2000 system to
> transfer data via ssh from one windows machine to this windows system
> with   cygwin sshd.
>
> If we have alot of data to transfer (e.g. 800 MB) after approximately 10
> minutes the transfer hangs
> without an exception.
>
> So I opened the log file for sshd on the cygwin folder on the target
> machine. In this log file
> I have the following messages:
>
> ++
>  9 [sig] sshd 2148 wait_sig: short read from signal pipe: 1 != 20
>3583 [sig] sshd 2148 wait_sig: short read from signal pipe: 2 != 20
> 1237139 [sig] sshd 2148 wait_sig: short read from signal pipe: 1 != 20
> 1245150 [sig] sshd 2148 wait_sig: short read from signal pipe: 2 != 20
> 1529145 [sig] sshd 2148 wait_sig: short read from signal pipe: 1 != 20
> 1536801 [sig] sshd 2148 wait_sig: short read from signal pipe: 2 != 20
> 3581925 [sig] sshd 2148 wait_sig: short read from signal pipe: 1 != 20
> 3591269 [sig] sshd 2148 wait_sig: short read from signal pipe: 2 != 20
> 6645385 [sig] sshd 2148 wait_sig: short read from signal pipe: 1 != 20
> 6883663 [sig] sshd 2148 wait_sig: short read from signal pipe: 1 != 20
>   9 [main] sshd 3684 sig_send: error sending signal 28 to pid 3684, pipe handle 
> 0x300, Win32 error 5
>  561758 [proc] sshd 3684 sig_send: error sending signal 20 to pid 3684, pipe handle 
> 0x300, Win32 error 5
>7482 [main] sshd 1556 sig_send: error sending signal 28 to pid 1556, pipe handle 
> 0x300, Win32 error 5
>  474317 [proc] sshd 1556 sig_send: error sending signal 20 to pid 1556, pipe handle 
> 0x300, Win32 error 5
> ++
>
> I am not really sure what the problem is. I also tried to transfer the
> data to a unix ssh daemon.
> With this daemon I had no problems. The whole 800 MB was transferred
> successfully.
>
> Do you think thats a bug in the ssh daemon of cygwin? And if it is a bug
> to you know how to fix it ?
>
> Thanks alot for your help in advance.
>  Marcel Kleinert

-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: FYI: GNU Smalltalk 2.1.5 on Cygwin

[Igor Pechtchanski]

On Wed, 19 May 2004, tuin01 wrote:

> Concerning Cygwin dll: 1.5.9 (Complete install may 16, 2004)
> GNU Smalltalk version 2.1.5
> Windows XP (v 5.1) Professional SP1.
>
> In directory where I've unpacked the smalltalk source package.
> ./configure
>
> changed following files.
> 1.  smalltalk-2.1.5/i18n/i18n.c
> - added  #include 

I'm assuming this was for some typedefs or macros.  If they are standard
POSIX ones that are present in the Linux headers but missing in the Cygwin
ones, it'd be interesting to know.

> 2. libgst/Makefile
> changed  -lgmp to /lib/libgmp.la in these lines
>
> libgst_la_LIBADD=libgst_la_LIBADD = $(top_builddir)/lib-src/library.la $(LIBSIGSEGV) 
> \
> ${top_builddir}/libltdl/libltdlc.la 
> ${top_builddir}/snprintfv/snprintfv/libsnprintfvc.la -lreadline /lib/libgmp.la
>
> libgst_la_DEPENDENCIES = $(top_builddir)/lib-src/library.la $(LIBSIGSEGV) \
> ${top_builddir}/libltdl/libltdlc.la 
> ${top_builddir}/snprintfv/snprintfv/libsnprintfvc.la -lreadline /lib/libgmp.la

This should not be needed...  What was the error that prompted this
change?
Igor

> ran
> make
> make install
>
> gst must be up and running.
>
> Patrick.
>
> I'll try and get 2.1.7 running, but has problem finding Glibc which is not
> available on cygwin.

-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: FYI: GNU Smalltalk 2.1.5 on Cygwin

[tuin01]

> > changed following files.
> > 1.  smalltalk-2.1.5/i18n/i18n.c
> > - added  #include 
> 
> I'm assuming this was for some typedefs or macros.  If they are standard
> POSIX ones that are present in the Linux headers but missing in the 
Cygwin
> ones, it'd be interesting to know.
> 

This were indeed some typedefs/macros. don't know exactly, but it were 
LANG_ typedefs, mainly because the macro MAKELANGID was not available.

> > 2. libgst/Makefile
> > changed  -lgmp to /lib/libgmp.la in these lines
> >
> > libgst_la_LIBADD=libgst_la_LIBADD = $(top_builddir)/lib-
> src/library.la $(LIBSIGSEGV) \
> > ${top_builddir}/libltdl/libltdlc.la ${top_builddir}
> /snprintfv/snprintfv/libsnprintfvc.la -lreadline /lib/libgmp.la
> >
> > libgst_la_DEPENDENCIES = $(top_builddir)/lib-src/library.la 
$(LIBSIGSEGV) \
> > ${top_builddir}/libltdl/libltdlc.la ${top_builddir}
> /snprintfv/snprintfv/libsnprintfvc.la -lreadline /lib/libgmp.la
> 
> This should not be needed...  What was the error that prompted this
> change?
>Igor
> 
this happened, because make quit on the error "no rule to make target 
-lgmp", so maybe the gmp library from cygwin is out of date.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: FYI: GNU Smalltalk 2.1.5 on Cygwin

[Brian Ford]

On Wed, 19 May 2004, tuin01 wrote:

> > > libgst_la_DEPENDENCIES = $(top_builddir)/lib-src/library.la
> $(LIBSIGSEGV) \
> > > ${top_builddir}/libltdl/libltdlc.la ${top_builddir}
> > /snprintfv/snprintfv/libsnprintfvc.la -lreadline /lib/libgmp.la
> >
> > This should not be needed...  What was the error that prompted this
> > change?
> >Igor
> >
> this happened, because make quit on the error "no rule to make target
> -lgmp", so maybe the gmp library from cygwin is out of date.

No, AFAIK, -lsomelib should never be in an automake _DEPENDENCIES target.
That's a Makefile.am bug in GNU Smalltalk.  Removing it from there should have
been all that was required.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Problem with terminal escapes for manpages RESENT W/OUT ENCLOSURES

[David A. Cobb]

I thought I sent this several weeks back, but I don't see it on the 
list.  My SWAG is that the attached zipfile caused it to be refused.
If the attachments are needed for understanding, please, how can I 
post them?
=== ORIGINAL MESSAGE FOLLOWS ===

Background: everything up to date
Terminal: rxvt
If I query info for a page that exists only in the manpages, all is 
well except there's nothing special about highlighting.
If, however, I use man itself it behaves as though it is 
double-escaping the highlight sequences: i.e. the \e]??m codes are 
in the source and man surrounds them with additional escapes in 
order to render "non-display" codes instead of just letting them do 
their thing.
If I'm really a glutton for punishment I can try pinfo.  That gives 
me the worst of both worlds.

attached:
(a) cygcheck output
(b) screenshot "info man"
(c) screenshot "man man"
(d) screenshot "pinfo man"
The screenshots were created in .png format by the Gimp v2.0-pre.
possibilities that occur to me: something not so good in terminfo or 
in my .Xdefaults

--
David A. Cobb, Software Engineer, Public Access Advocate
"By God's Grace, I am a Christian man; by my actions a great 
sinner." -- The Way of a Pilgrim: R.French, Tr.
Life is too short to tolerate crappy software!



begin:vcard
fn:David A. Cobb
n:Cobb;David A.
adr:;;7 Lenox Av #1;West Warwick;RI;02893-3918;USA
email;internet:[EMAIL PROTECTED]
title:Independent Software Consultant
note:PGP Key ID#0x4C293929 effective 01/28/2004
x-mozilla-html:TRUE
version:2.1
end:vcard


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Anyone using bash shell in Japanese, Chinese, or Korean?

[Joe Wigglesworth]

Your observation, Igor, is correct.  The 0x5C character is the backslash 
and that is at the root of the problem, especially in a command like ls. 
We haven't run across the problem with 0x2F, but that may just be a matter 
of time.

If Cygwin applications are handling the multibyte characters as a sequence 
of bytes that would certainly be the root of the problem. Moving to 
multibyte-friendly Windows API calls would be a big step forward.  Given 
the large number of Cygwin users in Japan, I'm surprised that hasn't 
already happened.  It must be possible because I've been told that the 
bash shell that comes with the MKS Toolkit can handle Japanese characters 
correctly.

-Joe


FWIW, I think it might be more than a coincidence that 0x5c is the ASCII
code for '\'.  I suspect the same problem will occur for characters with
0x2f ('/') in the second byte (if there are any).

The crux is that a lot of Cygwin applications don't have any handling of
multibyte characters -- they simply process each string as a sequence of
bytes.  The problem appears when the multi-byte representation contains
(accidentally) a character that's being treated specially (e.g., '/' or
'\').  How much of this is due to the program looking at the string
itself, and how much is due to using the wrong type of Windows API calls
(that aren't multibyte-friendly), remains to be seen.  It would be
interesting to strace the "ls ." invocation to see whether it breaks
somewhere inside "ls" or inside a Windows API call.
 Igor
P.S. We all saw the (identical?) post from two days ago
(), so there was no
need to re-post this.
-- 
 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_ [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_ [EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'Igor 
Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL  a.k.a JaguaR-R-R-r-r-r-.-.-. 
Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Unsufficient number of semaphores in a set

[Krzysztof Duleba]

Corinna Vinschen wrote:

> > In /usr/include/cygipc/sys one can find
> >
> > #define SEMMSL  32  /* <= 512 max num of semaphores per id
*/
> >
> > It's obviously not the case. How can I have Cygwin allowing semaphore
set
> > of size 250?
>
> First question:  Are you using cygipc or cygserver?

cygserver

> If you're using cygipc, somebody else will have to answer your question.
>
> If you're using cygserver, the include files in /usr/include/cygipc
> are irrelevant.  Look into /usr/include/sys.  If you want to change
> the values, reading /usr/share/doc/Cygwin/cygserver.README will help.

I wasn't aware of /etc/cygserver.conf file, which was mentioned in the
readme. Thanks.

Regards
Krzysztof Duleba



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: FYI: GNU Smalltalk 2.1.5 on Cygwin

[tuin01]

Brian Ford <[EMAIL PROTECTED]> wrote on 19-05-2004 21:34:37:

> 
> No, AFAIK, -lsomelib should never be in an automake _DEPENDENCIES 
target.
> That's a Makefile.am bug in GNU Smalltalk.  Removing it from there 
should have
> been all that was required.
> 

You're absolutely right I tried again without the /lib/libgst.la line and 
it works like a charm. I'm no make expert and I was a bit afraid I took 
away to much if I deleted it there's also a -lreadline in the 
dependencies. I'll try and find out how the Makefile.am should be changed 
to avoid this in later builds, I'm 99% sure it's still there in 2.1.7

patrick

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: xemacs shell problem

[Rui-Tao Dong]

Some old XEmacs (21.1 era) was handling this correctly, so I believe
the problem is in XEmacs.  I haven't had a chance to trace XEmacs code
yet.  I have been using the following work around.  None of which is
perfect.

1)  Stick with an old XEmacs.

2)  Do run /usr/local/bin/xemacs.  You can search google for cygwin
run.  However, although it works the first a few times,  the problem
re-appears after a while.

3)  Instead of compile with nmake -k (e.g.), do ssh localhost "cd $PWD; nmake -k"

-- 

Rui-Tao Dong
[EMAIL PROTECTED]


> "sly5+gmane" == Levent Yilmaz <[EMAIL PROTECTED]> writes:

 sly5+gmane> Hi!  After posting this message to emacs.xemacs.windows
 sly5+gmane> and following the advices I have been told, I found out
 sly5+gmane> that this happens only with Xemacs Cygwin build. Thus, I
 sly5+gmane> hope it would be a relevant discussion for this group.

 sly5+gmane> *the problem setting* The shell-mode(using bash) at
 sly5+gmane> Xemacs(21.4.15) called from Bash (2.05b.0(1)-release)
 sly5+gmane> running Cygwin(1.42) on WindowsXP-SP1

 sly5+gmane> *the ISSUE* Error messages from certain Windows console
 sly5+gmane> programs (such as the Fortran compilers LaheyF95 and
 sly5+gmane> Compaq Visual Fortran 6.6) (hereafter I will refer these
 sly5+gmane> as Compiler) are not displayed at the
 sly5+gmane> shell-buffer. Instead the errors are flushed to a DOS
 sly5+gmane> console that dissappears immidiately after the
 sly5+gmane> compilation is finished and the regular messages (logo
 sly5+gmane> and stuff) are displayed at the shell-buffer as usual.

 sly5+gmane> *complications* - When the Compiler is invoked directly
 sly5+gmane> from Bash, everything works fine, all messages are there
 sly5+gmane> and in fact, output redirection works as expected. The
 sly5+gmane> error mesages can be redirected with the usual 2>myfile.
 sly5+gmane> - This issue does not occur with all console applications
 sly5+gmane> (for instance I tried with MSVC++6/7 and they are working
 sly5+gmane> fine).  Among the ones I tested, only these fortran
 sly5+gmane> Compilers has this behaviour. This is also why I fail to
 sly5+gmane> find a reproducible example for submitting as a test case
 sly5+gmane> here (though, you may download a trial version from
 sly5+gmane> http://www.lahey.com/ and test with a erroneous Fortan
 sly5+gmane> code, if you really agree that this is a significant
 sly5+gmane> issue and worth the trouble).  Here is a sample failing
 sly5+gmane> FORTRAN code !== program fail end
 sly5+gmane> program nail !== - As I mentioned
 sly5+gmane> before this problem happens only with Xemacs Cygwin
 sly5+gmane> build. Native-Windows build is working fine.

 sly5+gmane> My question is, it seems that the output from the
 sly5+gmane> Compiler is flushed to that blinking console, what may be
 sly5+gmane> the cause of this? Are there other outputs other than
 sly5+gmane> STDERR and STDOUT, that Cygwin is handling properly, but
 sly5+gmane> the shell-mode in Xemacs is failing?

 sly5+gmane> Thank you so very much!!  - Levent









-- 

Rui-Tao Dong
(949) 673-1907 x116
(949) 673-1058(Fax)
[EMAIL PROTECTED]

ALL INFORMATION IN THIS EMAIL OR ATTACHED TO THIS EMAIL IS CONFIDENTIAL.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Problem with pty allocation code, race condition?

[Igor Pechtchanski]

On Mon, 17 May 2004, Christopher Faylor wrote:

> On Mon, May 17, 2004 at 09:29:44AM -0400, John P. Rouillard wrote:
> >Does the last cygwin snapshot contain any code changes in the pty
> >allocation area?
>
> Yes, the very latest snapshot attempts to fix this problem.  Please give
> it a try and report the results here.

I'm sorry to report that the problem I described in
<http://cygwin.com/ml/cygwin/2004-05/msg00596.html> (multiple xterms
started in quick succession get the same PTY) still exists in the 20040519
snapshot.  The output of "ps" after reproducing it with 4 xterms is below,
if it's of any help (the last bash, PID 1948, is a console).

$ ps
  PIDPPIDPGID WINPID  TTY  UIDSTIME COMMAND
 1732   11732   1748  con 1001 17:52:43 /usr/bin/xterm
 2812   12812   1268  con 1001 17:52:43 /usr/bin/xterm
 1160   11160   1152  con 1001 17:52:43 /usr/bin/xterm
 1772   11772   1844  con 1001 17:52:43 /usr/bin/xterm
S199617321996   20360 1001 17:52:53 /usr/bin/bash
S124428121244   21200 1001 17:52:53 /usr/bin/bash
I197211601972   21320 1001 17:52:53 /usr/bin/bash
S198817721988   21280 1001 17:52:53 /usr/bin/bash
 1948   11948   1948  con 1001 17:53:16 /usr/bin/bash
 208819482088968  con 1001 17:53:19 /usr/bin/ps

Note that now it's the third xterm that got a working bash, so I think my
prior conclusion that the last one always wins was wrong.  Note also that,
for some reason, there was a 10-second delay between starting the xterms
and having the bash shells started.  As before, any ideas on how to debug
this are appreciated.  FWIW, cygcheck output is attached.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Cygwin Configuration Diagnostics

Current System Time: Wed May 19 18:02:24 2004



Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 3



Path:   C:\cygwin\home\igor\bin

C:\cygwin\usr\local\bin

C:\cygwin\bin

C:\cygwin\bin

C:\cygwin\usr\local\games

C:\cygwin\usr\X11R6\bin

c:\Program Files\IBM\Java14\bin

c:\Program Files\IBM\Infoprint Select

c:\ActivePerl\bin

c:\MikTeX\miktex\bin

c:\WINNT\system32

c:\WINNT

c:\WINNT\system32\wbem

c:\Program Files\IBM\Trace Facility

c:\Program Files\Personal Communications

c:\Notes

c:\Utilities

c:\Program Files\ThinkPad\Utilities

c:\cygwin\bin

.\



Output from C:\cygwin\bin\id.exe (nontsec)

UID: 1001(igor) GID: 544(Administrators)

544(Administrators)  10953([EMAIL PROTECTED])



Output from C:\cygwin\bin\id.exe (ntsec)

UID: 1001(igor) GID: 544(Administrators)

513(None)544(Administrators)  

545(Users)



SysDir: C:\WINNT\system32

WinDir: C:\WINNT



CYGWIN = `check_case:strict ntsec notitle binmode nosmbntsec notty'

HOME = `C:\cygwin\home\igor'

MAKE_MODE = `unix'

PWD = `/home/igor'

USER = `igor'



ALLUSERSPROFILE = `C:\Documents and Settings\All Users'

APPDATA = `C:\Documents and Settings\igor\Application Data'

COMMONPROGRAMFILES = `C:\Program Files\Common Files'

COMPUTERNAME = `PECHTCHA'

COMSPEC = `C:\WINNT\system32\cmd.exe'

CVSREAD = `true'

CVS_RSH = `/bin/ssh'

HOMEDRIVE = `C:'

HOMEPATH = `\Documents and Settings\igor'

HOSTNAME = `pechtcha'

JAVA_HOME = `/usr/contrib/java'

JIKESPATH = 
`.:/usr/contrib/java/jre/lib/core.jar:/usr/contrib/java/jre/lib/charsets.jar'

LOGONSERVER = `\\PECHTCHA'

MANPATH = 
`/usr/local/man:/usr/man:/usr/autotool/devel/man:/usr/contrib/jikes/man::/usr/ssl/man:/usr/X11R6/man'

NUMBER_OF_PROCESSORS = `1'

OLDPWD = `/tmp'

OS2LIBPATH = `C:\WINNT\system32\os2\dll;'

OS = `Windows_NT'

PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'

PCOMM_ROOT = `C:\Program Files\Personal Communications'

PDBASE = `C:\Program Files\IBM\Infoprint Select'

PDHOST = `ushawsrv01'

PD_SOCKET = `6874'

PKG_CONFIG_PATH = `/usr/X11R6/lib/pkgconfig'

PROCESSOR_ARCHITECTURE = `x86'

PROCESSOR_IDENTIFIER = `x86 Family 6 Model 8 Stepping 6, GenuineIntel'

PROCESSOR_LEVEL = `6'

PROCESSOR_REVISION = `0806'

PROGRAMFILES = `C:\Program Files'

PROMPT = `$P$G'

PS1 = `[