-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| Looks like a gettext bug to me. Might be fixed in 0.16+, but please
| report upstream.
I'll admit I'm not that fluent in gettext internals. Obviously both
macros are supposed to be present; is having only one just old
behav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| Well, that's not enough information at all. The c++ tests all pass, so
| I'm going to need a testcase or at least the actual project you're
| building that gives this error.
.cygport attached, as well as the diff between the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
+++ libpcre0-7.6-2
+++ pcre-7.6-2
+++ pcre-devel-7.6-2
+++ pcre-doc-7.6-2
This is an upstream version bump. Cygwin-specific changes:
* Patch from Gentoo for libpcrecpp compatibi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following package has been updated in the Cygwin net release:
+++ cygport-0.3.9-1
Overview of changes since 0.3.8:
* UNSTABLE API: src_unpack_hook and src_patch_hook
* Allow multiple postinstall/preremove scripts for split packages.
* Now com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| Yep, looks like that will work -- once 0.3.9 is out. However, the
| inetutils-1.5-3 cygport file *as released* requires a function in
| neither the official cygport-0.3.8 nor the upcoming cygport-0.3.9. So,
| *as released*, i
Yaakov (Cygwin Ports) wrote:
Here's yet another interesting case with libtool-2.2:
"interesting", as in "may you live in interesting times"?
/bin/sh ../../libtool --tag=CXX --mode=link g++ -O2 -pipe-o
libfoo-1.2.la -rpath /usr/lib -no-undefined sources.lo
libtool: link: rm -fr .libs/lib
Yaakov (Cygwin Ports) wrote:
* libtool should catch if the lt-foo.c compile fails;
Yes. I haven't tracked this one down yet.
I think I have also found a separate case of breakage when the CXX tag
is enabled, in which case LTCC is mysteriously undefined. The results:
./libtool: line 7737: -O
Charles Wilson wrote:
Yaakov (Cygwin Ports) wrote:
./.libs/lt-foo.c:263: warning: string length `4368' is greater than the
length `4095' ISO C99 compilers are required to support
This one can be fixed by splitting the string into two pieces. I'm
working on a patch for that.
./.libs/lt-foo.
Yaakov (Cygwin Ports) wrote:
[EMAIL PROTECTED] wrote:
| Building this package requires a patched cygport:
| http://cygwin.com/ml/cygwin-apps/2008-03/msg00139.html
Are you sure? AFAICS the attached WFM; I just need to update cygport in
the distro.
Yep, looks like that will work -- once 0.3.9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[EMAIL PROTECTED] wrote:
| Building this package requires a patched cygport:
| http://cygwin.com/ml/cygwin-apps/2008-03/msg00139.html
Are you sure? AFAICS the attached WFM; I just need to update cygport in
the distro.
Yaakov
-BEGIN PGP SIG
On 4/24/08, Nefastor <[EMAIL PROTECTED]> wrote:
>
>
> Brian Dessent wrote:
> >
> > Nefastor wrote:
> >
> >> (...) I don't know which of Cygwin's /dev/tty device corresponds to which
> >> serial
> >> port on my PC (that is, I only know the COM port number). I can "sort of
> >> guess" /dev/tty0 is CO
The pkg-config program is used to retrieve information about installed
libraries in the system, including the CFLAGS, LDFLAGS, and other
information necessary to compile and link against one or more libraries.
CHANGES since 0.21-1
* update to latest bzr development version
I've updated inetutils, based on the upstream 1.5 release. A short list
of the changes appears below, but the documentation has been extensively
revised. I urge you to read /usr/share/doc/Cygwin/inetutils-1.5.README.
The old README, from inetutils-1.3.2-40, is now located in
/usr/share/doc/ine
Thorsten Kampe wrote:
> * Paul Domaskis (Tue, 22 Apr 2008 16:47:16 -0400) wrote:
>>
>> I will be using a standalone Win2K machine on which I will likely
>> not have admin access. Will this be a problem, if I choose to
>> install only for the account of interest?
>
> No, I use that version exclusi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
Here's yet another interesting case with libtool-2.2:
/bin/sh ../../libtool --tag=CXX --mode=link g++ -O2 -pipe-o
libfoo-1.2.la -rpath /usr/lib -no-undefined sources.lo
libtool: link: rm -fr .libs/libfoo-1.2.dll.a .libs/libfoo-1.2.la
Brian Dessent wrote:
>
> Nefastor wrote:
>
>> (...) I don't know which of Cygwin's /dev/tty device corresponds to which
>> serial
>> port on my PC (that is, I only know the COM port number). I can "sort of
>> guess" /dev/tty0 is COM1, but that's a guess, and I'd prefer some
>> certainty.
>
> C
On Thu, Apr 24, 2008 at 01:41:42PM -0700, Matt Seitz (matseitz) wrote:
>> When compiled out of the box, the upstream git maintainers
>> cater to older cygwin releases, and intentionally disable
>> certain features that have been reported on their mailing
>> list, even though they work with the l
On Thu, Apr 24, 2008 at 05:32:26PM +0200, Math?us Muzalewski wrote:
> Dear community,
>
> I tried to install the Shark library for machine learning from
> http://shark-project.sourceforge.net/ on my windows system using cygwin.
> As known from Linux, I called 'autoconfig' and './configure' to crea
> When compiled out of the box, the upstream git maintainers
> cater to older cygwin releases, and intentionally disable
> certain features that have been reported on their mailing
> list, even though they work with the latest cygwin.
> Therefore, this build turns those features back on.
What
On Thu, Aug 09, 2007 at 01:50:59PM -0700, TomL wrote:
>
> Based on the idea that its a file locking problem, I ran "handle" from
> sysinternals, and it showed up as an open filehandle in an explorer.exe
> process. I terminated the process, and all is well.
>
> I don't understand how it got into
Dear community,
I tried to install the Shark library for machine learning from
http://shark-project.sourceforge.net/ on my windows system using cygwin.
As known from Linux, I called 'autoconfig' and './configure' to create
the Makefile and then 'make libs' to build the library.
Unfortunately it
This is a problem in using of Cygwin-tools on Windows x64, running on VMware.
I'm using Cygwin 1.5.25 on a Windows 2003 Server, 64-bit Standard Edition
running on VMware Workstation ACE Edition, Version 6.0.2. The host system is a
Windows 2003 Server R2 Enterprise x64 Edition, SP2, running on In
* Paul Domaskis (Tue, 22 Apr 2008 16:47:16 -0400)
> I will be using a standalone Win2K machine on which I will likely not
> have admin access. Will this be a problem, if I choose to install
> only for the account of interest?
No, I use that version exclusively on my machines (because I run Cygwin
23 matches
Mail list logo
