You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@santuario.apache.org by Scott Cantor <ca...@osu.edu> on 2010/10/26 04:03:02 UTC
C++ release candidate posted
I've uploaded a release candidate for C++ 1.6.0 to the non-mirrored
distribution point:
http://santuario.apache.org/dist/c-library/
CHANGELOG is here:
http://svn.apache.org/viewvc/santuario/trunk/c/CHANGELOG.txt?view=markup
All but one filed bug is resolved. NSS is supported by the build now, but I
will do no testing of the code itself.
It also builds with Xalan-C for XPath support if the Xalan trunk is used,
but that project appears to be dead for all intents and purposes, so I only
do
--without-xalan builds for my purposes.
I would welcome testing, otherwise I'll probably move for a vote to release
within a couple of weeks.
-- Scott
RE: C++ release candidate posted
Posted by "Mazumdar, Subrata (Subrata)" <ma...@avaya.com>.
Link below did not work but the revised link Scott mentioned worked.
--
Subrata
-----Original Message-----
From: Colm O hEigeartaigh [mailto:coheigea@apache.org]
Sent: Tuesday, October 26, 2010 12:04 PM
To: dev@santuario.apache.org
Subject: Re: C++ release candidate posted
Try the following URL instead:
http://svn.apache.org/viewvc/santuario/trunk/c
Colm.
On Tue, Oct 26, 2010 at 4:55 PM, Mazumdar, Subrata (Subrata)
<ma...@avaya.com> wrote:
> SVN download (as described in
> http://santuario.apache.org/c/installation.html) is not working.
>
> I invoked :
> svn co https://svn.apache.org/repos/asf/xml/security/trunk/c
> and getting following error message: svn: URL ... does not exists.
> I also tried the instruction on Java page. It also does not work.
> --
> Subrata
>
> -----Original Message-----
> From: Scott Cantor [mailto:cantor.2@osu.edu]
> Sent: Tuesday, October 26, 2010 11:01 AM
> To: dev@santuario.apache.org
> Subject: RE: C++ release candidate posted
>
>> I would prefer to chop the prefix too.
>
> You can pull svn now and re-test (just run autoreconf -if to generate
> the
> scripts).
>
> I can post a new RC a bit later.
>
> -- Scott
>
>
>
>
Re: C++ release candidate posted
Posted by Colm O hEigeartaigh <co...@apache.org>.
Try the following URL instead:
http://svn.apache.org/viewvc/santuario/trunk/c
Colm.
On Tue, Oct 26, 2010 at 4:55 PM, Mazumdar, Subrata (Subrata)
<ma...@avaya.com> wrote:
> SVN download (as described in
> http://santuario.apache.org/c/installation.html) is not working.
>
> I invoked :
> svn co https://svn.apache.org/repos/asf/xml/security/trunk/c
> and getting following error message: svn: URL ... does not exists.
> I also tried the instruction on Java page. It also does not work.
> --
> Subrata
>
> -----Original Message-----
> From: Scott Cantor [mailto:cantor.2@osu.edu]
> Sent: Tuesday, October 26, 2010 11:01 AM
> To: dev@santuario.apache.org
> Subject: RE: C++ release candidate posted
>
>> I would prefer to chop the prefix too.
>
> You can pull svn now and re-test (just run autoreconf -if to generate
> the
> scripts).
>
> I can post a new RC a bit later.
>
> -- Scott
>
>
>
>
RE: C++ release candidate posted
Posted by Scott Cantor <ca...@osu.edu>.
> SVN download (as described in
> http://santuario.apache.org/c/installation.html) is not working.
> I invoked :
> svn co https://svn.apache.org/repos/asf/xml/security/trunk/c
> and getting following error message: svn: URL ... does not exists.
The code was moved to the santuario tree.
https://svn.apache.org/repos/asf/santuario/trunk/c
-- Scott
RE: C++ release candidate posted
Posted by "Mazumdar, Subrata (Subrata)" <ma...@avaya.com>.
SVN download (as described in
http://santuario.apache.org/c/installation.html) is not working.
I invoked :
svn co https://svn.apache.org/repos/asf/xml/security/trunk/c
and getting following error message: svn: URL ... does not exists.
I also tried the instruction on Java page. It also does not work.
--
Subrata
-----Original Message-----
From: Scott Cantor [mailto:cantor.2@osu.edu]
Sent: Tuesday, October 26, 2010 11:01 AM
To: dev@santuario.apache.org
Subject: RE: C++ release candidate posted
> I would prefer to chop the prefix too.
You can pull svn now and re-test (just run autoreconf -if to generate
the
scripts).
I can post a new RC a bit later.
-- Scott
RE: C++ release candidate posted
Posted by Scott Cantor <ca...@osu.edu>.
> I would prefer to chop the prefix too.
You can pull svn now and re-test (just run autoreconf -if to generate the
scripts).
I can post a new RC a bit later.
-- Scott
RE: C++ release candidate posted
Posted by "Mazumdar, Subrata (Subrata)" <ma...@avaya.com>.
I would prefer to chop the prefix too.
Thanks.
--
Subrata
-----Original Message-----
From: Scott Cantor [mailto:cantor.2@osu.edu]
Sent: Tuesday, October 26, 2010 10:49 AM
To: dev@santuario.apache.org
Subject: RE: C++ release candidate posted
> My preference would be to chop the prefix off the headers if NSS can't
> decide what its prefix is, but that won't work if I leave the
configuration
> to nss-config, so I'll have to ifdef it.
Actually, I'm wrong, it looks like nss-config is returning the
unprefixed
path directly, so the right thing is to chop the prefix.
I can try and add a couple of checks for where the includes are for
non-packaged versions.
-- Scott
RE: C++ release candidate posted
Posted by Scott Cantor <ca...@osu.edu>.
> My preference would be to chop the prefix off the headers if NSS can't
> decide what its prefix is, but that won't work if I leave the
configuration
> to nss-config, so I'll have to ifdef it.
Actually, I'm wrong, it looks like nss-config is returning the unprefixed
path directly, so the right thing is to chop the prefix.
I can try and add a couple of checks for where the includes are for
non-packaged versions.
-- Scott
RE: C++ release candidate posted
Posted by Scott Cantor <ca...@osu.edu>.
> In XSEC-C++ 1.6.0, include declarations for NSS files are changed from
> "nss/xxxx.h" to "nss3/xxxx.h". Since the NSS distribution (I am using NS
> 3.12.6) creates 'nss' directory for include files the configure phase
> fails for NSS validation.
> Would it be possible to go back to nss/xxxx.h declaration?
I used the convention that I found on packaged versions of NSS on Linux
(specifically SUSE and Red Hat). I can't just use nss, that wouldn't work.
If there's a different convention on different systems, we'll have to have a
check for it.
My preference would be to chop the prefix off the headers if NSS can't
decide what its prefix is, but that won't work if I leave the configuration
to nss-config, so I'll have to ifdef it.
-- Scott
RE: C++ release candidate posted
Posted by "Mazumdar, Subrata (Subrata)" <ma...@avaya.com>.
Hi,
In XSEC-C++ 1.6.0, include declarations for NSS files are changed from
"nss/xxxx.h" to "nss3/xxxx.h". Since the NSS distribution (I am using NS
3.12.6) creates 'nss' directory for include files the configure phase
fails for NSS validation.
Would it be possible to go back to nss/xxxx.h declaration?
Thanks.
--
Subrata
-----Original Message-----
From: Scott Cantor [mailto:cantor.2@osu.edu]
Sent: Monday, October 25, 2010 10:03 PM
To: santuario-dev@apache.org
Subject: C++ release candidate posted
I've uploaded a release candidate for C++ 1.6.0 to the non-mirrored
distribution point:
http://santuario.apache.org/dist/c-library/
CHANGELOG is here:
http://svn.apache.org/viewvc/santuario/trunk/c/CHANGELOG.txt?view=markup
All but one filed bug is resolved. NSS is supported by the build now,
but I
will do no testing of the code itself.
It also builds with Xalan-C for XPath support if the Xalan trunk is
used,
but that project appears to be dead for all intents and purposes, so I
only
do
--without-xalan builds for my purposes.
I would welcome testing, otherwise I'll probably move for a vote to
release
within a couple of weeks.
-- Scott