This release simply changes the libexpat1-devel package name to
libexpat-devel, so that it upgrades correctly if the Expat ABI ever changes.
This change should be transparent. It will happen for anyone with
libexpat1-devel installed on running setup.exe after your chosen mirror
updates.
--
On 7/31/2013 17:54, Linda Walsh wrote:
Warren Young wrote:
Just to emphasize: if both 32- and 64-bit Cygwin bin dirs are in your
PATH at the same time, you will get complaints in the terminal window
--
Ok, but would it be desirable (or wouldn't it be)
to have only 1 /etc, /var, /home?
Warren Young wrote:
On 7/26/2013 23:44, marco atzeri wrote:
Il 7/27/2013 7:17 AM, Kenneth Wolcott ha scritto:
I guess I will somehow modify my PATH so that I have
/cygdrive/c/cygwin64/usr/bin and /cygdrive/c/cygwin32/usr/bin
mixing will not work as the dll's are called in the same way
J
On 2013-07-31 16:56, Warren Young wrote:
On 7/30/2013 21:48, Yaakov (Cygwin/X) wrote:
* Implemented [PKG_]OBSOLETES.
It appears to function as expected for expat. Thanks!
Sorry for not getting around to testing it before release.
Don't worry, I have already put it to good use. :-)
Yaako
On 7/30/2013 21:48, Yaakov (Cygwin/X) wrote:
* Implemented [PKG_]OBSOLETES.
It appears to function as expected for expat. Thanks!
Sorry for not getting around to testing it before release.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq
On 2013-07-31 19:59,marco atzeri wrote:
Il 7/31/2013 7:57 PM, tipot ozen ha scritto:
On 2013-07-31 11:44,yaakov wrote:
On 2013-07-31 11:08, tipot ozen wrote:
Recently, i have encountered the need to check the
validity of the
default utilities that
On 31/07/2013 05:10, Kenneth Wolcott wrote:
Here's the error during the install:
Package: Unknown package
brltty.sh exit code 1
Here's the pertinent line in the /var/log/setup.log.full:
2013/07/30 20:56:03 running: C:\cygwin32\bin\bash.exe --norc
--noprofile "/etc/postinstall/brltty.s
The following packages have been updated for both arches:
* poppler-0.22.5-1
* libpoppler37-0.22.5-1
* libpoppler-devel-0.22.5-1
* libpoppler-cpp0-0.22.5-1
* libpoppler-cpp-devel-0.22.5-1
* libpoppler-glib8-0.22.5-1
* libpoppler-glib-devel-0.22.5-1
* libpoppler-qt4_4-0.22.5-1
* libpoppler-qt4-dev
The following package has been updated for both arches:
*** bind-9.9.3-P2-1
*** bind-utils-9.9.3-P2-1
ISC BIND is a suite of Domain Name Service (DNS) utilities.
This is an update to the latest upstream release.
--
Yaakov
Cygwin/X
CYGWIN-ANNOUNCE UNSUBSCRIBE INFO
===
Corinna Vinschen wrote:
I can reproduce the effect, and it looks like this is the result of
an accidental checkin. Thanks for the hint.
???
Is it?
AFAIK, you can no longer safely paste code into the bash command line
because the TAB char is the default completion character.
If your co
I've made a new version of the gdb debugger available for installation
on both x86 and x86_64 platforms. This version is a refresh from the
main branch of the CVS repository on sourceware.org.
This version also has some as-yet-unsubmitted fixes for Cygwin signal
handling.
*** CYGWI
At 06:31 PM 7/31/2013 +, Stephan Mueller wrote:
>Yeah, I can see your viewpoint here. Christopher
>is known for being brusque at times. And you may
>have, no doubt accidentally, pushed a hot button
>for this particular community.
>
>For what it's worth, the Cygwin folks do prefer
>that people
On 2013-07-31 12:37, Enrico Ferrero wrote:
When trying to install your Rcpp R package from CRAN on Cygwin,
compilation aborts with the following error:
Timer.cpp:35:6: error: #error "Rcpp::Timer not supported by your OS."
Such an error means that the code needs to be patched to select (or add)
I have noticed something in the new 64 bit Cygwin's behavior that may help
people if documented.
I have a Windows Server Datacenter 2003 R2 64-bit machine, and I installed
the new 64 bit Cygwin. I have noticed that if I run bash from the 64 bit
version of cmd.exe, it works fine:
---
>From C:\WI
Il 7/31/2013 7:57 PM, tipot ozen ha scritto:
On 2013-07-31 11:44,yaakov wrote:
On 2013-07-31 11:08, tipot ozen wrote:
Recently, i have encountered the need to check the validity of the
default utilities that installed with cygwin (like grep, find ,etc.)
and i am w
On 2013-07-31 11:44,yaakov wrote:
On 2013-07-31 11:08, tipot ozen wrote:
Recently, i have encountered the need to check the validity of the
default utilities that installed with cygwin (like grep, find ,etc.)
and i am wondering if is there a way to obtain and compare md
Hi Dirk,
When trying to install your Rcpp R package from CRAN on Cygwin,
compilation aborts with the following error:
Timer.cpp:35:6: error: #error "Rcpp::Timer not supported by your OS."
A simple Google search brought up this bug on the Debian bug tracking
system: http://bugs.debian.org/cgi-bin/
Well I uncovered a serious regression
and expressed a willingness to track
down the cause.
However your nasty reply and bad attitude
assures that I will defintiely not help
now.
At 01:21 PM 7/31/2013 -0400, Christopher Faylor wrote:
>You are right in assuming that newer DLLs should
>work with old
On Wed, Jul 31, 2013 at 12:24:32PM -0400, starlight.201...@binnacle.cx wrote:
>Have been running 1.7.16 for some time and living with the annoying
>CTRL-C hang bug.
>
>Tried swapping in cygwin1.dll cyglsa.dll and cyglsa64.dll from 1.7.22-1
>without (thankfully) updating the entire CYGWIN release.
>
On 2013-07-31 11:08, tipot ozen wrote:
Recently, i have encountered the need to check the validity of the
default utilities that installed with cygwin (like grep, find ,etc.)
and i am wondering if is there a way to obtain and compare md5
checksum for all of these utilities.
setup*.exe verifies
On 2013-07-31 10:18, Rhadesan wrote:
I am trying to install qt4 via cygwin installer. I need only very
small subset of qt, such as qmake and qtest framework.
http://cygwin.com/cgi-bin2/package-grep.cgi?grep=bin%2Fqmake
http://cygwin.com/cgi-bin2/package-grep.cgi?grep=QTest
1) I have selected
Hello,
Have been running 1.7.16 for some time
and living with the annoying CTRL-C hang
bug.
Tried swapping in cygwin1.dll cyglsa.dll
and cyglsa64.dll from 1.7.22-1 without
(thankfully) updating the entire CYGWIN
release.
The 22-1 DLLs fix the CTRL-C problem,
but cause a high-intensity parallel
b
Hello,
I am using cygwin for a long time and i am pretty satisfied.
Recently, i have encountered the need to check the validity of the
default utilities that installed with cygwin (like grep, find ,etc.)
and i am wondering if is there a way to obtain and compare md5
checksum for all of these uti
Hello,
I am trying to install qt4 via cygwin installer. I need only very
small subset of qt, such as qmake and qtest framework.
1) I have selected qt4 4.8.4-2 without source code - in Size column
there is '?' - what does it mean?
2) I have done installation, but there is nothing installed (i.e. I
On 7/31/2013 10:11 AM, Corinna Vinschen wrote:
On Jul 31 09:08, Charles Wilson wrote:
FAIL: t/tap-signal.tap 5 - TAP driver catch test termination by
signal SIGQUIT
Hmm.
$ cat
In another shell:
$ ps
PIDPPIDPGID WINPID TTY UIDSTIME COMMAND
5682
On 29/07/2013 3:27 PM, Ryan Johnson wrote:
On 29/07/2013 3:13 PM, Ryan Johnson wrote:
On 29/07/2013 3:11 PM, Corinna Vinschen wrote:
On Jul 29 12:01, Ryan Johnson wrote:
On 29/07/2013 7:06 AM, Corinna Vinschen wrote:
On Jul 27 11:30, Daniel Brown wrote:
I have also ran into this problem, in
On Jul 31 17:26, Pavel Fedin wrote:
> Hello!
>
> > s/svn/cvs/
> >
> > You can rebuild the lib, just update to the latest.
>
> Thank you, tested and works fine. Testing included:
>
> 1. Accessing existing directories then ..
> 2. Accessing nonexistent directories then ..
> 3. Going beyond the r
On Jul 31 09:08, Charles Wilson wrote:
> I was running the automake-1.12 test suite, and found a difference
> in behavior between the two cygwin's. On 32bit, it appears to miss
> the SIGQUIT signal:
>
>
> == 32 bit ==
> PASS: t/tap-signal.tap 1 - "make check" fails
> FAIL: t/tap-
Hello!
> s/svn/cvs/
>
> You can rebuild the lib, just update to the latest.
Thank you, tested and works fine. Testing included:
1. Accessing existing directories then ..
2. Accessing nonexistent directories then ..
3. Going beyond the root multiple times (/../../../../../..)
4. The same, but w
On 2013-07-31 00:41, Christian Franke wrote:
Cygport 0.13.0 (and 0.12.2) adds a bogus "requires: ...
cygwin64-gcc-core ..." to setup.hint when cross-compiling for x86_64.
I suppose it would. The problem here is that the libgcc1 DLL has
different names on each arch due to the added -seh on x86
I was running the automake-1.12 test suite, and found a difference in
behavior between the two cygwin's. On 32bit, it appears to miss the
SIGQUIT signal:
== 32 bit ==
PASS: t/tap-signal.tap 1 - "make check" fails
FAIL: t/tap-signal.tap 2 - count of test results
PASS: t/tap-sig
On 7/30/2013 11:48 PM, Yaakov (Cygwin/X) wrote:
* The gnuconfigize function for replacing config.{guess,sub} is now
public, and is called by all relevant *autoreconf functions.
As soon as all the test suites finish, I'll be publishing updated
versions of ALL of the automake* packages (for both
When I click on cygwin's mintty icon, which is installed by setup.exe and is,
basically a
link which invokes mintty as:
C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico -
I then start X11 by running $ startx & from this 1st initial mintty window.
Objective. I want to have 'start
On 7/31/2013 19:49, Corinna Vinschen wrote:
> On Jul 31 19:31, JonY wrote:
>> On 7/31/2013 18:47, Corinna Vinschen wrote:
>>> Erm... hang on. On second thought, I'm not sure that this is a bug.
>>> The actual bug here was clearly in the Cygwin utils Makefile.
>>>
>>> In fact, since w32api should o
On Jul 31 16:02, Pavel Fedin wrote:
> Hello!
>
> > I applied a patch which skips testing / or // when a /.. or //.. has
> > been encountered. Can you please give it a try?
>
> Where can i get it ? In svn ? I cannot rebuild the library...
s/svn/cvs/
You can rebuild the lib, just update to the
Hello!
> I applied a patch which skips testing / or // when a /.. or //.. has
> been encountered. Can you please give it a try?
Where can i get it ? In svn ? I cannot rebuild the library...
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
Problem repo
On Jul 31 19:31, JonY wrote:
> On 7/31/2013 18:47, Corinna Vinschen wrote:
> > Erm... hang on. On second thought, I'm not sure that this is a bug.
> > The actual bug here was clearly in the Cygwin utils Makefile.
> >
> > In fact, since w32api should only be used by Cygwin executables, why
> > sho
On 7/31/2013 18:47, Corinna Vinschen wrote:
> On Jul 31 12:28, Corinna Vinschen wrote:
>> On Jul 31 18:13, JonY wrote:
>>> On 7/31/2013 17:59, Corinna Vinschen wrote:
On Jul 31 12:55, Pavel Fedin wrote:
> /usr/x86_64-w64-mingw32/sys-root/mingw/lib/../lib/crt2.o: In function
> `__tmainC
Hi there,
I've mailed this to cygwin-ports-general on 2013-01-23, and
got it confirmed, but today realized this bug does still
persist. Since I now know that libpango is part of the basic
Cygwin package, I'll report it here, again:
The libpango1.0 postinstall script fails with exit code 1.
Some
On Jul 31 12:28, Corinna Vinschen wrote:
> On Jul 31 18:13, JonY wrote:
> > On 7/31/2013 17:59, Corinna Vinschen wrote:
> > > On Jul 31 12:55, Pavel Fedin wrote:
> > >> /usr/x86_64-w64-mingw32/sys-root/mingw/lib/../lib/crt2.o: In function
> > >> `__tmainCRTStartup':
> > >> /usr/src/debug/mingw64-x8
On Jul 31 18:13, JonY wrote:
> On 7/31/2013 17:59, Corinna Vinschen wrote:
> > On Jul 31 12:55, Pavel Fedin wrote:
> >> Hello!
> >>
> >> I have occasionally found a little problem in path check code. Attempt to
> >> reference thing like '/..' fails, however at least under Linux this
> >> resolve
On Jul 31 12:55, Pavel Fedin wrote:
> Hello!
>
> I have occasionally found a little problem in path check code. Attempt to
> reference thing like '/..' fails, however at least under Linux this resolves
> to root, and you can actually attempt to go past-root as many times as you
> want, e. g. '/.
On 7/31/2013 17:59, Corinna Vinschen wrote:
> On Jul 31 12:55, Pavel Fedin wrote:
>> Hello!
>>
>> I have occasionally found a little problem in path check code. Attempt to
>> reference thing like '/..' fails, however at least under Linux this resolves
>> to root, and you can actually attempt to g
On Jul 31 12:55, Pavel Fedin wrote:
> Hello!
>
> I have occasionally found a little problem in path check code. Attempt to
> reference thing like '/..' fails, however at least under Linux this resolves
> to root, and you can actually attempt to go past-root as many times as you
> want, e. g. '/.
Hello!
I have occasionally found a little problem in path check code. Attempt to
reference thing like '/..' fails, however at least under Linux this resolves
to root, and you can actually attempt to go past-root as many times as you
want, e. g. '/../../../..'. The bug was occasionally revealed b
On Jul 31 08:37, Denis Excoffier wrote:
> Hello,
>
> Starting with the 20130726 snapshot, i have problems with the
> clipboard.
> Not the clipboard itself, but the capability to paste into the shell
> in order to execute a command containing several lines (or several
> commands).
>
> % cat copypa
46 matches
Mail list logo
