You need to build with the newest version of mingw from the mingw64-i686
package. It seems like yours is out of date. Corinna and I build with
the i686-w64-mingw32 target.
It appears I have the latest version (gcc, g++, 4.5.3-6,
runtime runtime-3.0b_svn5747-1, headers-3.0b_svn5747-1) offered
On Jun 21 09:26, d_h...@hotmail.com wrote:
You need to build with the newest version of mingw from the mingw64-i686
package. It seems like yours is out of date. Corinna and I build with
the i686-w64-mingw32 target.
It appears I have the latest version (gcc, g++, 4.5.3-6,
runtime
I really don't know what you mean.
on 32bit XP SP3, With cygwin installation of the latest packages currently
(well as of 2013/06/03 or so) available from mirrors.kernel.org, a 32bit build
of setup retrieved from cvs as -D20130619 will not run on
A patch for setup providing command line switches (-I, --include-source) to
automatically include source packages associated with any selected binary
packages when downloading/installing.
The first version is targeted at source revision 2.774 (can obtain as
-D20120430) from cvs, which seems to
On Jun 21 10:40, d_h...@hotmail.com wrote:
I really don't know what you mean.
on 32bit XP SP3, With cygwin installation of the latest packages currently
(well as of 2013/06/03 or so) available from mirrors.kernel.org, a 32bit
build of setup
Hi Ken,
On Jun 20 21:16, Corinna Vinschen wrote:
On Jun 20 15:07, Ken Brown wrote:
On 6/20/2013 2:42 PM, Corinna Vinschen wrote:
On Jun 20 12:10, Ken Brown wrote:
I'm giving four separate wget commands below to make it clear what's
happening:
The first is for noarch packages that
On 6/21/2013 7:02 AM, Corinna Vinschen wrote:
Hi Ken,
On Jun 20 21:16, Corinna Vinschen wrote:
On Jun 20 15:07, Ken Brown wrote:
On 6/20/2013 2:42 PM, Corinna Vinschen wrote:
On Jun 20 12:10, Ken Brown wrote:
I'm giving four separate wget commands below to make it clear what's happening:
On Jun 21 07:49, Ken Brown wrote:
On 6/21/2013 7:02 AM, Corinna Vinschen wrote:
Hi Ken,
Something has gone wrong with your TexLive update. Upset produces
thie following report every five minutes:
upset: *** setup.ini: warning - package
texlive-collection-documentation-polish
requires
On 6/21/2013 7:49 AM, Ken Brown wrote:
On 6/21/2013 7:02 AM, Corinna Vinschen wrote:
Hi Ken,
On Jun 20 21:16, Corinna Vinschen wrote:
On Jun 20 15:07, Ken Brown wrote:
On 6/20/2013 2:42 PM, Corinna Vinschen wrote:
On Jun 20 12:10, Ken Brown wrote:
I'm giving four separate wget commands
On Fri, Jun 21, 2013 at 09:26:38AM +, d_h...@hotmail.com wrote:
You need to build with the newest version of mingw from the
mingw64-i686 package. It seems like yours is out of date. Corinna and
I build with the i686-w64-mingw32 target.
It appears I have the latest version (gcc, g++,
Marco,
I'm trying to update emacs-auctex, but you're the owner of
/sourceware/ftp/pub/cygwin/64bit/release/TeX/emacs-auctex, and the
cygwin group doesn't have write permission on the directory or its
files. Could you fix this?
Thanks.
Ken
Il 6/21/2013 4:26 PM, Ken Brown ha scritto:
Marco,
I'm trying to update emacs-auctex, but you're the owner of
/sourceware/ftp/pub/cygwin/64bit/release/TeX/emacs-auctex, and the
cygwin group doesn't have write permission on the directory or its
files. Could you fix this?
Thanks.
Ken
changed
On 17/06/2013 07:48, marco atzeri wrote:
Il 6/16/2013 4:51 PM, marco atzeri ha scritto:
testing a octave/fltk graphics issue, I noticed that also the
demo of fltk with GL interface has a similar issue.
Thanks for reporting this and thanks for providing the test binaries.
On
On 10/06/2013 22:39, David Stacey wrote:
On 10/06/13 14:30, Jon TURNEY wrote:
On 09/06/2013 19:59, David Stacey wrote:
I am trying to package keepassx for 64-bit Cygwin, and have noticed a
difference between the way the clipboard functions under 32-bit and 64-bit
Cygwin/X. Essentially,
Jon TURNEY jon.tur...@dronecode.org.uk writes:
On 19/06/2013 22:27, J. David Boyd wrote:
I can get my capslock key to be super with the command line 'setxkbmap
-option
caps:super', but I can't get 'setxkbmap -option altwin:hyper_win' to do
anything.
Running 'setxkbmap -print' shows both
On 21/06/13 13:33, Jon TURNEY wrote:
On 10/06/2013 22:39, David Stacey wrote:
On 10/06/13 14:30, Jon TURNEY wrote:
On 09/06/2013 19:59, David Stacey wrote:
I am trying to package keepassx for 64-bit Cygwin, and have noticed a
difference between the way the clipboard functions under 32-bit
CVSROOT:/cvs/src
Module name:src
Changes by: cori...@sourceware.org 2013-06-21 08:14:26
Modified files:
winsup/cygwin : ChangeLog path.cc path.sgml
Log message:
* path.cc (cygwin_conv_path): Handle NULL from path gracefully.
* path.sgml
The following statement:
char * tmp_path =
(char *) cygwin_create_path (CCP_POSIX_TO_WIN_A, newargz[0]);
Results in this error popup (and a coredump), when newargz[0] is NULL.
Sure, it's a bug in my program to do that...but shouldn't it be handled
more gracefully? Like...return a NULL,
On Jun 20 18:56, Jeffrey Altman wrote:
On 6/20/2013 6:31 PM, Nogin, Aleksey wrote:
Jeffrey Altman wrote:
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue:
publickey,gssapi-with-mic,password
debug1: Next
On Jun 20 22:38, Andrew Schulman wrote:
If every maintainer would use cygport, it would allow us to change
the build method to one along the lines of most Linux distros.
In Linux distros, the maintainer provides only the spec file and
the source archive. The actual build for all
Hello,
I have been experiencing problems with building several unrelated
projects on Cygwin/Windows 7. One of them is GCC 4.8.1, another is a
project that uses CMake to create the Makefiles. The problems occur
either during the configuration
(the CMake-based project) or during the make itself
On Jun 21 03:26, Charles Wilson wrote:
The following statement:
char * tmp_path =
(char *) cygwin_create_path (CCP_POSIX_TO_WIN_A, newargz[0]);
Results in this error popup (and a coredump), when newargz[0] is
NULL. Sure, it's a bug in my program to do that...but shouldn't it
be
On Jun 21 00:39, Jean-Pierre Flori wrote:
Dear all,
First thanks a lot for your hard work on the Cygwin project and the
Cygwin64 project.
I've begun to try to build Sage (http://www.sagemath.org) on Cygwin64
to provide some Windows support without the need of a virtual machine
running
On Jun 21 10:05, Arjen Markus wrote:
Hello,
I have been experiencing problems with building several unrelated
projects on Cygwin/Windows 7. One of them is GCC 4.8.1, another is a
project that uses CMake to create the Makefiles. The problems occur
either during the configuration
(the
On Jun 21 10:30, Corinna Vinschen wrote:
On Jun 21 00:39, Jean-Pierre Flori wrote:
[...]
/bin/sh ../libtool --tag=CC--mode=link gcc -std=gnu99 -m64 -O2
-march=corei7-avx -mtune=corei7-avx-o t-bswap.exe t-bswap.o
Uhm, are you sure this arch and tune options aren't the problem
Hey,
Thanks for the quick reply.
Le Fri, 21 Jun 2013 10:30:39 +0200, Corinna Vinschen a écrit :
/bin/sh ../libtool --tag=CC--mode=link gcc -std=gnu99 -m64 -O2
-march=corei7-avx -mtune=corei7-avx-o t-bswap.exe t-bswap.o
Uhm, are you sure this arch and tune options aren't the
On Jun 21 09:27, Jean-Pierre Flori wrote:
Hey,
Thanks for the quick reply.
Le Fri, 21 Jun 2013 10:30:39 +0200, Corinna Vinschen a écrit :
/bin/sh ../libtool --tag=CC--mode=link gcc -std=gnu99 -m64 -O2
-march=corei7-avx -mtune=corei7-avx-o t-bswap.exe t-bswap.o
Uhm, are
Cygwin's TeX Live packages have been updated to the latest upstream
release, TeX Live 2013.
TeX Live provides a comprehensive, cross-platform TeX system. It
includes all the major TeX-related programs, macro packages, and fonts
that are free software, including support for many languages
I have a small testcase, but my replies are consistently refused.
How do I solve that?
Regards,
Arjen
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
On Jun 21 13:00, Arjen Markus wrote:
I have a small testcase, but my replies are consistently refused.
How do I solve that?
The reason should be given in the reply you get. Basically, don't
use raw email addresses in your body, don't use html.
Corinna
--
Corinna Vinschen
Well, I got a message back about using too many keywords that made it look like
an off-topic reply. But without an indication (of course) of what
these keywords are.
Regards,
Arjen
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Trying again:
- Unpack the tar file in a separate directory, say, and create a work
directory in which
to configure and build it, something like:
src/ - contents of the tar-file
work/ - directory to work in
CMakeLists.txt - the main CMake file
- Run CMake in the work
Hi Chuck, Hi Yaakov,
as our resident autotools/libtool experts, could you please have a
look here?
On Jun 21 11:43, Corinna Vinschen wrote:
On Jun 21 09:27, Jean-Pierre Flori wrote:
Hey,
Thanks for the quick reply.
Le Fri, 21 Jun 2013 10:30:39 +0200, Corinna Vinschen a écrit :
On Jun 21 13:18, Arjen Markus wrote:
Trying again:
- Unpack the tar file in a separate directory, say, and create a work
directory in which
to configure and build it, something like:
src/ - contents of the tar-file
work/ - directory to work in
CMakeLists.txt - the
Here it is.
Regards,
Arjen
problem-cygwin.tgz
Description: GNU Zip compressed data
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
On Jun 20 09:46, Corinna Vinschen wrote:
On Jun 19 23:31, Matt D. wrote:
I've been looking further into this and it appears as though the
problem is in 'patch' not 'quilt'. quilt is actually a collection of
bash scripts and calls patch to do the actual patching.
Using the same example
On Jun 21 13:40, Arjen Markus wrote:
Here it is.
Regards,
Arjen
Is the tar file broken?
$ tar xvzf problem-cygwin.tgz
src/
src/CMakeLists.txt
src/include/
src/include/CMakeLists.txt
src/include/gnulliver.h.in
CMakeLists.txt
tar: A lone zero block at 11
$ mkdir work
$
Oops, my mistake. The correct invocation of CMake is:
cmake -G Unix Makefiles ../
(These generators are part of CMake, not of the tar file)
Regards,
Arjen
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On Jun 21 14:18, Arjen Markus wrote:
Oops, my mistake. The correct invocation of CMake is:
cmake -G Unix Makefiles ../
(These generators are part of CMake, not of the tar file)
Ok, thank you. I never used cmake before so I didn't notice.
Other than that, I have not the problem you're
I noticed that if I use noacl, then I get the correct looking POSIX permissions,
but the Windows permissions make it impossible to use the file.
Try: cat gnulliver.h
I have had the same problem with a package built via autotools, so it
is more general
than CMake. (I first reported this on the
On Jun 21 14:38, Arjen Markus wrote:
I noticed that if I use noacl, then I get the correct looking POSIX
permissions,
but the Windows permissions make it impossible to use the file.
I always use acl as mount option.
Try: cat gnulliver.h
$ pwd
/home/corinna/tmp/cmake/work
$ cat
Hi Corinna,
you seem to have hit the right spot. The parent directories had the
permission --
according to Cygwin, but I could still enter them via cd. Things go
wrong if under Cygwin
a file gets _copied_ via cp or something similar that takes the file
permissions according
to POSIX from the
Le Fri, 21 Jun 2013 11:43:44 +0200, Corinna Vinschen a écrit :
On Jun 21 09:27, Jean-Pierre Flori wrote:
Hey,
Thanks for the quick reply.
Le Fri, 21 Jun 2013 10:30:39 +0200, Corinna Vinschen a écrit :
/bin/sh ../libtool --tag=CC--mode=link gcc -std=gnu99 -m64 -O2
On 6/21/2013 3:43 AM, Corinna Vinschen wrote:
Guys, whatever the problem here is, it needs to be investigated and
potentially implemented by somebody who knows this kerberos/gss-api
stuff. Openssh is built against these libraries and that's it from my
side. If something's missing in openssh
On Jun 21 09:39, Jeffrey Altman wrote:
On 6/21/2013 3:43 AM, Corinna Vinschen wrote:
Guys, whatever the problem here is, it needs to be investigated and
potentially implemented by somebody who knows this kerberos/gss-api
stuff. Openssh is built against these libraries and that's it from my
The following package has been updated in the 32-bit Cygwin
distribution, and a 64-bit update will follow shortly:
*** emacs-auctex-11.87-2
AUCTeX is an extensible package for writing and formatting TeX files in
GNU Emacs and XEmacs. It supports many different TeX macro packages,
including
On Fri, Jun 21, 2013 at 09:49:34AM +0200, Corinna Vinschen wrote:
On Jun 20 22:38, Andrew Schulman wrote:
If every maintainer would use cygport, it would allow us to change
the build method to one along the lines of most Linux distros.
In Linux distros, the maintainer provides only the
On 6/14/2013 5:39 PM, Nogin, Aleksey wrote:
I am experiencing the same error that Corinna Vinschen have reported on
cygwin-apps mailing list about a year ago without any obvious resolution(*),
and I was wondering whether somebody was able to resolve it since.
I am running Heimdal's kinit
Hi all,
Here is my experience with a shared version of the library after taking
Corinna's message into account, starting from a clean MPIR tarball (except
for updating the FSF config.sub/guess) without autoreconfing, and using
the Cygwin shipped yasm rather than the one included in MPIR (in
Thank you. I took the time to make certain that I couldn't find any
other lingering problems.
The update to 2.7.1 corrects the test case I submitted previously.
Thanks! :)
On 6/21/2013 8:11 AM, Corinna Vinschen wrote:
On Jun 20 09:46, Corinna Vinschen wrote:
On Jun 19 23:31, Matt D. wrote:
Le Fri, 21 Jun 2013 16:56:23 +, Jean-Pierre Flori a écrit :
And the bad news is: tests still segfault.
I'll also check with the static library now.
With the same changes but trying a static lib I get to the same point as
for the shared one:
* ld doesn't segfault anymore, so tests
Le Fri, 21 Jun 2013 17:06:03 +, Jean-Pierre Flori a écrit :
I'll also check without assembly optimizations, or lowering gcc
optimization level, etc.
So I'm going to try that now.
If i disable ASM routines by passing MPN_PATH=generic to configure, then
(in the static setting at least) most
On 6/21/2013 10:07 AM, Corinna Vinschen wrote:
To the best of my knowledge the Heimdal developers have not been
contacted by the Cygwin Heimdal package maintainer.
Well, if it builds...
We are discussing security software that must integrate with the native
environment. When MIT or Heimdal
I've had Cygwin installed on this computer for over two years
without any problems but recently I've started seeing a few problems
and my installation seems corrupted.
1. Starting several weeks ago, whenever I run setup.exe I get this
pop-up message part way through the process.
On 2013-06-21 06:33, Corinna Vinschen wrote:
as our resident autotools/libtool experts, could you please have a
look here?
The problem is, as a fork of GMP, it too tries to be too clever with
libtool in an attempt to shorten configure times by avoiding the CXX/F77
checks. Those hacks are
On 6/20/2013 12:10, Corinna Vinschen wrote:
If every maintainer would use cygport, it would allow us to change
the build method to one along the lines of most Linux distros.
In Linux distros, the maintainer provides only the spec file and
the source archive. The actual build for all
Le Fri, 21 Jun 2013 17:27:22 +, Jean-Pierre Flori a écrit :
Le Fri, 21 Jun 2013 17:06:03 +, Jean-Pierre Flori a écrit :
I'll also check without assembly optimizations, or lowering gcc
optimization level, etc.
So I'm going to try that now.
If i disable ASM routines by passing
On 6/21/2013 12:05, Warren Young wrote:
On 6/20/2013 12:10, Corinna Vinschen wrote:
If every maintainer would use cygport, it would allow us to change
the build method to one along the lines of most Linux distros.
In Linux distros, the maintainer provides only the spec file and
the
I have a BAT file that calls a bash script that generates the
following (edited):
cygwin warning:
MS-DOS style path detected: XXX
Preferred POSIX equivalent is: XXX
CYGWIN environment variable option nodosfilewarning turns off this warning.
Consult the user's guide for more details about
On 2013-06-21 13:10, Warren Young wrote:
On 6/21/2013 12:05, Warren Young wrote:
With cygport, you wouldn't even need to provide sources. We could email
in the new cygport file instead of an RFU.
...and patches.
...and customized .hint files, if needed.
Yeah, I guess sending the
On 6/21/2013 2:38 PM, Nellis, Kenneth wrote:
I have a BAT file that calls a bash script that generates the
following (edited):
cygwin warning:
MS-DOS style path detected: XXX
Preferred POSIX equivalent is: XXX
CYGWIN environment variable option nodosfilewarning turns off this warning.
From: Larry Hall (Cygwin)
On 6/21/2013 2:38 PM, Nellis, Kenneth wrote:
I have a BAT file that calls a bash script that generates the
following (edited):
cygwin warning:
MS-DOS style path detected: XXX
Preferred POSIX equivalent is: XXX
CYGWIN environment variable option
On Fri, Jun 21, 2013 at 09:49:34AM +0200, Corinna Vinschen wrote:
On Jun 20 22:38, Andrew Schulman wrote:
If every maintainer would use cygport, it would allow us to change
the build method to one along the lines of most Linux distros.
In Linux distros, the maintainer provides
On Fri, Jun 21, 2013 at 04:03:46PM -0400, Andrew Schulman wrote:
On Fri, Jun 21, 2013 at 09:49:34AM +0200, Corinna Vinschen wrote:
On Jun 20 22:38, Andrew Schulman wrote:
If every maintainer would use cygport, it would allow us to change the
build method to one along the lines of most Linux
On 6/21/2013 9:19 AM, Arjen Markus wrote:
Hi Corinna,
you seem to have hit the right spot. The parent directories had the
permission --
according to Cygwin, but I could still enter them via cd. Things go
wrong if under Cygwin
a file gets _copied_ via cp or something similar that takes the
On 6/21/2013 3:47 PM, Nellis, Kenneth wrote:
From: Larry Hall (Cygwin)
On 6/21/2013 2:38 PM, Nellis, Kenneth wrote:
I have a BAT file that calls a bash script that generates the
following (edited):
cygwin warning:
MS-DOS style path detected: XXX
Preferred POSIX equivalent is: XXX
Le Fri, 21 Jun 2013 18:07:00 +, Jean-Pierre Flori a écrit :
Le Fri, 21 Jun 2013 17:27:22 +, Jean-Pierre Flori a écrit :
Le Fri, 21 Jun 2013 17:06:03 +, Jean-Pierre Flori a écrit :
I'll also check without assembly optimizations, or lowering gcc
optimization level, etc.
So I'm
Le Fri, 21 Jun 2013 22:10:15 +, Jean-Pierre Flori a écrit :
Now there is also a x86_64w dir for windows assembly but yasm does not
like its syntax.
I'll be looking into that.
In fact its not yasm which is used I guess.
We should indeed use the *w directories and basically do quite
On 06/21/2013 02:11 PM, Larry Hall (Cygwin) wrote:
On 6/21/2013 3:47 PM, Nellis, Kenneth wrote:
From: Larry Hall (Cygwin)
On 6/21/2013 2:38 PM, Nellis, Kenneth wrote:
I have a BAT file that calls a bash script that generates the
following (edited):
cygwin warning:
MS-DOS style path
Cygwin's TeX Live packages have been updated to the latest upstream
release, TeX Live 2013.
TeX Live provides a comprehensive, cross-platform TeX system. It
includes all the major TeX-related programs, macro packages, and fonts
that are free software, including support for many languages
The following package has been updated in the 32-bit Cygwin
distribution, and a 64-bit update will follow shortly:
*** emacs-auctex-11.87-2
AUCTeX is an extensible package for writing and formatting TeX files in
GNU Emacs and XEmacs. It supports many different TeX macro packages,
including
71 matches
Mail list logo
