It's about time that I replied... I've been swamped with more responsibilities
at work and haven't been able to maintain my packages. They are all out of
date. One collection (c-client and uw-imap*) has a security issue that would
be resolved by upgrading the package to the current released v
I had built xerces-c 2.3.0-1 on my system with a cygwin dll and environment
that I had built from recent CVS sources and therefore cygxerces-c23.dll was
looking for some imports (specifically _fopen64) from cygwin1.dll that
aren't in a released version. I re-built on another machine that has a
"fr
Removing them is fine with me :)
thanks!
-Abe
- Original Message -
> PS- Shall I remove package files for version 2.1.0-1?
There has been a new release of xerces-c (2.3.0). Here is part of the
release announcement:
The Xerces-C team is pleased to announce that Xerces-C 2.3.0 is now
available. The primary features of this release are:
- pluggable memory management: Allows an application to have Xerces
request memor
> 1. Is it necessary to put 'gcc' in the 'requires' directive for
> xerces-c-devel ? I've scanned the current setup.ini file and all
> -devel packages I've looked at do not include 'gcc'.
I guess if nobody else is requiring gcc, it isn't necessary.
> 2. Does xerces-c-doc require xerces-c-devel ?
There has been a new release of the official xerces-c 2.2.0. More info at
http://xml.apache.org/
>From the announcement to [EMAIL PROTECTED]:
Highlights of this version:
- C++ Namespace Support
- Schema 1.0 Errata Implementation
- Experimental Implementation of XML 1.1
- More DOM L3 Core Sup
I want to check the list to see if there are active
maintainers of any of these packages before I decide to start work on any of
them.
Net-snmp and UW-imapd aren't currently in our
distribution, but I've seen some discussions of these two packages in the
list. Is anyone actively working o
I installed this and it looks fine to me. Didn't know how best to test it,
but I remembered in the openssl build instructions for VC++ that you can use
nasm to build some of the routines to make openssl faster. I followed these
openssl instructions to use this nasm and everything built ok.
-Abe
I've discovered that in some cases I'm not getting the response that I
expect from the HTTP request that setup.exe issues. I believe my particular
case is probably a misconfiguration of the Apache server that hosts my
website, but in any case I think it might make the setup.exe user experience
a l
Christopher,
Is this something that I did? Just want to make sure everything is ok in
future releases :)
Is the problem that the setup.hint has "desc:", when it should have been
"sdesc:"?
thanks!
-Abe
- Original Message -
> I've fixed this problem but please make a note of this and ma
Thanks for reviewing Gareth. I've updated the script to do a "make
distclean" before creating the src tar just in case there might be some .o
or other build-time generated files laying around.
Updated tar.bz2 file (for src only) is in same location if it needs to be
looked at:
http://abackus.imag
1) changed dll naming (cygxerces-c21.dll) and packaging based on the
suggestions and guidance of Charles Wilson
2) patched stricmp/strnicmp bug found by Gareth Pearce
Apache bug #14612 GCCDefs clashes with cygwin's string.h for stricmp and
strnicmp
(http://nagoya.apache.org/bugzilla/show_bug.cg
1) fixed issue where the cygxerces-c2_1_0.dll wasn't being included (my tar
include file didn't get updated).
2) added patch from Gareth for nasty bug in DOMDocumentTypeImpl.cpp
3) changed back from -2 to -1 in version, following conventions at
http://www.cygwin.com/setup.html
source:
http://aback
Sorry about that guys... I don't like making excuses, so I'll just blame it
on the hallucinogenic drugs :) I'll have a -1 version back there soon and
I'll remove the -2 version. It'll contain the fix for the problem with the
wrong dll (my tar.incl file still had the libxerces instead of cygxerce
I added a patch to follow some recommendations from
Gerrit.
1) have the library name be "cygxerces-c2_1_0.dll"
rather than "libxerces-c2_1_0.dll" (following conventions used by other
libraries in cygwin).
2) the symlinks created in the build structure
during "make" more accurately repres
Sorry for the excessive mailing related to this, it's my first shot at
getting a cygwin package...
Anyway, I didn't like the process that xdrive provided for third party
retrieval of files and yahoo briefcase wouldn't let me share files either.
I put all the files on a single server for consiste
Same links apply for the packages themselves, the source package is on a
different site due to space limitations on all the other places that I know
of...
https://plus.xdrive.com/s/804283208Fy53FcN9QeLkMTBhBPt&partner=xdrv
click on the "Download" button, then double check the download filename...
http://www.mycgiserver.com/~abackus/xerces-c-2.1.0-1.tar.bz2
http://www.mycgiserver.com/~abackus/xerces-c-devel-2.1.0-1.tar.bz2
I also have a source tar.bz2, but it is just over
the 5M limit on any of the public web servers that I have access to :) If
anyone knows where I can drop it, let
I'm interested in becoming a package maintainer for the xerces-c and
xerces-c-devel (http://xml.apache.org/xerces-c/index.html) packages. Below
are the proposed setup.hint files for these packages. I'll have the tar
files ready for uploading by the end of this week.
thank you!
-Abe
xerces-c se
19 matches
Mail list logo
