The problem is still existing:
$ cygport emacs-22.3-1.cygport prep
Preparing emacs-22.3-1
*** Info: SOURCE 1 signature follows:
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: Signature made Fri Sep 5 18:34:56 2008 WEST using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steffen Sledz wrote:
The problem is still existing:
$ cygport emacs-22.3-1.cygport prep
Preparing emacs-22.3-1
*** Info: SOURCE 1 signature follows:
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for
On 1/18/2009 1:11 PM, Steffen Sledz wrote:
The problem is still existing:
You received a reply on the main cygwin mailing list to your first
message about this problem:
http://cygwin.com/ml/cygwin/2008-10/msg00524.html
By the way, do you subscribe to that list? There was quite a bit of
wget -x -nH --cut-dirs=2 \
http://mysite.verizon.net/res00a7j/cygwin/libapr1/apr1/apr1-1.3.3-3.tar.bz2 \
http://mysite.verizon.net/res00a7j/cygwin/libapr1/apr1/setup.hint \
http://mysite.verizon.net/res00a7j/cygwin/libapr1/libapr1-1.3.3-3-src.tar.bz2
\
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This is quickly becoming a FAQ, so:
ftp://ftp.cygwinports.org/pub/cygwinports/release/bind/bind-9.6.0-1-src.tar.bz2
ftp://ftp.cygwinports.org/pub/cygwinports/release/bind/bind-9.6.0-1.tar.bz2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andy Koppe wrote:
I'd like to maintain MinTTY as an official Cygwin package. MinTTY is a
small and fast pty-based terminal emulator with a native Windows user
interface. As it's a new program, it requires 5 positive votes.
+1, that makes five.
Yaakov (Cygwin/X) wrote:
Glad to help. Under the circumstances, I'll let someone else to review
the packages. It's a really quick build with deps only on cygwin and
w32api, so I hope someone will step forward quickly.
Packaging looks good, and builds fine from source. Just one quibble with
Charles Wilson wrote:
Doesn't cygwin officially support i386, or are we allowed to assume i586
and above, now?
Considering that support for Win98 is going to be dropped, the
question may be answered if Win2K or better will even run on
a 386 or 486? :-)
Ralph
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralph Hempel on 1/18/2009 4:44 PM:
Charles Wilson wrote:
Doesn't cygwin officially support i386, or are we allowed to assume i586
and above, now?
Considering that support for Win98 is going to be dropped, the
question may be
Eric Blake wrote:
According to Ralph Hempel on 1/18/2009 4:44 PM:
Charles Wilson wrote:
Doesn't cygwin officially support i386, or are we allowed to assume i586
and above, now?
Considering that support for Win98 is going to be dropped, the
question may be answered if Win2K or better will
Hang on... one little afterthought.
Considering that support for Win98 is going to be dropped, the
question may be answered if Win2K or better will even run on
a 386 or 486? :-)
Did we drop support for NT4 already? ;-)
cheers,
DaveK
Ralph Hempel wrote:
Charles Wilson wrote:
Doesn't cygwin officially support i386, or are we allowed to assume i586
and above, now?
Considering that support for Win98 is going to be dropped, the
question may be answered if Win2K or better will even run on
a 386 or 486? :-)
a) cygwin-1.7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
Did we drop support for NT4 already? ;-)
Is NT4 really *still* supported by MS?
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
Woo hoo!
Thanks Yaakov!
cgf
I'd like to maintain MinTTY as an official Cygwin package. MinTTY is a
small and fast pty-based terminal emulator with a native Windows user
interface. As it's a new program, it requires 5 positive votes.
+1, that makes five.
Thanks everyone for the support!
Charles Wilson wrote:
a)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
An old cygwin installation where I haven't updated Xorg yet doesn't show
this behavior.
So it really looks like some X lib is the culprit.
I've got a hunch. On 1.7, could you try replacing your libxcb1 with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Paul Loewenstein wrote:
Sorry, I did the diff backwards. You can tell I don't do this often.
Corrected .diffs attached, so you don't have to use the patch reverse
option.
Could you please provide these as one unidiff (-u) patch?
Yaakov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Ah, and what do you think about the attached change to the .cygport file
itself to propagate the distribution patchlevel into the version number?
I would prefer to use the BUILD_DATE define instead, since that is a
patch to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Attached is a patch against the xinit package in cygports svn:
* In an attempt to avoid some instances of the ever popular I upgraded
X and now my keyboard doesn't work problem, update the X server
starting sample scripts to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
I'm sorry that I wasn't completely precise but, yes, of course I meant
the Cygwin/X component.
Could you make me (yselkowitz AT cygwin DOT com) the default
owner/assignee for the Cygwin/X component?
Yaakov
Cygwin/X
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
There's a few packaging oddities with regards to X fonts requirements,
which could probably do with tidying up.
Agreed. Opened bug accordingly:
http://sourceware.org/bugzilla/show_bug.cgi?id=9761
Yaakov
Cygwin/X
-BEGIN
Ok for HEAD of both gcc/ and src/ ?
Ok.
libiberty/ChangeLog
* configure.ac (funcs, vars, checkfuncs): Don't munge on Cygwin,
as it no longer shares libiberty object files.
* configure: Regenerated.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Vincent François wrote:
That I applied the new command (diff -u), the file syntax.nanorc.patch
is now join ;-)
Excuse me for my English, I am of French origin.
Merci beaucoup.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9
Version 0.42-1 of monotone has been uploaded.
monotone is a free distributed version control system. it provides a
simple, single-file transactional version store, with fully disconnected
operation and an efficient peer-to-peer synchronization protocol. it
understands history-sensitive merging,
On Wed, Jan 14, 2009 at 10:29 AM, Larry Hall (Cygwin)
reply-to-list-only...@cygwin.com wrote:
Alexey Eremenko wrote:
Seeing the output (*attached*) from 'cygcheck -s -r -v' as requested by
http://cygwin.com/problems.html would help. What does 'ls -ld /etc'
say? What does 'getfacl /etc' say?
On Sun, Jan 18, 2009 at 16:12, Alexey Eremenko wrote:
$ cygrunsrv -S sshd
and I hope SSH service started but have no idea if it really started...
cygrunsrv -Q sshd
C:\cygwin\binssh localhost
ssh_exchange_identification: Connection closed by remote host
It still does not work. What else
Hi,
Thanks for all the done job : packages, setup and mirrors.
I would like to know if there's a way to lauch some cygwin program
without have windows console box _on screen_.
I whould lauch at start-up, via services.msc, a command line to have a
resident like program. Is that possible ?
Best
On 1/18/2009 8:29 AM, Daniel Stonier wrote:
Hi,
Hi. Please direct these kinds of questions to the cygwin mailing list
(cygwin AT cygwin.com) in the future.
I've been running into a few hitches with libapr1 and libapr1-util on
cygwin. Namely another package I need requires liblog4cxx to
On 1/18/2009 10:44 AM, David Rothenberger wrote:
On 1/18/2009 8:29 AM, Daniel Stonier wrote:
I've been running into a few hitches with libapr1 and libapr1-util on
cygwin. Namely another package I need requires liblog4cxx to have
these libraries available statically and I noticed the cygwin
Hey all,
I'm not very great with the inner workings of GNU or Cygwin libc, so
please bear with me if I make any mistakes or misunderstandings.
I was trying to get GNU coreutils to work on Cygwin. Maybe this seems
weird to you guys, because Cygwin has coreutils, but there are a few
reasons:
Hey all,
I'm not very great with the inner workings of GNU or Cygwin libc, so
please bear with me if I make any mistakes or misunderstandings.
I was trying to get GNU coreutils to work on Cygwin. Maybe this seems
weird to you guys, because Cygwin has coreutils, but there are a few
reasons:
Sébastien Major wrote:
Hi,
Thanks for all the done job : packages, setup and mirrors.
I would like to know if there's a way to lauch some cygwin program
without have windows console box _on screen_.
I whould lauch at start-up, via services.msc, a command line to have a
resident like program.
dazjorz wrote:
Hey all,
I'm not very great with the inner workings of GNU or Cygwin libc, so
please bear with me if I make any mistakes or misunderstandings.
I was trying to get GNU coreutils to work on Cygwin. Maybe this seems
weird to you guys, because Cygwin has coreutils, but there are
Larry Hall (Cygwin) wrote:
dazjorz wrote:
Hey all,
I'm not very great with the inner workings of GNU or Cygwin libc, so
please bear with me if I make any mistakes or misunderstandings.
I was trying to get GNU coreutils to work on Cygwin. Maybe this seems
weird to you guys, because Cygwin
Hi. Please direct these kinds of questions to the cygwin mailing list
(cygwin AT cygwin.com) in the future.
Sure.
I recall that the build failed when static libraries were enabled. I don't
recall how. I'll try it again and see if I can debug it. Feel free to
download the source package and
On 1/18/2009 1:26 PM, Daniel Stonier wrote:
David Rothenberger wrote:
I recall that the build failed when static libraries were enabled.
[snip]
However, I've run into a few hitches with the cygwin source build - I
just started using cygwin yesterday, so not very familiar with its
build
dazjorz wrote:
- Cygwin didn't have md5sum,
Cygwin does have md5sum in coreutils. You can see this at the cygwin
package list:
http://cygwin.com/packages/
by entering 'md5sum.exe' in the search box.
- It should work, and Because I Can is always a valid reason in UNIX
world
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sjors Gielen wrote:
Did you try with Cygwin coreutils or GNU coreutils? :)
Cygwin's coreutils *is* GNU coreutils, with some patches which you will
find necessary.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using
Yaakov (Cygwin/X) wrote:
Sjors Gielen wrote:
Did you try with Cygwin coreutils or GNU coreutils? :)
Cygwin's coreutils *is* GNU coreutils, with some patches which you will
find necessary.
[snip]
Dave Korn wrote:
However, you may have to recreate all the cygwin-specific patches
that the
On Sun, Jan 18, 2009 at 5:11 PM, Sjors Gielen wrote:
I'm trying to create a full Cygwin port for Debian. This means the base
system packages, et cetera. Let's just keep it at I love apt and dpkg for
package managers.
Keep in mind that apt and dpkg will never be able to work completely
on
Hello all,
* Sjors Gielen mailingl...@dazjorz.com wrote:
Yaakov (Cygwin/X) wrote:
Sjors Gielen wrote:
Did you try with Cygwin coreutils or GNU coreutils? :)
Cygwin's coreutils *is* GNU coreutils, with some patches which you will
find necessary.
[snip]
Dave Korn wrote:
However, you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Sjors Gielen on 1/18/2009 3:11 PM:
cygwin bash maintainer hasn't managed to send upstream yet...
[snip]
?? Are you using an old version?? It should be fixed by now.
http://www.mail-archive.com/bug-coreut...@gnu.org/msg10188.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ed Schouten on 1/18/2009 3:19 PM:
But that's not a proper fix anyway. cat can't just decide to reopen the
file descriptor of the standard output. That even breaks the first
sentence of POSIX:
The cat utility shall read files
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Dave Korn on 1/18/2009 2:42 PM:
However, you may have to recreate all the cygwin-specific patches that the
cygwin bash maintainer hasn't managed to send upstream yet...
Not only that, but some of those patches will never be sent
Hugh Sasse wrote on 22 May 2008 12:08:
relsondt1-- ./hello.sh
+ Bcc +BccDos.cfg -c -Ic:/BC45/INCLUDE -D -oHELLO.OBJ HELLO.CPP
7 [main] bash 5564! _pinfo::dup_proc_pipe: DuplicateHandle failed, \
pid 5564, hProcess 0x6DD, wr_proc_pipe 0x750, Win32 error 6
That Win32 error looks
Corinna Vinschen wrote:
I applied a patch to cygcheck in CVS which avoids the recursion due to
the funny behaviour of the Wow6432Node in 32 bit mode.
Corinna
Thanks. I compiled that (under cygwin on an XP machine) and it worked.
Cygwin now works on my 64-bit Vista machine too. I decided
Greetings to the Cygwin list forum,
I have had some difficulty finding a place to post this question and I hope
this is it.
I have a cygwin bash script that runs rsync and makes some entries in the
rsync log files.
Here is an example.
echo
On 01/18/2009, LMHmedchem wrote:
Can anyone tell me why this is not working, especially since it works on
another computer with the same setup?
Without any configuration information from the machine having this problem,
it's hard to say anything too definitive. However, my WAG is that you
I added c:\cygwin\bin; to the path and that seems to have corrected the
problem, thanks for the tip.
Two questions if you have a minute,
1. At first I tried adding cygwin to the end of the path, but that didn't
work. I checked my other machine and found cygwin immediately after
LMHmedchem wrote:
I added c:\cygwin\bin; to the path and that seems to have corrected the
problem, thanks for the tip.
Two questions if you have a minute,
1. At first I tried adding cygwin to the end of the path, but that didn't
work. I checked my other machine and found cygwin immediately
Version 0.42-1 of monotone has been uploaded.
monotone is a free distributed version control system. it provides a
simple, single-file transactional version store, with fully disconnected
operation and an efficient peer-to-peer synchronization protocol. it
understands history-sensitive merging,
51 matches
Mail list logo
