From meorero at gmail.com Sun Mar 1 00:26:41 2009 From: meorero at gmail.com (Oren Maurer) Date: Sun Mar 1 00:26:48 2009 Subject: How / where to get a Perl that has threads? Message-ID: Hello all. As I'm new to this list - please forgive me for a newbie questions (but I promise to at least try to first Google and search this list archives). In short: I have FreeBSD 7.1. It seems to have Perl without threads . And I do need threads. How can I get it? Details: I want to try install Padre (Perl IDE, see: http://padre.perlide.org/) - which requires a perl that has threads. I have run the command: perl -V |grep threads I get this: meorero_bsd03# perl -V |grep threads config_args='-sde -Dprefix=/usr/local -Darchlib=/usr/local/lib/perl5/5.8.8/mach -Dprivlib=/usr/local/lib/perl5/5.8.8 -Dman3dir=/usr/local/lib/perl5/5.8.8/perl/man/man3 -Dman1dir=/usr/local/man/man1 -Dsitearch=/usr/local/lib/perl5/site_perl/5.8.8/mach -Dsitelib=/usr/local/lib/perl5/site_perl/5.8.8 -Dscriptdir=/usr/local/bin -Dsiteman3dir=/usr/local/lib/perl5/5.8.8/man/man3 -Dsiteman1dir=/usr/local/man/man1 -Ui_malloc -Ui_iconv -Uinstallusrbinperl -Dcc=cc -Duseshrplib -Dccflags=-DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.8/BSDPAN" -Doptimize=-O2 -fno-strict-aliasing -pipe -Ud_dosuid -Ui_gdbm -Dusethreads=n -Dusemymalloc=y -Duse64bitint' usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef meorero_bsd03# As you can see - I have: usethreads=undef use5005threads=undef useithreads=undef I understand that I need one (and only one) of these: usethreads , use5005threads or useithread - Not to be undef. I installed p5-threads http://www.freshports.org/devel/p5-threads/ and p5-threads-shared http://www.freshports.org/devel/p5-threads-shared/ Still I get the same. Note: This is a question after discussing in the same in the [Padre-dev] mailing list: http://mail.perlide.org/pipermail/padre-dev/2009-February/000710.html Regards Oren Maurer -- ________________________________ Oren Maurer http://meorero.wordpress.com http://www.meorero.org.il _______________________________ # =======================| # Please avoid sending me Word | # or PowerPoint attachments | # =======================| # See: http://www.gnu.org/philosophy/no-word-attachments.html From m.seaman at infracaninophile.co.uk Sun Mar 1 02:34:05 2009 From: m.seaman at infracaninophile.co.uk (Matthew Seaman) Date: Sun Mar 1 02:34:12 2009 Subject: How / where to get a Perl that has threads? In-Reply-To: References: Message-ID: <49AA6490.7080305@infracaninophile.co.uk> Oren Maurer wrote: > Hello all. > > As I'm new to this list - please forgive me for a newbie questions > (but I promise to at least try to first Google and search this list > archives). > > In short: > I have FreeBSD 7.1. > > It seems to have Perl without threads . And I do need threads. > How can I get it? You have to re-install perl from ports and you have to select the config option that says 'build a perl with threads'. Note that if you're using other applications that embed a perl interpreter (mod_perl, snmpd) they may not work correctly with a threaded perl. At minimum you'll have to recompile them. Similarly perl modules that use .xs to generate compiled loadable objects may also need recompilation or may not work at all. Best to test this out thoroughly on a spare machine before you put it on anything production. # cd /usr/ports/lang/perl5.8 # make config Ensure the THREADS option is checked in the dialogue: [X] THREADS Build threaded perl # portupgrade -f lang/perl5.8 To ensure *everything* is recompiled against the new threaded perl, you can do: # portupgrade -fr lang/perl5.8 but be warned: that is basically going to recompile virtually every port you've got installed which will take approximately forever and is really overkill. There's no reason to recompile ports whose only dependency on perl is because they use automake at compile time. Nor is there any reason to reinstall pure-perl modules. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090301/25118ebe/signature.pgp From esbjerg at xbsd.net Sun Mar 1 02:37:15 2009 From: esbjerg at xbsd.net (Sven Esbjerg) Date: Sun Mar 1 02:37:21 2009 Subject: How / where to get a Perl that has threads? In-Reply-To: References: Message-ID: <20090301101205.GB539@esbjerg.name> On Sun, Mar 01, 2009 at 10:05:19AM +0200, Oren Maurer wrote: > In short: > I have FreeBSD 7.1. > > It seems to have Perl without threads . And I do need threads. > How can I get it? Run make config and enable threads. Then rebuild perl :) -Sven From meorero at gmail.com Sun Mar 1 04:02:45 2009 From: meorero at gmail.com (Oren Maurer) Date: Sun Mar 1 04:02:52 2009 Subject: How / where to get a Perl that has threads? In-Reply-To: <49AA6490.7080305@infracaninophile.co.uk> References: <49AA6490.7080305@infracaninophile.co.uk> Message-ID: Is there a reason for not having threaded Perl as the default? Is it matter of History (compatibility with past code)? Or internal FreeBSD reason (memory)? I have seen other OS's - that do use threaded Perl as default (Linux, MSWin32). But in all of those OS's I have Perl 5.10. (hint .... hint....) I hope that when Perl 5.10 port will be available for FreeBSD - It will be threaded. Oren. On Sun, Mar 1, 2009 at 12:33 PM, Matthew Seaman wrote: > Oren Maurer wrote: >> >> Hello all. >> >> As I'm new to this list - please forgive me for a newbie questions >> (but I promise to at least try to first Google and search this list >> archives). >> >> In short: >> I have FreeBSD 7.1. >> >> It seems to have Perl without threads . And I do need threads. >> How can I get it? > > You have to re-install perl from ports and you have to select the config > option that says 'build a perl with threads'. ?Note that if you're using > other applications that embed a perl interpreter (mod_perl, snmpd) they > may not work correctly with a threaded perl. ?At minimum you'll have to > recompile them. ?Similarly perl modules that use .xs to generate compiled > loadable objects may also need recompilation or may not work at all. Best to > test this out thoroughly on a spare machine before you put it on > anything production. > > ? # cd /usr/ports/lang/perl5.8 > ? # make config > ? ? ? ? ?Ensure the THREADS option is checked in the dialogue: > ? ? ? ? [X] THREADS ? ? ? ?Build threaded perl > ? # portupgrade -f lang/perl5.8 > > To ensure *everything* is recompiled against the new threaded perl, you > can do: > > ? # portupgrade -fr lang/perl5.8 > > but be warned: that is basically going to recompile virtually every port > you've got installed which will take approximately forever and is really > overkill. ?There's no reason to recompile ports whose only dependency on > perl is because they use automake at compile time. ?Nor is there any reason > to reinstall pure-perl modules. > > ? ? ? ?Cheers, > > ? ? ? ?Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. ? ? ? ? ? ? ? ? ? 7 Priory Courtyard > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey ? ? Ramsgate > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Kent, CT11 9PW > > -- ________________________________ Oren Maurer http://meorero.wordpress.com http://www.meorero.org.il _______________________________ # =======================| # Please avoid sending me Word | # or PowerPoint attachments | # =======================| # See: http://www.gnu.org/philosophy/no-word-attachments.html From tobez at tobez.org Sun Mar 1 07:34:50 2009 From: tobez at tobez.org (Anton Berezin) Date: Sun Mar 1 07:35:04 2009 Subject: How / where to get a Perl that has threads? In-Reply-To: <49AA6490.7080305@infracaninophile.co.uk> References: <49AA6490.7080305@infracaninophile.co.uk> Message-ID: <20090301153448.GA94320@heechee.tobez.org> On Sun, Mar 01, 2009 at 10:33:52AM +0000, Matthew Seaman wrote: > Oren Maurer wrote: > > Hello all. > > > > As I'm new to this list - please forgive me for a newbie questions > > (but I promise to at least try to first Google and search this list > > archives). > > > > In short: > > I have FreeBSD 7.1. > > > > It seems to have Perl without threads . And I do need threads. > > How can I get it? > > You have to re-install perl from ports and you have to select the config > option that says 'build a perl with threads'. Or just make Padre work with devel/p5-forks instead, which is faster, uses an interface compatible with "use threads", and does not require threaded Perl. Cheers, \Anton. -- There is no beauty in entropy. -- Eliezer Yudkowsky From tobez at tobez.org Sun Mar 1 07:39:02 2009 From: tobez at tobez.org (Anton Berezin) Date: Sun Mar 1 07:39:08 2009 Subject: How / where to get a Perl that has threads? In-Reply-To: References: <49AA6490.7080305@infracaninophile.co.uk> Message-ID: <20090301153900.GB94320@heechee.tobez.org> On Sun, Mar 01, 2009 at 02:02:27PM +0200, Oren Maurer wrote: > Is there a reason for not having threaded Perl as the default? > Is it matter of History (compatibility with past code)? > Or internal FreeBSD reason (memory)? > I have seen other OS's - that do use threaded Perl as default (Linux, > MSWin32). The biggest reason is that FreeBSD has a rather small main thread stack size (2 MB for 32-bit architectures and 4 MB for 64-bit architectures), and this parameter cannot be changed without recompiling the system threads library. Or at least that used to be the case last time I checked, about a year ago. So a given Perl program that does NOT use threads will have much smaller stack when executed in a perl compiled with threads support. Some large applications (amavisd-new, IIRC) had problems with that. Cheers, \Anton. -- There is no beauty in entropy. -- Eliezer Yudkowsky From meorero at gmail.com Sun Mar 1 07:53:49 2009 From: meorero at gmail.com (Oren Maurer) Date: Sun Mar 1 07:53:55 2009 Subject: How / where to get a Perl that has threads? In-Reply-To: <20090301153448.GA94320@heechee.tobez.org> References: <49AA6490.7080305@infracaninophile.co.uk> <20090301153448.GA94320@heechee.tobez.org> Message-ID: Thanks for the reply, Anton. I'm cross-posting your 2 answers also to the Padre development discussion list. So... - Here is a question is to padre developers: FreeBSD had a package named "p5-fork". Could Padre use this on FreeBSD? (or even on other OS's ?) If yes - How?? The "p5-fork" is actually: http://search.cpan.org/dist/forks/ See here: http://portsmon.freebsd.org/portoverview.py?category=devel&portname=p5-forks and here: http://www.freshports.org/devel/p5-forks/ See also my question on the FreeBSD-Perl list: http://lists.freebsd.org/pipermail/freebsd-perl/2009-March/002097.html Thanks Oren On Sun, Mar 1, 2009 at 5:34 PM, Anton Berezin wrote: > On Sun, Mar 01, 2009 at 10:33:52AM +0000, Matthew Seaman wrote: >> Oren Maurer wrote: >> > Hello all. >> > >> > As I'm new to this list - please forgive me for a newbie questions >> > (but I promise to at least try to first Google and search this list >> > archives). >> > >> > In short: >> > I have FreeBSD 7.1. >> > >> > It seems to have Perl without threads . And I do need threads. >> > How can I get it? >> >> You have to re-install perl from ports and you have to select the config >> option that says 'build a perl with threads'. > > Or just make Padre work with devel/p5-forks instead, which is faster, uses > an interface compatible with "use threads", and does not require threaded > Perl. > > Cheers, > \Anton. > -- > There is no beauty in entropy. -- Eliezer Yudkowsky > -- ________________________________ Oren Maurer http://meorero.wordpress.com http://www.meorero.org.il _______________________________ # =======================| # Please avoid sending me Word | # or PowerPoint attachments | # =======================| # See: http://www.gnu.org/philosophy/no-word-attachments.html From szabgab at gmail.com Sun Mar 1 08:35:08 2009 From: szabgab at gmail.com (Gabor Szabo) Date: Sun Mar 1 08:35:14 2009 Subject: [Padre-dev] How / where to get a Perl that has threads? In-Reply-To: References: <49AA6490.7080305@infracaninophile.co.uk> <20090301153448.GA94320@heechee.tobez.org> Message-ID: On Sun, Mar 1, 2009 at 5:53 PM, Oren Maurer wrote: > Thanks for the reply, Anton. > I'm cross-posting your 2 answers ?also to the Padre development discussion list. > > So... - Here is a question is to padre developers: > > FreeBSD had a package named "p5-fork". > > Could Padre use this on FreeBSD? > (or even on other OS's ?) > > If yes - How?? I don't know. Try it :-) Have you managed to compile wxWidgets already ? Gabor From valerio.daelli at gmail.com Mon Mar 2 01:03:48 2009 From: valerio.daelli at gmail.com (Valerio Daelli) Date: Mon Mar 2 01:03:54 2009 Subject: Upgrade to perl 5.10 Message-ID: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> Hi is there any plan in upgrading perl from 5.8 o 5.10? I tried compiling from sources and everything went fine. I can test the perl ports in archivers/ to check everything works with this new version. Thanks Valerio From bugmaster at FreeBSD.org Mon Mar 2 03:09:18 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Mar 2 03:13:31 2009 Subject: Current problem reports assigned to perl@FreeBSD.org Message-ID: <200903021108.n22B80Po058596@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/131225 perl math/PDL: PDL-2.4.3_5: Unable to find PDL/pdldoc.db o ports/130175 perl Update math/PDL to version 2.4.4 o ports/129626 perl lang/p5-Tcl segfaults on i386 and amd64 on FreeBSD 7 o ports/121472 perl Loading perl scripts causes irc/xchat segmentation fau 4 problems total. From meorero at gmail.com Mon Mar 2 06:16:08 2009 From: meorero at gmail.com (Oren Maurer) Date: Mon Mar 2 06:16:16 2009 Subject: Upgrade to perl 5.10 In-Reply-To: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> Message-ID: Joining the question of Valerio. Perl 5.10.0 was released more than a year ago (in December 2007 - according to Wikipedia). Furthermore - I think it should become compiled with threads as default - just like in other OS'es. See discussion here: [Padre-dev] "cpan> install Padre'" on FreeBSD 7.1: Padre requires a perl built using threads http://mail.perlide.org/pipermail/padre-dev/2009-March/000719.html Oren On Mon, Mar 2, 2009 at 10:33 AM, Valerio Daelli wrote: > Hi > > is there any plan in upgrading perl from 5.8 o 5.10? > I tried compiling from sources and everything went fine. > I can test the perl ports in archivers/ to check everything works with this > new version. > Thanks > > Valerio > _______________________________________________ > freebsd-perl@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-perl > To unsubscribe, send any mail to "freebsd-perl-unsubscribe@freebsd.org" > -- ________________________________ Oren Maurer http://meorero.wordpress.com http://www.meorero.org.il _______________________________ # =======================| # Please avoid sending me Word | # or PowerPoint attachments | # =======================| # See: http://www.gnu.org/philosophy/no-word-attachments.html From valerio.daelli at gmail.com Mon Mar 2 09:07:19 2009 From: valerio.daelli at gmail.com (Valerio Daelli) Date: Mon Mar 2 09:07:26 2009 Subject: Upgrade to perl 5.10 In-Reply-To: References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> Message-ID: <27dbfc8c0903020907w6cee397fkd7fc577d2d9bb891@mail.gmail.com> I am quite interested in getting perl 5.10 working with the FreeBSD perl ports. I can provide help in testing and debugging code. I think I'll ask the perl mantainer if he's working on something: if he has some patch for the port I'll start working with his code. Bye Valerio Daelli On Mon, Mar 2, 2009 at 3:16 PM, Oren Maurer wrote: > Joining the question of Valerio. > > Perl 5.10.0 was released more than a year ago (in December 2007 - > according to Wikipedia). > > Furthermore - I think it should become compiled with threads ?as > default - ?just like in other OS'es. > > See discussion here: > [Padre-dev] "cpan> install Padre'" on FreeBSD 7.1: Padre requires a > perl built using threads > http://mail.perlide.org/pipermail/padre-dev/2009-March/000719.html > > > Oren > > > On Mon, Mar 2, 2009 at 10:33 AM, Valerio Daelli > wrote: >> Hi >> >> is there any plan in upgrading perl from 5.8 o 5.10? >> I tried compiling from sources and everything went fine. >> I can test the perl ports in archivers/ to check everything works with this >> new version. >> Thanks >> >> Valerio >> _______________________________________________ >> freebsd-perl@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-perl >> To unsubscribe, send any mail to "freebsd-perl-unsubscribe@freebsd.org" >> > > > > -- > ________________________________ > Oren ?Maurer > http://meorero.wordpress.com > http://www.meorero.org.il > ?_______________________________ > ?# ?=======================| > ?# ?Please avoid sending me Word | > ?# ? or PowerPoint attachments ? ? ?| > ?# ?=======================| > ?# See: http://www.gnu.org/philosophy/no-word-attachments.html > _______________________________________________ > freebsd-perl@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-perl > To unsubscribe, send any mail to "freebsd-perl-unsubscribe@freebsd.org" > From skv at protey.ru Fri Mar 6 05:29:33 2009 From: skv at protey.ru (Sergey Skvortsov) Date: Fri Mar 6 05:29:40 2009 Subject: Upgrade to perl 5.10 In-Reply-To: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> Message-ID: <49B11D73.90409@protey.ru> On 02.03.2009 11:33, Valerio Daelli wrote: > Hi > > is there any plan in upgrading perl from 5.8 o 5.10? > I tried compiling from sources and everything went fine. > I can test the perl ports in archivers/ to check everything works with this > new version. > Thanks Port lang/perl5.10 will be committed in March 2009. Right now I run some regression tests in tinderbox. If you want to be an "early adopter" feel free test it in your environment - patch & shar can be obtained here: http://people.freebsd.org/~skv/20090306/ -- Sergey Skvortsov mailto: skv@protey.ru From meorero at gmail.com Fri Mar 6 06:19:32 2009 From: meorero at gmail.com (Oren Maurer) Date: Fri Mar 6 06:19:39 2009 Subject: Upgrade to perl 5.10 In-Reply-To: <49B11D73.90409@protey.ru> References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> <49B11D73.90409@protey.ru> Message-ID: Hi Sergey. Good news. I have installed other system on the partition where I had my FreeBSD (other BSD, and no - I'll not mentioned what other BSD ... ) -- but I'll e glad to re-install everything and test it! And I'll be glad to see it released (We are on March 2009 already... ). As I wrote - I want to try to install Padre on it. in "Padre" - I mean the Perl IDE. See http://padre.perlide.org/wiki On Fri, Mar 6, 2009 at 2:56 PM, Sergey Skvortsov wrote: > On 02.03.2009 11:33, Valerio Daelli wrote: > > Hi > > > > is there any plan in upgrading perl from 5.8 o 5.10? > > I tried compiling from sources and everything went fine. > > I can test the perl ports in archivers/ to check everything works with > this > > new version. > > Thanks > > Port lang/perl5.10 will be committed in March 2009. > > Right now I run some regression tests in tinderbox. > > If you want to be an "early adopter" feel free test it in your > environment - patch & shar can be obtained here: > > http://people.freebsd.org/~skv/20090306/ > > -- > Sergey Skvortsov > mailto: skv@protey.ru > _______________________________________________ > freebsd-perl@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-perl > To unsubscribe, send any mail to "freebsd-perl-unsubscribe@freebsd.org" > -- ________________________________ Oren Maurer http://meorero.wordpress.com http://www.meorero.org.il _______________________________ # =======================| # Please avoid sending me Word | # or PowerPoint attachments | # =======================| # See: http://www.gnu.org/philosophy/no-word-attachments.html From cm at therek.net Fri Mar 6 07:15:57 2009 From: cm at therek.net (Cezary Morga) Date: Fri Mar 6 07:16:04 2009 Subject: Upgrade to perl 5.10 In-Reply-To: References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> <49B11D73.90409@protey.ru> Message-ID: <200903061604.50931.cm@therek.net> Oren Maurer wrote: > As I wrote - I want to try to install Padre on it. > > in "Padre" - I mean the Perl IDE. Have you tried running it on 5.8.9? I'm working on it and I appears that might be do-able. Right now I'm at going through all the dependencies. -- Cezary Morga "Examinations are formidable even to the best prepared, for the greatest fool may ask more than the wisest man can answer." (Charles Caleb Colton) From meorero at gmail.com Fri Mar 6 09:19:26 2009 From: meorero at gmail.com (Oren Maurer) Date: Fri Mar 6 09:19:33 2009 Subject: Upgrade to perl 5.10 In-Reply-To: <200903061604.50931.cm@therek.net> References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> <49B11D73.90409@protey.ru> <200903061604.50931.cm@therek.net> Message-ID: Yes I tried it - but I had another problem: Padre requires a Perl built using threads! Do you have Perl with threads? How did you made it? I used the Perl that is instaled with FreeBSD 7.1. I hope that the Perl 5.10 port will have threads by default - this is what U see in Perl with other OS'es. On Fri, Mar 6, 2009 at 5:04 PM, Cezary Morga wrote: > Oren Maurer wrote: > > As I wrote - I want to try to install Padre on it. > > > > in "Padre" - I mean the Perl IDE. > > Have you tried running it on 5.8.9? > > I'm working on it and I appears that might be do-able. Right now I'm at > going through all the dependencies. > > -- > Cezary Morga > "Examinations are formidable even to the best prepared, for the greatest > fool may ask more than the wisest man can answer." (Charles Caleb > Colton) > _______________________________________________ > freebsd-perl@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-perl > To unsubscribe, send any mail to "freebsd-perl-unsubscribe@freebsd.org" > -- ________________________________ Oren Maurer http://meorero.wordpress.com http://www.meorero.org.il _______________________________ # =======================| # Please avoid sending me Word | # or PowerPoint attachments | # =======================| # See: http://www.gnu.org/philosophy/no-word-attachments.html From martin at martinkjeldsen.dk Fri Mar 6 09:46:13 2009 From: martin at martinkjeldsen.dk (Martin Kjeldsen) Date: Fri Mar 6 09:46:20 2009 Subject: Upgrade to perl 5.10 In-Reply-To: References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> <49B11D73.90409@protey.ru> <200903061604.50931.cm@therek.net> Message-ID: <20090306172917.GA1604@martinkjeldsen.dk> Oren Maurer (19:19 2009-03-06): > > I hope that the Perl 5.10 port will have threads by default - this is what U > see in Perl with other OS'es. > I've just downloaded the patch and it doesn't seem like threading is on by default, but you can turn in on with make config... -- Martin From lars at balker.dk Fri Mar 6 09:56:36 2009 From: lars at balker.dk (Lars Balker Rasmussen) Date: Fri Mar 6 09:56:42 2009 Subject: Upgrade to perl 5.10 In-Reply-To: References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> <49B11D73.90409@protey.ru> <200903061604.50931.cm@therek.net> Message-ID: <376a98e00903060925r53c5d231gcd479cc35c3202b1@mail.gmail.com> On Fri, Mar 6, 2009 at 6:19 PM, Oren Maurer wrote: > I hope that the Perl 5.10 port will have threads by default - this is what U > see in Perl with other OS'es. I absolutely agree. But stack-space becomes an issue then - how do other OS'es deal with this? Sergey, your thoughts? -- Lars Balker Rasmussen Consult::Perl From cm at therek.net Fri Mar 6 14:27:52 2009 From: cm at therek.net (Cezary Morga) Date: Fri Mar 6 14:27:58 2009 Subject: Padre (Was: Re: Upgrade to perl 5.10) In-Reply-To: References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> <200903061604.50931.cm@therek.net> Message-ID: <200903062327.44745.cm@therek.net> Oren Maurer wrote: > Yes I tried it - but I had another problem: > Padre requires a Perl built using threads! > > Do you have Perl with threads? > How did you made it? Yes. I've compiled it from ports with WITH_THREADS=yes flag (available through port's config as well). If anyone's interested here's my first attempt at creating FreeBSD Ports for Padre, including wxPerl: http://www.therek.net/ports/padre.shar. Total of 21 new ports. An update for devel/p5-Module-Starter (patch here: http://www.freebsd.org/cgi/query-pr.cgi?pr=132364) might also be required. -- Cezary Morga "The power of accurate observation is commonly called cynicism by those who have not got it." (George Bernard Shaw) From meorero at gmail.com Fri Mar 6 14:50:54 2009 From: meorero at gmail.com (Oren Maurer) Date: Fri Mar 6 14:51:02 2009 Subject: Padre (Was: Re: Upgrade to perl 5.10) In-Reply-To: <200903062327.44745.cm@therek.net> References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> <200903061604.50931.cm@therek.net> <200903062327.44745.cm@therek.net> Message-ID: I'm happy to see this - so I cross-post this to the Padre mailing list. (Padre guys - please see thread on http://lists.freebsd.org/pipermail/freebsd-perl/2009-March/thread.html ). I'll try after I'll re-install my FreeBSD. On Sat, Mar 7, 2009 at 12:27 AM, Cezary Morga wrote: > Oren Maurer wrote: > > Yes I tried it - but I had another problem: > > Padre requires a Perl built using threads! > > > > Do you have Perl with threads? > > How did you made it? > > Yes. I've compiled it from ports with WITH_THREADS=yes flag (available > through port's config as well). > > If anyone's interested here's my first attempt at creating FreeBSD Ports > for Padre, including wxPerl: http://www.therek.net/ports/padre.shar. > Total of 21 new ports. An update for devel/p5-Module-Starter (patch > here: http://www.freebsd.org/cgi/query-pr.cgi?pr=132364) might also be > required. > > -- > Cezary Morga > "The power of accurate observation is commonly called cynicism by those > who have not got it." (George Bernard Shaw) > _______________________________________________ > freebsd-perl@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-perl > To unsubscribe, send any mail to "freebsd-perl-unsubscribe@freebsd.org" > -- ________________________________ Oren Maurer http://meorero.wordpress.com http://www.meorero.org.il _______________________________ # =======================| # Please avoid sending me Word | # or PowerPoint attachments | # =======================| # See: http://www.gnu.org/philosophy/no-word-attachments.html From cm at therek.net Sat Mar 7 10:58:34 2009 From: cm at therek.net (Cezary Morga) Date: Sat Mar 7 10:58:41 2009 Subject: Padre (Was: Re: Upgrade to perl 5.10) In-Reply-To: <200903062327.44745.cm@therek.net> References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> <200903062327.44745.cm@therek.net> Message-ID: <200903071958.25381.cm@therek.net> > If anyone's interested here's my first attempt at creating FreeBSD > Ports for Padre, including wxPerl: > http://www.therek.net/ports/padre.shar. Total of 21 new ports. An > update for devel/p5-Module-Starter (patch here: > http://www.freebsd.org/cgi/query-pr.cgi?pr=132364) might also be > required. I've uploaded a bit updated .shar[1] file. It turned out Padre was updated three days ago removing one dependency (Wx::Perl::Dialog is now a part of Padre). Also I've found two more ports that have been added to FreeBSD ports tree a week ago. [1] http://www.therek.net/ports/padre2.shar -- Cezary Morga "Not a shred of evidence exists in favor of the idea that life is serious." (Brendan Gill) From miwi at FreeBSD.org Sun Mar 8 09:19:51 2009 From: miwi at FreeBSD.org (miwi@FreeBSD.org) Date: Sun Mar 8 09:20:23 2009 Subject: FreeBSD ports you maintain which are out of date Message-ID: <20090308160118.73EF523C958A@portscout.org> Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.org/perl@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/p5-Term-CallEditor | 0.11 | 0.13 ------------------------------------------------+-----------------+------------ security/p5-PerlCryptLib | 1.05 | 1.07 ------------------------------------------------+-----------------+------------ sysutils/p5-Fuse | 0.09 | 0.09_3 ------------------------------------------------+-----------------+------------ textproc/p5-Text-Tabs+Wrap | 2006.1117 | 2009.0305 ------------------------------------------------+-----------------+------------ textproc/p5-Text-Trac | 0.14 | 0.15 ------------------------------------------------+-----------------+------------ www/p5-Apache-Clean | 0.05 | 2.00_7 ------------------------------------------------+-----------------+------------ www/p5-WWW-Spinn3r | 2.00200002 | 3.00700001 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://beta.inerd.com/portscout-portconfig.txt If you need help, have any problems, find a bug in this software, or wish to stop (or start!) receiving portscout reminders, feel free to contact me at miwi(at)FreeBSD.org. Thanks. From linimon at FreeBSD.org Mon Mar 9 00:28:22 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon Mar 9 00:28:36 2009 Subject: FreeBSD ports that you maintain which are currently marked broken Message-ID: <20090309072821.17E5A1CD40@mail.droso.net> Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 5.x/6.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: www/p5-HTML-Embperl broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=p5-HTML-Embperl If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. From bugmaster at FreeBSD.org Mon Mar 9 10:16:16 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Mar 9 10:18:32 2009 Subject: Current problem reports assigned to perl@FreeBSD.org Message-ID: <200903091716.n29HGDpn046549@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/131225 perl math/PDL: PDL-2.4.3_5: Unable to find PDL/pdldoc.db o ports/130175 perl Update math/PDL to version 2.4.4 o ports/129626 perl lang/p5-Tcl segfaults on i386 and amd64 on FreeBSD 7 o ports/121472 perl Loading perl scripts causes irc/xchat segmentation fau 4 problems total. From tom at FreeBSD.org Mon Mar 9 11:01:25 2009 From: tom at FreeBSD.org (Tom Hukins) Date: Mon Mar 9 11:01:31 2009 Subject: Upgrade to perl 5.10 In-Reply-To: References: <27dbfc8c0903020033r65388ac8j1190008af28154f6@mail.gmail.com> <49B11D73.90409@protey.ru> <200903061604.50931.cm@therek.net> Message-ID: <20090309173438.GA39921@eborcom.com> On Fri, Mar 06, 2009 at 07:19:24PM +0200, Oren Maurer wrote: > I hope that the Perl 5.10 port will have threads by default I hope it won't. Perl's threads don't work well for many applications. A perl binary built with threading slows down all applications, even those that do not use threads, noticeably. I like that FreeBSD's Perl uses Perl's default settings in most cases, with the port letting users override them if they choose. Perl itself disables threads by default. > this is what U see in Perl with other OS'es. I usually build my own perl binaries on other operating systems, partly because of this. Tom From edwin at FreeBSD.org Mon Mar 9 14:20:14 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Mon Mar 9 14:20:20 2009 Subject: ports/132485: Update: textproc/p5-Text-Trac to 0.15 Message-ID: <200903092120.n29LKDBE061637@freefall.freebsd.org> Synopsis: Update: textproc/p5-Text-Trac to 0.15 Responsible-Changed-From-To: freebsd-ports-bugs->perl Responsible-Changed-By: edwin Responsible-Changed-When: Mon Mar 9 21:20:13 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=132485 From miwi at FreeBSD.org Mon Mar 9 15:13:06 2009 From: miwi at FreeBSD.org (miwi@FreeBSD.org) Date: Mon Mar 9 15:13:11 2009 Subject: ports/132485: Update: textproc/p5-Text-Trac to 0.15 Message-ID: <200903092213.n29MD3HZ037166@freefall.freebsd.org> Synopsis: Update: textproc/p5-Text-Trac to 0.15 Responsible-Changed-From-To: perl->miwi Responsible-Changed-By: miwi Responsible-Changed-When: Mon Mar 9 22:13:03 UTC 2009 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=132485 From awardcenter2009 at gmail.com Tue Mar 10 10:36:59 2009 From: awardcenter2009 at gmail.com (YAHOO AWARD CENTER) Date: Tue Mar 10 10:37:19 2009 Subject: YOU ARE A WINNER OF YAHOO AWARD GRANTS JANUARY 2009 Message-ID: <20090310171011.11326.qmail@be27.masterhost.ru> Awards Centre 124 Stockport Road, Longsight, Manchester M60 2DB - United KingdomTel:+447031925532. This is to inform you that you have won a prize money of Three million,Two Hundred Thousand Great Britain Pounds (GBP 3,200,000.00) for the month of January, 2009 Prize promotion which is organized by YAHOO A WARDS & WINDOWS LIVE. YAHOO collects all the email addresses of the people that are active online, among the millions that subscribed to Yahoo and Hotmail and few from other e-mail providers. Six people are selected monthly to benefit from this promotion and you are one of the Selected Winners which your e-mail address won the Jackpot Prize while other five winners won One Million Great Britain Pounds(GBP 1,000,000.00) each. PAYMENT OF PRIZE / CLAIMS Winners shall be paid in accordance with their Settlement Centers. Yahoo Prize Award must be claimed not later than 10 days from date of Draw Notification. Any prize not claimed within this period will be forfeited and returned to its source as unclaimed. Stated below are your identification numbers: BATCH NUMBER: MFI/06/APA-43658 REFERENCE NUMBER: 2007234522 PIN: 1207 You are requested to contact our Assistant co-ordinator in Manchester and send your winning identification numbers to him: Co-ordinator's Name: Dr. Christopher Adam.E-Mail:award_cent123@yahoo.fr Tel:+447031925532 You are advised to send the following information to our co-ordinator to facilitate the release of of your fund to you. 1. Full name.............................................. 2. Country................................................. 3. Contact Address................................ 4. Telephone Number............................ 5. fax Number.......................................... 5. Marital Status..................................... 6. Occupation.......................................... 7. Sex......................................................... 8. Date of Birth/Age ............................... 9. Identity card(carte identite)............. Congratulations!! once again. Yours in service, Mrs. Mary Anna Jones(Awards coordinator) -------------------------------------------------------------------------------------------------------------------------------------------------WARNING! You must keep strict confidentiality of your Prize Award claims to yourself until your money is successfully handed over to you to avoid disqualification that may arise from double claims. Yahoo Awards Team shall not be held liable for any loss of funds arising from the above mentioned. From edwin at FreeBSD.org Wed Mar 11 09:20:16 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Wed Mar 11 09:20:27 2009 Subject: ports/132549: [Update]devel/p5-Coro:update to 5.13 Message-ID: <200903111620.n2BGKF5K071364@freefall.freebsd.org> Synopsis: [Update]devel/p5-Coro:update to 5.13 Responsible-Changed-From-To: freebsd-ports-bugs->perl Responsible-Changed-By: edwin Responsible-Changed-When: Wed Mar 11 16:20:15 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=132549 From erwin at FreeBSD.org Wed Mar 11 10:29:23 2009 From: erwin at FreeBSD.org (erwin@FreeBSD.org) Date: Wed Mar 11 10:29:32 2009 Subject: ports/132549: [Update]devel/p5-Coro:update to 5.13 Message-ID: <200903111729.n2BHTMMG062326@freefall.freebsd.org> Synopsis: [Update]devel/p5-Coro:update to 5.13 State-Changed-From-To: open->closed State-Changed-By: erwin State-Changed-When: Wed Mar 11 17:29:18 UTC 2009 State-Changed-Why: Committed, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=132549 From dfilter at FreeBSD.ORG Wed Mar 11 10:30:07 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Wed Mar 11 10:30:16 2009 Subject: ports/132549: commit references a PR Message-ID: <200903111730.n2BHU5ix062590@freefall.freebsd.org> The following reply was made to PR ports/132549; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/132549: commit references a PR Date: Wed, 11 Mar 2009 17:29:26 +0000 (UTC) erwin 2009-03-11 17:29:15 UTC FreeBSD ports repository Modified files: devel/p5-Coro Makefile distinfo pkg-plist devel/p5-Coro/files patch-Coro-Makefile.PL patch-Coro-State.xs Log: Update to 5.13 PR: 132549 Submitted by: Wen Heping Revision Changes Path 1.30 +5 -2 ports/devel/p5-Coro/Makefile 1.25 +3 -3 ports/devel/p5-Coro/distinfo 1.6 +28 -14 ports/devel/p5-Coro/files/patch-Coro-Makefile.PL 1.2 +6 -6 ports/devel/p5-Coro/files/patch-Coro-State.xs 1.12 +5 -0 ports/devel/p5-Coro/pkg-plist _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From bugmaster at FreeBSD.org Mon Mar 16 04:08:05 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Mar 16 04:10:08 2009 Subject: Current problem reports assigned to perl@FreeBSD.org Message-ID: <200903161108.n2GB81t4044523@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/131225 perl math/PDL: PDL-2.4.3_5: Unable to find PDL/pdldoc.db o ports/130175 perl Update math/PDL to version 2.4.4 o ports/129626 perl lang/p5-Tcl segfaults on i386 and amd64 on FreeBSD 7 o ports/121472 perl Loading perl scripts causes irc/xchat segmentation fau 4 problems total. From kmenzel at whisolutions.com Tue Mar 17 14:17:03 2009 From: kmenzel at whisolutions.com (Ken Menzel) Date: Tue Mar 17 14:17:16 2009 Subject: [Fwd: p5-XML-Xerces-2.7.0 failed on amd64 6] In-Reply-To: <1232117639.1546.15.camel@pav.hide.vol.cz> References: <1232060149.42745.16.camel@hood.oook.cz> <49709981.2010105@whisolutions.com> <1232117639.1546.15.camel@pav.hide.vol.cz> Message-ID: <49C00B9A.4080804@whisolutions.com> Pav, I don't know if you still care about Xerces, but I found the problem was perl 5.10 and perl 5.8.9 broke binary swig compatibility. I started having the problem on new updates after the security fixes for perl. I have created a patch and port update would you like to try it? It is located here http://www.kodem.com/ports/ The change is swig is now required and must rebuild the perl interface files before compiling. Sorry it took so long but I did not see the problem until now. Ken Pav Lucistnik wrote: > No, it's using gcc from the base system. > > Ken Menzel p??e v p? 16. 01. 2009 v 09:28 -0500: > >> Did you install a gcc or other c compiler from ports? I have not tried >> 6.4, but I have compiled this on 6.3, 7.0 and 7.1 they all work fine. >> P.S. I am not subscribed to perl@freebsd.org. I hope someone else has >> an idea! >> >> Ken >> >> Pav Lucistnik wrote: >> >>> -------- P?eposlan? zpr?va -------- >>> >>> >>>> Od: User Ports-amd64 >>>> Komu: cvs@oook.cz >>>> P?edm?t: p5-XML-Xerces-2.7.0 failed on amd64 6 >>>> Datum: Thu, 15 Jan 2009 02:22:01 GMT >>>> >>>> Excerpt from the build log at >>>> >>>> http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.6.20090114102347/p5-XML-Xerces-2.7.0.log >>>> >>>> building p5-XML-Xerces-2.7.0 on hammer1.isc.gumbysoft.com >>>> in directory /usr2/pkgbuild/6/20090114102347/chroot/1055 >>>> building for: 6.4-STABLE amd64 >>>> maintained by: kenm@icarz.com >>>> port directory: /usr/ports/textproc/p5-XML-Xerces >>>> Makefile ident: $FreeBSD: ports/textproc/p5-XML-Xerces/Makefile,v 1.11 2008/04/17 14:29:26 araujo Exp $ >>>> >>>> [... lines trimmed ...] >>>> >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp:69331: error: too many initializers for `swig_command_info' >>>> Xerces.cpp: In function `void boot_XML__Xerces(CV*)': >>>> Xerces.cpp:69557: error: 'struct swig_command_info' has no member named 'wrapper' >>>> gmake: *** [Xerces.o] Error 1 >>>> *** Error code 2 >>>> >>>> Stop in /a/ports/textproc/p5-XML-Xerces. >>>> ================================================================ >>>> build of /usr/ports/textproc/p5-XML-Xerces ended at Thu Jan 15 02:22:01 UTC 2009 >>>> >>>> >>> >>> From bugmaster at FreeBSD.org Mon Mar 23 04:08:06 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Mar 23 04:10:26 2009 Subject: Current problem reports assigned to perl@FreeBSD.org Message-ID: <200903231108.n2NB80kR005240@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/131225 perl math/PDL: PDL-2.4.3_5: Unable to find PDL/pdldoc.db o ports/130175 perl Update math/PDL to version 2.4.4 o ports/129626 perl lang/p5-Tcl segfaults on i386 and amd64 on FreeBSD 7 o ports/121472 perl Loading perl scripts causes irc/xchat segmentation fau 4 problems total. From miwi at FreeBSD.org Tue Mar 24 08:26:03 2009 From: miwi at FreeBSD.org (miwi@FreeBSD.org) Date: Tue Mar 24 08:26:10 2009 Subject: ports/130175: Update math/PDL to version 2.4.4 Message-ID: <200903241525.n2OFPx3t060524@freefall.freebsd.org> Synopsis: Update math/PDL to version 2.4.4 State-Changed-From-To: open->closed State-Changed-By: miwi State-Changed-When: Tue Mar 24 15:25:59 UTC 2009 State-Changed-Why: already updated. http://www.freebsd.org/cgi/query-pr.cgi?pr=130175 From cm at therek.net Tue Mar 24 15:38:33 2009 From: cm at therek.net (Cezary Morga) Date: Tue Mar 24 15:39:10 2009 Subject: www / p5-HTML-Embperl In-Reply-To: <200903190714.11577.cm@therek.net> References: <49BDF024.8050006@ccstores.com> <200903190714.11577.cm@therek.net> Message-ID: <200903242338.21125.cm@therek.net> Well, I've been slacking a bit lately with this so this is what I've got so far. It build against mod_perl2+Apache2, libxml2 and libxslt. Xalan is not supported. http://therek.net/freebsd/ports/www/p5-Embperl/ -- Cezary Morga "If you live to be one hundred, you've got it made. Very few people die past that age." (George Burns) From edwin at FreeBSD.org Thu Mar 26 09:20:15 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Thu Mar 26 09:20:29 2009 Subject: ports/133096: [Update]textproc/p5-POSIX-Regex:update to 1.0001 Message-ID: <200903261620.n2QGKEfA086622@freefall.freebsd.org> Synopsis: [Update]textproc/p5-POSIX-Regex:update to 1.0001 Responsible-Changed-From-To: freebsd-ports-bugs->perl Responsible-Changed-By: edwin Responsible-Changed-When: Thu Mar 26 16:20:13 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=133096 From miwi at FreeBSD.org Thu Mar 26 12:21:13 2009 From: miwi at FreeBSD.org (miwi@FreeBSD.org) Date: Thu Mar 26 12:21:19 2009 Subject: ports/133096: [Update]textproc/p5-POSIX-Regex:update to 1.0001 Message-ID: <200903261921.n2QJLCHJ037118@freefall.freebsd.org> Synopsis: [Update]textproc/p5-POSIX-Regex:update to 1.0001 Responsible-Changed-From-To: perl->miwi Responsible-Changed-By: miwi Responsible-Changed-When: Thu Mar 26 19:21:12 UTC 2009 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=133096 From bugmaster at FreeBSD.org Mon Mar 30 04:08:05 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Mar 30 04:10:07 2009 Subject: Current problem reports assigned to perl@FreeBSD.org Message-ID: <200903301108.n2UB81Ec056000@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/131225 perl math/PDL: PDL-2.4.3_5: Unable to find PDL/pdldoc.db o ports/129626 perl lang/p5-Tcl segfaults on i386 and amd64 on FreeBSD 7 o ports/121472 perl Loading perl scripts causes irc/xchat segmentation fau 3 problems total.