RE: New GMP and MPFR packages for review
From: Corinna Vinschen I'm not using this so I can't test. The packaging looks good. But I don't think the gmp package should have libgmp-devel in its requirements. This contradicts the purpose of differing between runtime and devel packages. The devel package should only be pulled if the user explicitely requests it, isn't it? I have fixed the dependencies in the setup.hint files. As these are generated by cygport I also updated the src package (and rebuilt gmp and mpfr as a check). David NOTICE This e-mail and any attachments are private and confidential and may contain privileged information. If you are not an authorised recipient, the copying or distribution of this e-mail and any attachments is prohibited and you must not read, print or act in reliance on this e-mail or attachments. This notice should not be removed.
New GMP and MPFR packages for review
The current cygwin version of gmp is 4.1.4. This also contains an old version of mpfr. The latest version of gmp is 4.2.1 It no longer contains it own version of mpfr. I have packaged gmp-4.2.1 and mpfr-2.2.0. The current gmp maintainer Lapo Luchini is happy for me to offer these for review and take over as maintainer if they are acceptable. There is some discussion from a few months back here http://cygwin.com/ml/cygwin-apps/2006-05/msg00098.html http://cygwin.com/ml/cygwin-apps/2006-05/msg00104.html http://cygwin.com/ml/cygwin-apps/2006-05/msg00111.html As gfortran - the fortran compiler in gcc-4 - uses libgmp3 and libmpfr, it seems sensible to break the monolithic packages into sub-packages. The new cyggmp3.dll is suposed to be binary compatible with the current release, and testing seems to confirm this. The new cygmpfr1.dll is not binary compatible with the current cygmpfr0.dll. I provide a libmpfr0 package that just contains the existing cygmpfr0.dll, and supplies the existing gmp3-4.1.4 src tarball as the src package. http://billinghurst.customer.netspace.net.au/cygwin/gmp/gmp-4.2.1-1-src.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/gmp/gmp-4.2.1-1.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/gmp/setup.hint http://billinghurst.customer.netspace.net.au/cygwin/gmp/libgmp3/libgmp3-4.2.1-1.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/gmp/libgmp3/setup.hint http://billinghurst.customer.netspace.net.au/cygwin/gmp/libgmp-devel/libgmp-devel-4.2.1-1.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/gmp/libgmp-devel/setup.hint http://billinghurst.customer.netspace.net.au/cygwin/mpfr/mpfr-2.2.0-2-src.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/mpfr-2.2.0-2.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/setup.hint http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmpfr-devel/libmpfr-devel-2.2.0-2.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmpfr-devel/setup.hint http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmpfr1/libmpfr1-2.2.0-2.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmpfr1/setup.hint http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmpfr0/libmpfr0-4.1.4-3-src.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmpfr0/libmpfr0-4.1.4-3.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmpfr0/setup.hint NOTICE This e-mail and any attachments are private and confidential and may contain privileged information. If you are not an authorised recipient, the copying or distribution of this e-mail and any attachments is prohibited and you must not read, print or act in reliance on this e-mail or attachments. This notice should not be removed.
RE: [ITP] gmp-4.2 and mpfr-2.2
From: Charles Wilson Billinghurst, David (CALCRTS) wrote: The new cygmpfr1.dll is not binary compatible with the current cygmpfr0.dll. How should this be managed? Should I provide a libmpfr0 package that just contains the existing cygmpfr0.dll? Yes. What I would suggest is the following: Get the current gmp-4.1.4-2 binary package. Unpack usr/bin/cygmpfr-0.dll from it. Package that file into libmpfr0-4.1.4-3.tar.bz2 Get the currrent gmp-4.1.4-2-src source package Rename it libmpfr0-4.1.4-3-src. And there you have it. Sure, downloading and unpacking libmpfr0-4.1.4-3-src and following its build instructions won't get you the exact package libmpfr0-4.1.4-3.tar.bz2 -- but it WILL get you the exact cygmpfr-0.dll -- and that's all that's truly necessary in this case. Done. http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmpfr0/libmpfr0-4.1.4-3.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmpfr0/libmpfr0-4.1.4-3-src.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmpfr0/setup.hint NOTICE This e-mail and any attachments are private and confidential and may contain privileged information. If you are not an authorised recipient, the copying or distribution of this e-mail and any attachments is prohibited and you must not read, print or act in reliance on this e-mail or attachments. This notice should not be removed.
[ITP] gmp-4.2 and mpfr-2.2
The current cygwin version of gmp is 4.1.4. This also contains an old version of mpfr. The latest version of gmp is 4.2. It no longer contains it own vestion of mpfr. I have packaged gmp-4.2 and mpfr-2.2.0. The current gmp maintainer Lapo Luchini is happy for me to offer these for review and take over as maintainer if they are acceptable. As gfortran - the fortran compiler in gcc-4 - uses libgmp3 and libmpfr, it seems sensible to break the monolithic packages into The new cyggmp3.dll is suposed to be binary compatible with the current release, and limited testing confirms this. The new cygmpfr1.dll is not binary compatible with the current cygmpfr0.dll. How should this be managed? Should I provide a libmpfr0 package that just contains the existing cygmpfr0.dll? http://billinghurst.customer.netspace.net.au/cygwin/gmp/gmp-4.2-1-src.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/gmp/gmp-4.2-1.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/gmp/setup.hint http://billinghurst.customer.netspace.net.au/cygwin/gmp/libgmp-devel/libgmp-devel-4.2-1.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/gmp/libgmp-devel/setup.hint http://billinghurst.customer.netspace.net.au/cygwin/gmp/libgmp3/libgmp3-4.2-1.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/gmp/libgmp3/setup.hint http://billinghurst.customer.netspace.net.au/cygwin/mpfr/mpfr-2.2.0-1-src.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/mpfr-2.2.0-1.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/setup.hint http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmfpr-devel/libmfpr-devel-2.2.0-1.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmfpr-devel/setup.hint http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmfpr1/libmfpr1-2.2.0-1.tar.bz2 http://billinghurst.customer.netspace.net.au/cygwin/mpfr/libmfpr1/setup.hint NOTICE This e-mail and any attachments are private and confidential and may contain privileged information. If you are not an authorised recipient, the copying or distribution of this e-mail and any attachments is prohibited and you must not read, print or act in reliance on this e-mail or attachments. This notice should not be removed.
New gmp and mfpr (was RE: Maintainer searched)
From: Dave Korn I'm wondering if Dave Korn or Brian Dessent would consider maintaining gcc? Well I didn't finish rolling the lot over the weekend owing to reasons I'll explain on the talk list, but I'm saying yes anyway. First thing I'll do will be reroll a 3.4.4-2 with the fix for PR-whateveritis about the C++ strings-vs-dlls problem. Once that's done and seems ok, I'll look at making an experimental package from one of the gcc 4 series. (Anyone got any preferences?) I am tempted to punt for 4.2 as a test release. It is now in stage 3, so by the time we shake out any bugs it will be released. gmp and mfpr are required for gfortran. I have packages of gmp-4.2 and mfpr-2.2.0 built and almost ready to go, and am using them for gcc-4.2 test builds I have discussed this off list with Lapo and he is happy for me take over as maintainer. I will try and get something out for review over the weekend. David NOTICE This e-mail and any attachments are private and confidential and may contain privileged information. If you are not an authorised recipient, the copying or distribution of this e-mail and any attachments is prohibited and you must not read, print or act in reliance on this e-mail or attachments. This notice should not be removed.
RE: gcc 3.3.3 builds corrupt lesstif-0.93.94
From: Harold L Hunt II The lesstif package was last built and released (0.93.94) with gcc-3.3.1 (or earlier, not sure). Performing a rebuild of the lesstif source as released (or any lesstif version after that) results in a good build, but one that gives a status access violation *immediately* upon being loaded; that is, DllMain is not even correctly called. Has anyone else ran into libraries that fail to build correctly under gcc-3.3.3? How close are we to another gcc release for Cygwin (I'm hoping this just goes away)? Harold I have seen this with a few packages I have tried to build recently. One case I was looking at this week was octave with a home build shared libstdc++. This used to work for me. I haven't investigated further. David NOTICE This e-mail and any attachments are private and confidential and may contain privileged information. If you are not an authorised recipient, the copying or distribution of this e-mail and any attachments is prohibited and you must not read, print or act in reliance on this e-mail or attachments. This notice should not be removed.
RE: openjade needed (was: Re: [ITP] gtk-doc)
Oh no, it requires openjade.. Is there someone out there who is able to build the current version of openjade / opensp. Gerrit There is http://www.flett.org/archives/2004/06/09/10.49.58/
RE: My pending ITPs 2. update
Package: libwmf-0.2.8.3-1 http://sources.redhat.com/ml/cygwin-apps/2004-06/msg00058.html Votes : 2 From : David [EMAIL PROTECTED] Christopher [EMAIL PROTECTED] This works for me. I have downloaded the source package, built it and installed it. Layout looks OK, but I didn't look really closely. wmf2x wmf2eps wmf2gd and wmf2fig work on the examples in the source tarball. I don't see any dependencies on libiconv2 or libintl2, in either Gerrit's binary package or the one I built. The other dependencies are OK. cygwmf-0-2-7.dll cygwmflite-0-2-7.dll cygX11-6.dllxorg-x11-bin-dlls cygexpat-0.dll expat cygfreetype-6.dll libfreetype26 cygz.dllzlib cygjpeg-62.dll libjpeg62 cygpng12.dlllibpng12
RE: [ITP] libwmf-0.2.8.3-1
I want to contribute/maintain libwmf, the library for reading vector images Windøws Metafile Format (WMF). I'd like to see this. I have been using the command line utils from libwmf for a while.
RE: [ITP] ImageMagick
From: Harold L Hunt II [mailto:[EMAIL PROTECTED] Sent: Wednesday, 3 December 2003 7:28 PM I would like to contribute and maintain ImageMagick: Question for other maintainers: ImageMagick defaults to building as a static library... I have not yet tried to build it as a shared library; does anyone have an instant educated guess as to whether or not it will be a good idea to pursue a shared library? It would save me a lot of wasted effort if someone told me right now that ImageMagick won't work as a shared lib on Cygwin because foo isn't a shared library or that ImageMagick is known to use undefined symbols at link time. Thanks. I have built ImageMagick-5.5.3 as a shared library. It worked for me some time in July 2003. I indended to contribute the package myself, but (insert usual excuses). I am travelling on business, but I have one of my old build script with me. See below. ImageMagick-5.5.3-1.patch Description: ImageMagick-5.5.3-1.patch ImageMagick-5.5.3-1.sh Description: ImageMagick-5.5.3-1.sh
RE: [ITP] ImageMagick
From: Harold L Hunt II [mailto:[EMAIL PROTECTED] Sent: Thursday, 4 December 2003 5:26 AM To: cygapps Subject: Re: [ITP] ImageMagick David, Billinghurst, David (CALCRTS) wrote: I have built ImageMagick-5.5.3 as a shared library. It worked for me some time in July 2003. I indended to contribute the package myself, but (insert usual excuses). I am travelling on business, but I have one of my old build script with me. See below. Thanks. Can you justify the following flags you passed: --disable-largefile --without-frozenpaths \ --with-magick-plus-plus --without-perl -without-wmf --without-perl is required because the PerlMagick build fails. --without-wmf is detected automatically. I have a local copy of libwmf and didn't want to use it --with-magick-plus-plus is detected automatically. This was around the gcc-2 / gcc-3 transition when the C++ was changing --without-frozenpaths is a mystery to me. I don't know what it does. I think it stops hard-coded paths Additionally, configure.ac looks for convert: Don't recall this happening
RE: new package proposal: CLISP
From: Sam Steingold [mailto:[EMAIL PROTECTED] Sent: Thursday, 18 September 2003 7:26 AM To: Billinghurst, David (CALCRTS) Subject: Re: new package proposal: CLISP maybe you could be interested in maintaining cygwin packages of both CLISP and Maxima? it appears that you are the natural candidate! Sam, You may be right. Pressure of real work has stopped me from putting my hand up, and fatally delayed plans to contribute some other packages, but I would like to see a maxima package for cygwin. I can't do anything for a week or two, but I will consider you offer.
RE: new package proposal: CLISP
From: Sam Steingold Sent: Saturday, 6 September 2003 6:58 AM To: [EMAIL PROTECTED] Subject: new package proposal: CLISP I created a new package: CLISP (http://clisp.cons.org) I would like to see this included. I use clisp compiled maxima under cygwin. BTW: Does it pass it's regression tests? I built clisp-2.31 with cygwin-1.5.3 last night, and had a testsuite failure.
RE: new package proposal: CLISP
From: Sam Steingold Sent: Saturday, 6 September 2003 6:58 AM To: [EMAIL PROTECTED] Subject: new package proposal: CLISP I created a new package: CLISP (http://clisp.cons.org) ftp://ftp2.cons.org/pub/lisp/clisp/binaries/latest/cygwin/clisp-2.31-1.tar.bz2 ftp://ftp2.cons.org/pub/lisp/clisp/binaries/latest/cygwin/clisp-2.31-1-src.tar.bz2 ftp://ftp2.cons.org/pub/lisp/clisp/binaries/latest/cygwin/setup.hint I have installed this (by untarring the tarball in /) and tested it by building maxima-5.9.0. maxima passes its testsuite.
