Hey,
So when I run ./configure I get that it cannot find the X library. I have
searched everywhere for an answer for this question and I actually found one.
It says to change the configure script to search not only for $i/libX11.a and
$i/libX11.so, but also for $i/libX11.dll.a. Unfortunately, my
On Sun, Dec 28, 2003 at 03:52:33PM -, Max Bowsher wrote:
>Less common failures include shell scripts receiving terminating with a
>"Hangup" message, or locking up entirely.
>
>Debugging suggestions welcome.
Forgot to add that the obvious thing to try here is attaching to the
process in the "lo
On Sun, Dec 28, 2003 at 03:52:33PM -, Max Bowsher wrote:
>I installed a self-built cygwin HEAD version - mostly it works fine, but it
>causes odd failures during builds (speculation: race when many processes
>being created and destroyed?)
>
>The most common failure is a Windows error box:
>
>Th
At 10:03 PM 12/29/2003, Greg Smith you wrote:
>I'm trying a very simple search: cygpcre-0.dll
>It doesn't work, I get all the hits for cygpcre
>and dll, even if it's in quotes. As a result, I am
>probably about to submit a duplicate report.
>
>I know, it's probably because that's the way
>it's ind
I'm trying a very simple search: cygpcre-0.dll
It doesn't work, I get all the hits for cygpcre
and dll, even if it's in quotes. As a result, I am
probably about to submit a duplicate report.
I know, it's probably because that's the way
it's indexed. Still, it turns what could be a very
narrow, tar
On Mon, Dec 29, 2003 at 10:04:01PM -0500, Christopher Faylor wrote:
>On Sun, Dec 28, 2003 at 12:26:32PM -0500, Nicholas Wourms wrote:
>>Pierre A. Humblet wrote:
>>>At 12:46 PM 12/27/2003 -0500, Christopher Faylor wrote:
>>>
I missed the 'sh -c' clue in your previous message. Since sh uses
On Sat, Dec 27, 2003 at 06:28:09PM -0500, Pierre A. Humblet wrote:
>...when I launch inetd from an rxvt window running bash, or from a Dos
>window running cygwin.bat with tty, I still see tty handles in inetd.
I fixed some more problems with both vfork and with fork recently. The
fixes are curren
On Sun, Dec 28, 2003 at 12:26:32PM -0500, Nicholas Wourms wrote:
>Pierre A. Humblet wrote:
>>At 12:46 PM 12/27/2003 -0500, Christopher Faylor wrote:
>>
>>>I missed the 'sh -c' clue in your previous message. Since sh uses
>>>vfork, that indicates a vfork problem. I've checked in some more
>>>chang
In message <[EMAIL PROTECTED]>, Larry Hall writes:
>Would you be willing to take this a step further and provide some
>configuration timings for some of the existing Cygwin packages? Of
>particular interest would be the larger packages, like binutils, gcc, and
>gdb. If these have favorable resul
"Gerrit P. Haase" wrote:
>
> The Makefiles need to be modified, look for the install targets, they
> do things like: `cp httpd /target/path/httpd' which doesn't work
> without patched versions of the fileutils. Change the Makefiles to
> include the suffixes (`cp httpd.exe /target/path/httpd.exe')
On Mon, Dec 29, 2003 at 11:50:52AM -0500, Christopher Faylor wrote:
>On Sun, Dec 28, 2003 at 10:49:55AM +0100, Gerrit P. Haase wrote:
>>Hallo David,
>>
>>Am Montag, 22. Dezember 2003 um 01:08 schriebst du:
>>
>>> I notice that some of the larger info files, notably gcc & related files
>>> plus the
On Sun, Dec 28, 2003 at 10:49:55AM +0100, Gerrit P. Haase wrote:
>Hallo David,
>
>Am Montag, 22. Dezember 2003 um 01:08 schriebst du:
>
>> I notice that some of the larger info files, notably gcc & related files
>> plus the Cygwin-ug files, are in /usr/share/info as xxx.info.gz files.
>
>> Is info
You're not starting sshd as a service. You're not going to have allot of
luck starting it from the command line. If you're looking for debug output,
you need to install sshd under a different name (than "sshd") and pass it
the "-d" flag. See the "cygrunsrv -I" command in /bin/ssh-host-config fo
In message <[EMAIL PROTECTED]>, Larry Hall writes:
>Indeed. That it would be. Of course, like I said, lot's of things have
>changed so the results today don't necessarily conflict with the findings
>of yesteryear.
It's possible. My guess is that the big improvement was nuking the history
and j
I've tryed this advice from Corinna:
> - Deinstall the sshd service: cygrunsrv -R sshd
> - Edit /etc/passwd and remove the sshd account entry.
> - Remove the sshd account: net user sshd /delete
> - If you didn't change much in your /etc/ssh_config and /etc/ssdh_config
> files, remove them.
> - R
At 06:46 PM 12/29/2003, Peter Seebach you wrote:
>In message <[EMAIL PROTECTED]>, Peter Seebach writ
>es:
>>Can we just kill this now? Take out the "-j", leave the support for getopts
>>in the shell, and all the shell scripters will be happy. The configure
>>scripts will run at exactly the same s
In message <[EMAIL PROTECTED]>, Peter Seebach writ
es:
>Can we just kill this now? Take out the "-j", leave the support for getopts
>in the shell, and all the shell scripters will be happy. The configure
>scripts will run at exactly the same speed, and I will happily join in
>defending the decisi
Okay, some real data.
This is done using ash as of 20031007. The only change made is this:
*** builtins.def.orig Mon Dec 29 17:23:28 2003
--- builtins.defMon Dec 29 17:23:33 2003
***
*** 66,72
falsecmd false
histcmd -hfc
fgcmd -j fg
! getoptscmd -j
In message <[EMAIL PROTECTED]>, Larry Hall writes:
>Perhaps. By your own admission, you used different source though so the
>results of the space savings are inconclusive, or more precisely,
>incompatible given the historical base.
I can't imagine that "the ash source" varies that widely.
>But
At 03:48 PM 12/29/2003, Peter Seebach you wrote:
>In message <[EMAIL PROTECTED]>, Larry Hall writes:
>>I see. So how does this thread differ from previous ones on this subject?
>
>Well, first off, I've done the obvious test, and verified that there is no
>"13k space saving". There might be 1/2k.
* Larry Hall (2003-12-29 20:18 +0100)
> At 01:48 PM 12/29/2003, Thorsten Kampe you wrote:
>>* Lynn Wilson (2003-12-23 19:40 +0100)
>>> It seems that a few months ago the man pages were showing the ESC[1m etc. escape
>>> sequences in a bash shell. The problem was quickly fixed.
>>
>>> I downloaded
In message <[EMAIL PROTECTED]>, Brian Dessent writes:
>Peter Seebach wrote:
>> But, most importantly, it's in POSIX. I can see no reason for /bin/sh to not
>> be at least reasonably close to a POSIX shell, when the code is already
>> written.
>I was looking at the POSIX specs, and while getopts i
In message <[EMAIL PROTECTED]>, "Robb
, Sam" writes:
>> Well, first off, I've done the obvious test, and verified
>> that there is no "13k space saving". There might be 1/2k.
>There is no 13k space saving *now*. There may well have
>been with a previous set of sources and build tools.
I don't
Peter Seebach wrote:
> But, most importantly, it's in POSIX. I can see no reason for /bin/sh to not
> be at least reasonably close to a POSIX shell, when the code is already
> written.
I was looking at the POSIX specs, and while getopts is listed as a
required utility[1], and it is listed in the
> Well, first off, I've done the obvious test, and verified
> that there is no "13k space saving". There might be 1/2k.
There is no 13k space saving *now*. There may well have
been with a previous set of sources and build tools.
> I can indeed run tests, but right now, no one has offered
> e
Cygwin.bat
__
REGEDIT4
@echo off
if "%1"=="" goto login
bash -c "$( cygpath -u "%1" )"
goto fim
:login
C:
chdir C:\cygwin\bin
bash --login -i
:fim
cygwin.reg
__
REGEDIT4
[H
In message <[EMAIL PROTECTED]>, Larry Hall writes:
>I see. So how does this thread differ from previous ones on this subject?
Well, first off, I've done the obvious test, and verified that there is no
"13k space saving". There might be 1/2k.
>As far as I can see, you simply want to state your c
At 03:19 PM 12/29/2003, Peter Seebach you wrote:
>In message <[EMAIL PROTECTED]>, Larry Hall writes:
>>OK, sounds to me like you've convinced yourself that ash should contain
>>getopts. Does that mean that you no longer have a need to keep this thread
>>going? I'm not sure I see the discussion
Hallo Blair,
Am Montag, 29. Dezember 2003 um 04:51 schriebst du:
> I think I've found the problem.
> By more careful use of the -d=flags option to make, I traced it
> down to the second of two "subdirs"
> targets, and then turned off the NOECHO command (by taking it out
> of the script line in t
In message <[EMAIL PROTECTED]>, Larry Hall writes:
>OK, sounds to me like you've convinced yourself that ash should contain
>getopts. Does that mean that you no longer have a need to keep this thread
>going? I'm not sure I see the discussion providing any useful benefit beyond
>you becoming mor
At 02:54 PM 12/29/2003, Peter Seebach you wrote:
>In message <[EMAIL PROTECTED]>, Igor Pechtcha
>nski writes:
>>I'm sure this discussion is in the archives somewhere.
>
>A first run of casual searching hasn't turned it up.
>
>However, since I happen to have an unmunged ash source around, I removed
Christian Joensson <[EMAIL PROTECTED]> writes:
> [...]
> In file included from /usr/local/src/branch/gcc/libmudflap/mf-hooks2.c:1618:
> /usr/include/sys/ipc.h:59: error: syntax error before "ushort"
> /usr/include/sys/ipc.h:61: error: syntax error before "cuid"
> /usr/include/sys/ipc.h:62: error:
In message <[EMAIL PROTECTED]>, Igor Pechtcha
nski writes:
>I'm sure this discussion is in the archives somewhere.
A first run of casual searching hasn't turned it up.
However, since I happen to have an unmunged ash source around, I removed
getopts from it.
# Without getopts
$ ls -l obj/sh
-rwxr
On Mon, 29 Dec 2003, Blair P. Houghton wrote:
> Peter Seebach wrote:
> >In message <[EMAIL PROTECTED]>, Dario Alcocer writes:
> >>Use the "set -- `getopt`" idiom instead:
> >Yes, but *why*?
>
> ==
> % cygcheck --version
> cygcheck version 1.30
> System Checker for Cygwin
> Copyright 19
At 02:20 PM 12/29/2003, Peter Seebach you wrote:
>In message <[EMAIL PROTECTED]>, Larry Hall writes:
>>If you're curious, I suggest you run some timings on ash with and without
>>getopts enabled using a few configure scripts from some of Cygwin's
>>packages, large and small. It was the slowness
On Mon, 29 Dec 2003, Blair P. Houghton wrote:
> >The trailing backslashes aren't necessary. I've removed them in my LIB
> >and INCLUDE environment variables and VC works just fine. You could try
> >removing them and see if that fixes the perl build.
>
> Well, you can remove them manually; but this
At 01:48 PM 12/29/2003, Thorsten Kampe you wrote:
>* Lynn Wilson (2003-12-23 19:40 +0100)
>> It seems that a few months ago the man pages were showing the ESC[1m etc. escape
>> sequences in a bash shell. The problem was quickly fixed.
>
>> I downloaded docbook_xsl 1.64.1-1 yesterday and the proble
In message <[EMAIL PROTECTED]>, Larry Hall writes:
>If you're curious, I suggest you run some timings on ash with and without
>getopts enabled using a few configure scripts from some of Cygwin's
>packages, large and small. It was the slowness of configure scripts
>that prompted the streamlining
At 02:00 PM 12/29/2003, Peter Seebach you wrote:
>In message <[EMAIL PROTECTED]>, "Blair P. Houghto
>n" writes:
>>So I take it this "idiom" is only supposed to work in newer cygwin versions?
>
>I dunno. It's a very, very, odd idiom, that leaves you stuck with a great
>deal of manual parsing anyway
In message <[EMAIL PROTECTED]>, "Blair P. Houghto
n" writes:
>So I take it this "idiom" is only supposed to work in newer cygwin versions?
I dunno. It's a very, very, odd idiom, that leaves you stuck with a great
deal of manual parsing anyway.
>And I too am puzzled why someone would defeature a
* Lynn Wilson (2003-12-23 19:40 +0100)
> It seems that a few months ago the man pages were showing the ESC[1m etc. escape
> sequences in a bash shell. The problem was quickly fixed.
> I downloaded docbook_xsl 1.64.1-1 yesterday and the problem is back. I also
> downloaded a few X-modules. One
Peter Seebach wrote:
>In message <[EMAIL PROTECTED]>, Dario Alcocer writes:
>>Use the "set -- `getopt`" idiom instead:
>Yes, but *why*?
==
% cygcheck --version
cygcheck version 1.30
System Checker for Cygwin
Copyright 1998, 1999, 2000, 2001, 2002 Red Hat, Inc.
Compiled on Feb 8 2003
%
>The trailing backslashes aren't necessary. I've removed them in my LIB and
>INCLUDE environment variables and VC works just fine. You could try removing
>them and see if that fixes the perl build.
Well, you can remove them manually; but this is a computer and it should do the work.
The next
tim
On Mon, 29 Dec 2003 04:39:50 -, <[EMAIL PROTECTED]> wrote:
This is not an answer to the problem posted, but it reminds me to ask as
to where can a version of ImageMagick for cygwin is available for
download ?
I have the same question, assuming you mean a binary version.
(Actually I'm just
On Mon, 29 Dec 2003, Shaffer, Kenneth wrote:
> If using Active Perl with cygwin, put the following as the first line of
> your perl scripts:
>
> eval 'exec perl -S `cygpath -w $0`' if 0;
> --
> Ken Shaffer
...or put the following in your /usr/local/bin:
-- BEGIN /usr/local/bin/wrap -
Kimberlie,
On Tue, Dec 23, 2003 at 11:48:06AM -0500, Kimberlie S wrote:
> Thanks, Jason, for your help.
You are welcome.
> [snip]
>
> Am I doing something wrong?
I don't think so.
> Thanks for any other suggestions you might have!
I'm sorry but I don't know how to help you further.
Jason
-
If using Active Perl with cygwin, put the following as the first line of
your perl scripts:
eval 'exec perl -S `cygpath -w $0`' if 0;
--
Ken Shaffer
- - - - - - - Appended by Scientific-Atlanta, Inc. - - - - - - -
This e-mail and any attachments may contain information which is confid
In message <[EMAIL PROTECTED]>, Dario Alcocer writes:
>Peter Seebach wrote:
>
>>I know this is a pseudo-FAQ, but I haven't been able to find a clear enough
>>answer in the archives.
>>
>>1. Is it not the case that POSIX provides a specification for the getopts
>>builtin?
>>2. Doesn't ash, as orig
Peter Seebach wrote:
I know this is a pseudo-FAQ, but I haven't been able to find a clear enough
answer in the archives.
1. Is it not the case that POSIX provides a specification for the getopts
builtin?
2. Doesn't ash, as originally written, implement getopts?
I'm trying to figure out why this
--- "Blair P. Houghton" <[EMAIL PROTECTED]> wrote:
> I think I've found the problem.
>
> By more careful use of the -d=flags option to make, I traced it down to the
> second of two "subdirs"
> targets, and then turned off the NOECHO command (by taking it out of the
> script line in the Makefile
>
50 matches
Mail list logo
