-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
src_prep_init_hook() {
cd ${SRC_DIR}
apply_patch ${origsrcdir}/${PN}-import-xpm.patch
}
Does this work by using CVS HEAD as of Monday night[1], copying this
patch to the topdir, and defining
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov S (Cygwin Ports) wrote:
Eric Blake wrote:
bash ships as a primary tarball (3.1), then has several official patch
files on top of the tarball (bash31-001 through bash31-017), so that bash
3.1.17 is the combination of these. I know that I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Oh, and one other thing:
===
It's my understanding that this change (to std::string) would
constitute an ABI change of the underlying C++/STL runtime library on
cygwin.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm counting down to releasing 0.2.7. cygport developers, please cvs up
and test (especially PATCH_URI).
New features for 0.2.7:
* Use PATCH_URI for upstream or third-party patches; these patches are
included individually in the -src.tar.bz2 and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
Cygport currently makes it impossible to pass arguments to ./configure
that contain a space. I need this for building autogen.
2006-12-12 Eric Blake [EMAIL PROTECTED]
* cygport (cygconf): Preserve shell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jan Nieuwenhuizen wrote:
Changes
* Do not strip .a and .dll.a files, but strip them using -g.
Did you also fix the bogus prefix problem as described in:
http://cygwin.com/ml/cygwin/2006-11/msg00103.html
Your recently uploaded packages are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
And here's number 5 (or 6, depending on how you count). This one adds
the ability to call cygport functions (in addition to the usual
prep/compile/install/ and friends).
And I thought that *I* push cygport to the limits!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In September 2005[1], Corinna asked to postpone including giflib in the
distro until after all known LZW patents had expired. According to the
GNU website[2], this has already occurred. May I now proceed with
ITPing it?
[1]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcus Brinkmann wrote:
I gave it another look, and it seems to me that the problem could be
the following: GPGME tries to build versions of GPGME linking against
pthread and pth. These versions are built from a version of the
library without any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
Four different patchsets. They should all apply independently with only
minor fuzz. I know you're too busy at the moment, Yaakov (congrats!),
to review these patches -- I just wanted to update them to latest
cygport CVS so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake wrote:
Thanks. That hack to the Makefile seems better to me than hacking
cygport. I'll have to report that upstream.
I doubt that upstream will take the INSTALLDIRS=vendor part of the patch
as is, since different distros surely have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually, that isn't all that is needed, since git creates
/usr/lib/perl5/site_perl/5.8/cygwin/auto/Git/.packlist, and that .packlist
also needs the same treatment. Maybe I need to figure out how to make git
use PERL_VENDORLIB, instead of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
Yaakov S (Cygwin Ports) wrote:
autoconf-2.60 needs a patch to fix AC_PATH_XTRA (XrmInitialize is
defined in libX11, not libXt), see below.
Thanks for the heads up. I'll look into it over the weekend.
Ping?
Yaakov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
Gerritt -- can you update the gtk* packages to 2.10.x?
Actually GNOME is mine now; I updated the non-GUI libs a while ago,
thinking that the GUI would not be far behind, but I hit a snag.
A while ago I started working on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan Nieuwenhuizen wrote:
The .la files are needed at runtime if client code uses libtool's
libltdl's dlopen'ing to access the shared library.
For example, try readline activation code in guile without it's .la
or try dlopening fontconfig, ftm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wynfield Henman wrote:
How can I get the patch, mentioned above, i.e.,
ports/apps/imagemagick/ImageMagick-6.2.9.8-1.src.patch for studying?
I was referring to Cygwin Ports CVS[1], where I maintain the code to
cygport(1) as well as a large
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following package has been updated in the Cygwin net release:
*** cygport-0.2.6-1
cygport is a new, and increasingly popular, way to create Cygwin
packages. You only need cygport if you're a package developer or
building cygport-based Cygwin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following package has been updated in the Cygwin net release:
*** cygport-0.2.6-1
cygport is a new, and increasingly popular, way to create Cygwin
packages. You only need cygport if you're a package developer or
building cygport-based Cygwin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
At present, if you use cvs|svn|git cygclass, you can only have one
SRC_URI. This patch does three related things
These changes were necessary to support building jpeg (using the
autotoolized source package at sourceforge,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Volker Quetschke wrote:
| I had to revert to the previous versions
| because the new version was generating the problems shown below.
|
| I *guess* the problem stems from this entry in /usr/lib/libfontconfig.la
|
| - snip -
| # Directory that this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Volker Quetschke wrote:
| You mean here:
|
ftp://sunsite.dk/projects/cygwinports/release/ImageMagick/ImageMagick-6.2.9.1-1-src.tar.bz2
|
| I don't see it, but I'll fix the problem like you suggest. Don't hold
| your breath, version -2 coming soon ...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Volker Quetschke wrote:
| The only problem is that due to a MakeMaker problem, see
| http://cygwin.com/ml/cygwin/2006-11/msg00024.html
| the build is not completely self contained. An extra patch for
| MM_Unix.pm is needed.
A fix for this is part
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Volker Quetschke wrote:
| When building PerlMagick from ImageMagick 6.3.0.1 the build fails
| with the errorlog shown below.
|
| The problem seems to stem from the wrong order of link switches
| in the MakeMaker generated makefile and can be fixed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
| The attached patch (+ two new files) enables cygport to build
| relocatable packages using the framework devised by Bruno Haible -- if
| the upstream source supports it. Currently, only libiconv and gettext
| support this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles,
autoconf-2.60 needs a patch to fix AC_PATH_XTRA (XrmInitialize is
defined in libX11, not libXt), see below.
Yaakov
* START PATCH *
- --- libs.m4.orig2006-10-26 22:03:30.12825 -0500
+++ libs.m4 2006-10-26
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
Eric Blake wrote:
The check for config_h in cygautoreconf does not work when the
line requests a template by a different name, as is the case with
coreutils 6.4:
$ grep CONFIG_HEADERS coreutils-6.4/configure.ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake wrote:
The check for config_h in cygautoreconf does not work when the line
requests a template by a different name, as is the case with coreutils 6.4:
$ grep CONFIG_HEADERS coreutils-6.4/configure.ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
The attached patch (+ two new files) enables cygport to build
relocatable packages using the framework devised by Bruno Haible -- if
the upstream source supports it. Currently, only libiconv and gettext
support this feature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following package has been updated in the Cygwin net release:
*** cygport-0.2.5-1
cygport is a newer, and increasingly popular, way to create Cygwin
packages. More information is contained in the README, and a tutorial
at the URL below.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
Here's the problem: libtool (pre-version 2.0) ships with a subproject --
separately configured -- called libltdl. However, the subproject does
NOT include the GNU required files like README, AUTHORS, etc. Those
are all up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
CVS cygport now has support for the following:
* autoconf-2.60;
* mirror:// URIs;
* Apache2 .so modules;
* git snapshots;
* mono and Gtk#;
* AC_CONFIG_SUBDIRS autoreconf handling.
Now that Charles has released autoconf-2.60, I need to roll a new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vin Shelton wrote:
Have you had a chance to look at my patch which allows over-riding the
individual configure arguments in cygconf()? The patch is a
definitely a brute force approach, but something like it is necessary
to support XEmacs (or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
For most purposes, this is transparent. You run autoconf which is the
wrapper, and you get the right version. However, cygport explicitly
tests for the presence of autoconf-2.5x in $PATH.
This patch makes cygport's search
Eric Blake wrote:
bash ships as a primary tarball (3.1), then has several official patch
files on top of the tarball (bash31-001 through bash31-017), so that bash
3.1.17 is the combination of these. I know that I can add the patch files
to the SRC_URI in my .cygport file, but how do I apply
The following package has been updated in the Cygwin net release:
*** cygport-0.2.4-1
New features since 0.2.2-1:
* Zero-byte patches are not included in the -src tarball.
* localstatedir defaults to /var, with the exception of gnome2 packages
which require /var/lib for compatibility with
The following package has been updated in the Cygwin net release:
*** cygport-0.2.4-1
New features since 0.2.2-1:
* Zero-byte patches are not included in the -src tarball.
* localstatedir defaults to /var, with the exception of gnome2 packages
which require /var/lib for compatibility with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Buchbinder, Barry (NIH/NIAID) [E] wrote:
I do not meaning to bug the maintainer, request an update, or imply that
the maintainer is not paying attention to the canonical site, but in
case the maintainer just hasn't noticed ...
These are also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harold L Hunt II wrote:
I guess it is safe to say that I will not be able to maintain complex
Cygwin packages anymore. Thus, I am letting go of the following (from
the maintainer's list posted in 2003-11
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
Hello,
I working with cygwin installed from www.cygwin.com and glade installed
from gladewin32.sourceforge.net
That's your problem. GladeWin32 is meant for native Win32 apps and is
not intended for use with Cygwin. You
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Seidel wrote:
Yep, you're right. I installed it and now it seems to work better.
It just failed because of a missing __isnand function in libm. Afer
providing (only as a workaround) my own it works flawlessly.
__isnand *is* in the current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reini Urban wrote:
BTW: I wonder if people want wv, htmldoc and antiword also.
I have wv and wv2 in Cygwin Ports CVS, under ports/libs/{wv,wv2}, so if
you want to maintain them (fine with me), I'll at least save you the work.
Yaakov
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Seidel wrote:
$ g++ -H -g -O2 -I/usr/X11R6/include main.cpp -lglut
. /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/GL/glut.h
The references to w32api/GL are probably wrong!
Once I omit -I/usr/X11R6/include (or use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor Peshansky wrote:
As Reini rather forcefully alluded to, using ':' in filenames is
non-portable. You really should complain upstream about using that
character in their filenames. The standard Perl convention is to replace
'::' by '_',
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
cgf,
objdump from binutils-20060709-1 does absolutely nothing; even running
objdump without any arguments, which in 20050610-1 returns the help
message, also does nothing. Of course, this breaks building shared
libraries with libtool, which is how I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joseph H Allen wrote:
http://world.std.com/~jhallen/setup.hint
http://world.std.com/~jhallen/joe-3.5-1-src.tar.bz2
http://world.std.com/~jhallen/joe-3.5-1.tar.bz2
Uploaded; please remember to send an announcement to cygwin-announce.
Yaakov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In pngrutil.c, the function png_decompress_chunk() allocates
insufficient space for an error message, potentially overwriting stack
data, leading to a buffer overflow.
Solution: update libpng10 to 1.0.20 and libpng12 to 1.2.12
More information:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
Yaakov S (Cygwin Ports) wrote:
Multiple vulnerabilities, ranging from integer overflows and NULL
pointer dereferences to double frees, were reported in libTIFF.
And now, there's more:
A buffer overflow has been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following package has been updated in the Cygwin net release:
*** gvim-7.0.035-1
gvim provides a GTK2 GUI interface to the vim text editor. It requires
vim-7.0.x for the common runtime files.
Yaakov
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following packages have been updated in the Cygwin distribution:
*** libpcre0-6.6-1
*** pcre-6.6-1
*** pcre-devel-6.6-1
*** pcre-doc-6.6-1
The PCRE library is a set of functions that implement regular expression
pattern matching using the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following package has been updated in the Cygwin net release:
*** netpbm-10.33-1
Netpbm is a toolkit for manipulation of graphic images, including
conversion of images between a variety of different formats. There
are over 220 separate tools in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following package has been updated in the Cygwin net release:
*** cygport-0.2.2-1
cygport is a new way to create Cygwin packages. More information is
contained in the README, and a tutorial at the URL below.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following package has been updated in the Cygwin net release:
*** gvim-7.0.035-1
gvim provides a GTK2 GUI interface to the vim text editor. It requires
vim-7.0.x for the common runtime files.
Yaakov
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following package has been updated in the Cygwin net release:
*** netpbm-10.33-1
Netpbm is a toolkit for manipulation of graphic images, including
conversion of images between a variety of different formats. There
are over 220 separate tools in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following packages have been updated in the Cygwin distribution:
*** libpcre0-6.6-1
*** pcre-6.6-1
*** pcre-devel-6.6-1
*** pcre-doc-6.6-1
The PCRE library is a set of functions that implement regular expression
pattern matching using the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following package has been updated in the Cygwin net release:
*** cygport-0.2.2-1
cygport is a new way to create Cygwin packages. More information is
contained in the README, and a tutorial at the URL below.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
Reissuing ITP for gamin.
gamin is in Gentoo stable, Ubuntu dapper, and FC5. Lapo gave this a
GTG, but Corinna seemed to object due to lack of handling FAT drives on NT4.
This package will be required by gnome
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake wrote:
Thanks. By the way, WANT_AUTOCONF was not enough, I had to
export FORCE_AUTOCONF_2_5=yes
OK, but I got errors with automake-1.5; using automake-1.6 worked instead.
Try 2: Dynamic libraries are now built, and separated into
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
Multiple vulnerabilities, ranging from integer overflows and NULL
pointer dereferences to double frees, were reported in libTIFF.
And now, there's more:
A buffer overflow has been found in the t2p_write_pdf_string
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
Solution: update to 3.8.2 and apply the following patches:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/media-libs/tiff/files/tiff-3.8.2-tiffsplit.patch
http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
Eric Blake wrote:
In the process, I discovered that cygport doesn't recognize .asc as
a valid file suffix for a gpg signature. And if there are no source
patches, it would be nicer to not distribute ${P}.src.patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corinna Vinschen wrote:
And while we're at it, the localstatedir should be /var per
http://cygwin.com/setup.html, not /var/lib as is the default
in cygport.
Now fixed in CVS, except that I've overridden this back to /var/lib in
gnome2.cygclass,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake wrote:
Actually, I liked how g-b-s did it better - rather than hardcoding
everything (such as --mandir=/usr/share/man), it followed GNU Coding
Standards (such as --mandir='${prefix}/share/man'), so that I can do 'make
prefix=/my/path'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake wrote:
Right now, I only built it statically (the package has not been maintained
for several years, so it was built with autoconf 2.13 and libtool 1.3.3;
it refuses a VPATH build, and autoreconf gave up). But if there is enough
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
Try the attached cygport file and patch. You'll need to fill in
PKG_HINTS, make the corresponding .hint's, and I won't be too offended
if you don't like my choice of dividing the packages. :-) Depending on
your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake wrote:
I just switched diffstat from g-b-s to cygport, and have to say I was
pretty impressed.
Thanks. :-)
In the process, I discovered that cygport doesn't recognize .asc as
a valid file suffix for a gpg signature. And if there are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Morrison wrote:
Do you want to post the .cygport/patches? I can't promise to help, but
you'll at least stand a better chance of *somebody* helping...
Everything is available in Cygwin Ports CVS, module ports/xorg.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corinna Vinschen wrote:
could you please update the gvim package to vim7, too?
Since gvim expects the global configuration files from the vim package,
people will have a broken gvim configuration when updating vim.
Hmm, I see that gvim is quite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
It seems I will have a nice cozy package-preparing week-end ;-)
(typespeed, rsync, monotone...)
coughgamin/cough :-D
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A buffer overflow has been discovered in the addnewword() function of
Typespeed's network code.
Workaround: Don't run typespeed in multiplayer mode.
Solution: Upgrade to = 0.5.1. (0.5.0 fixed the security bug, but
introduced some functionality
Igor Peshansky wrote:
I thought Yaakov was working on becoming one eventually... This was
mostly a hint to him that he may want to take over the other duties of the
X maintainer... But then, I'm not even sure he's subscribed to this list
yet, so the hint may have been premature.
I am, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
While attempting to package eric3, python (2.4.3-1) just segfaults on
the included install.py script before it can do anything else. This
used to work with cygwin-1.5.18-1 and python-2.4.1-1, and since I've had
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
Multiple vulnerabilities, ranging from integer overflows and NULL
pointer dereferences to double frees, were reported in libTIFF.
Solution: Update to =3.8.1.
More information:
http://www.gentoo.org/security/en
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reini Urban wrote:
Attached is the new version.
No ChangeLog, ... entries.
Incorporated into CVS. Thanks for the patch.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The cygport sources can now be found in the cygwin-ports CVS repository.
Anyone interested in cygport development, work is currently on HEAD;
testers would be welcome.
I'm very close to making a 0.2.2 release before branching and working on
l10n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corinna Vinschen wrote:
Since there hasn't been much movement lately, I tracked which of
Gerrit's packages have been actually taken over. As I see it now,
the following packages remain to be taken over, please correct me
if I missed something:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reissuing ITP for gamin.
gamin is in Gentoo stable, Ubuntu dapper, and FC5. Lapo gave this a
GTG, but Corinna seemed to object due to lack of handling FAT drives on NT4.
This package will be required by gnome-vfs2-2.14.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Max Bowsher wrote:
Sorry, I could have been clearer. The issue is that these are all
library packages, which people could conceivably have self-compiled
stuff depending upon.
I'd like some opinions on how long a real (not empty .tar) version of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Max Bowsher wrote:
Yaakov suggested changing php-apache2 to apache2-php. I countered that
php-apache2 is consistent with the subversion-apache2 we already have,
and that it more useful to have all the possibilities for using PHP
grouped together,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corinna Vinschen wrote:
Did the FAT support make it into this package now? It really wasn't
that complicated, was it?
FAT detection on 2K/XP is supported, and assumed on 9x. FAT detection
on NT4 is still not supported. Lapo was going to work on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Grayson wrote:
There have been no replies to my message below. Does a lack of interest from
this mailing list mean our proposed package is unlikely to be accepted, and
thus I should expend no effort releasing our program in the cygwin format?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As previously mentioned, I have been working on porting the modular
X11R7 to Cygwin. While I have been (AFAICS) successful on the client
side, the server refused to find any fonts, and hence won't start.
Frankly, I'm baffled as to why, since it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Warren Young wrote:
I believe my problems with g-b-s were due to the fact that ctags uses
autoconf only, no automake. Do you know of anyone using cygport with
such a package?
Sure, cygport is designed to be flexible, and I've used cygport for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Multiple vulnerabilities, ranging from integer overflows and NULL
pointer dereferences to double frees, were reported in libTIFF.
Solution: Update to =3.8.1.
More information:
http://www.gentoo.org/security/en/glsa/glsa-200605-17.xml
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reini Urban wrote:
Attached is bash_completion support for cygport. (cygwin only)
Put it into /etc/bash_completion.d/cygport
Maybe it can be added to the package, though it's only useful for cygwin.
I don't use bash_completion myself, but if
Ralf Habacker wrote:
I just downloaded cywin snapshot 2005-06-27 and got running designer and
uic without any problem, so it looks like there is no need to deep
more into this stuff. I will follow the next time if this problems takes
places again.
I can confirm that the 2006-Jun-27 snapshot
Yaakov S (Cygwin Ports) wrote:
I can confirm that the 2006-Jun-27 snapshot (which is what he meant)
fixes the longstanding issues WRT qt3 and company. Thanks to all who
helped figure this out, and I look forward to restarting work on qt3,
qt4, and KDE 3.5 in the near future.
Sigh. That's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charli Li wrote:
There are some newer cygwin packages available from the original vendor(s)
that I would like to bring to your attention:
---
|Package name|setup.exe version|vendor's version|
|GTK+2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teun Burgers wrote:
Attached you find a script gsl-get.sh that fetches the files and
organises them in what I think is the intended directory structure
and renames all the .hints files to setup.hint in the appropriate
directory. After executing of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Tishler wrote:
AFAICT, Cygwin Python uses the normal Python layout.
On Cygwin, we have:
$ ls /usr/lib/python2.4/config
Makefile Setup.config config.c install-sh makesetup
Setup Setup.local config.c.in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
Corinna Vinschen wrote:
That's fine since the existance of reparse points corresponds with
the existance of the GetVolumePathName function. In other words,
if you have to emulate the function, no other volume mount points
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Rossi wrote:
I created a setup.hint for the first time. I don't have a README, is
this required?
Yes, see:
http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/packaging/templates/generic-readme?content-type=text/plaincvsroot=cygwin-apps
Keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Korn wrote:
The one thing I haven't done anything about is making libstdc++ as a dll,
because I don't yet know how. Jim, if you or anyone else can tell me what I
have to do in terms of configure options, I'll have a go; otherwise I'll leave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim O'Callaghan wrote:
FWIW +1
Are you a current package maintainer? You must be in order to vote.
AFAICS this still needs one more vote to be included.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
ftp://sunsite.dk/projects/cygwinports/release/cygport/cygport-0.1.93-1-src.tar.bz2
ftp://sunsite.dk/projects/cygwinports/release/cygport/cygport-0.1.93-1.tar.bz2
ftp://sunsite.dk/projects/cygwinports/release/cygport
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
peter360 wrote:
checking for X... no
configure: error: Mrxvt requires the X Window System libraries and headers.
I read the configure program. Looks like it is trying to find
libXt.{a|so|sl} but failed. I did find libXt.dll.a in my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Tishler wrote:
Done.
Thanks for the nudge. :,)
And thank you for the quick version bump!
BTW, for your next release, would you mind making a
/usr/lib/libpython2.4.dll.a -
/usr/lib/python2.4/config/libpython2.4.dll.a symlink? It would help
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following package has been added to the Cygwin net release:
*** cygport-0.1.93-1
cygport is a brand new way to create Cygwin packages. More
information is contained in the README, and a tutorial at the URL below.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Rossi wrote:
I have a package called CGDB. Do I understand you correctly by
thinking that cygport would help me easily be able to create a cygwin
package?
In the future, please respect the following:
http://cygwin.com/acronyms/#PPIOSPE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following package has been added to the Cygwin net release:
*** cygport-0.1.93-1
cygport is a brand new way to create Cygwin packages. More
information is contained in the README, and a tutorial at the URL below.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
python maintainer,
Could we have an update to python soon? gedit-2.14 requires
PyGC_Collect, but that function was not exported in libpython2.4 until
2.4.3[1].
[1] http://svn.python.org/view?rev=42188view=rev
Yaakov
-BEGIN PGP SIGNATURE-
1 - 100 of 363 matches
Mail list logo
