From fernan.aguero at gmail.com Fri Jan 2 16:31:06 2009 From: fernan.aguero at gmail.com (Fernan Aguero) Date: Fri Jan 2 16:31:12 2009 Subject: Storable byteorder incompatibilities in different FreeBSD installations Message-ID: <520894aa0901020758o79bb1233teee539f6d599d10a@mail.gmail.com> Hi, I've been bitten by binary incompatibilitiess (bytorder, and/or byte sizes of ints, longs, and whatnot) between two perl installations (both on FreeBSD, using latest perl5.8 from ports). Upon investigation, it does not seem clear to me why the two installations should be different. And it prompted me to ask a few questions :) The context: I have a perl web application running under mod_perl in FreeBSD that dumps Perl data structures using Storable (binary format) and stores them, after encoding them with Base64, into a MySQL database. This application is under production and we have just deployed a test server for development in another FreeBSD box. Binary incompatibilities when reading the Storable binary data have been observed in the past when running the web application from Linux boxes (Ubuntu, i386 or amd64). Now, they have been also observed under FreeBSD in the new test server. This prompted us to do an investigation of the issue, because up to now we were assuming we would have no problems if we kept our production servers running FreeBSD. Below is the description of each box and the output of: perl -MConfig -le "print @Config{byteorder}" perl -MConfig -le "print @Config{shortsize}" perl -MConfig -le "print @Config{intsize}" perl -MConfig -le "print @Config{longsize}" perl -MConfig -le "print @Config{longlongsize}" perl -V (I'm not including the full output, due to its size, only diffs between selected cases) 1. Production server: FreeBSD-6.3, i386, perl5.8 from ports byteorder: 12345678 shortsize: 2 intsize: 4 longsize: 4 lonlongsize: 8 2. Development/test server: FreeBSD-7.1-RC1, amd64, perl5.8 from ports byteorder: 12345678 shortsize: 2 intsize: 4 longsize:8 lonlongsize: 8 3. Yet another server where we did some tests: FreeBSD-6.3, i386, perl5.8 from ports, perl5.8 standalone build perl5.8 from ports byteorder: 12345678 shortsize: 2 intsize: 4 longsize: 4 lonlongsize: 8 perl5.8, standalone build cd /usr/ports/lang/perl5.8 && make extract cd work/perl-5.8.8 && ./Configure (answering all questions with the default values except for the prefix installation) make && make test && make install (PREFIX is /home/fernan/perl) byteorder: 1234 shortsize: 2 intsize: 4 longsize: 4 lonlongsize: 8 As you can see, a Perl built outside of the ports system, has a different binary configuration (and should produce incompatible Storable images) as the Perl built from ports. As a sidenote, the binary configuration is similar to the one found in ubuntu pre-compiled binary perl packages (Linux, see below). Attached to this message is a diff of the output produced by 'perl -V' both for the perl built from the lang/perl5.8 port, and from the perl built from sources, as explained above. 4. Other test boxes: Ubuntu-8.10, i386, perl5.8 and perl5.10 byteorder: 1234 shortsize: 2 intsize: 4 longsize: 4 lonlongsize: 8 Up to now the questions that come to mind are: i) why is it that the perl built from ports produces binary dumps (using Storable) with incompatible byteorder with respect to the one built from Perl sources? (both perls were built on the same platform, same gcc) ii) Why does the Perl built from ports have an unusual byteorder? iii) Why does Perl built from ports in different platforms produce incompatible binary dumps (this time because of a difference in longsize)? Is it because it was compiled with a different gcc (3.4.6 in FBSD-6.3 vs 4.2.1 in FBSD-7.1)? Or because it was compiled in a different platform (amd64 vs i386)? Reading the Configure script that comes with perl-5.8.8, and regarding the byteorder, it says that: "A big-endian machine like a Pyramid or a Motorola 680?0 chip will come out to 4321. A little-endian machine like a Vax or an Intel 80?86 chip would be 1234. Other machines may have weird orders like 3412. A Cray will report 87654321, an Alpha will report 12345678. If the test program works the default is probably right. I'm now running the test program..." So why is it that building Perl outside of the ports system makes the test program report '1234' which is what I would expect from an i386 box, while it gives '12345678' when running from within the ports system? Why this unusual byteorder? And now for a pragmatic and urgent question: iv) how can I use the ports system to build a Perl in different FBSD boxes that would result in the same binary configuration (byteorder, shortsize, intsize, etc.) to guarantee it would produce compatible (i.e. readable from other FBSD boxes) dumps of Perl data structures? Sorry for the long post, and have yourselves a happy and peaceful 2009! -- fernan -------------- next part -------------- A non-text attachment was scrubbed... Name: perl.gama.diff Type: text/x-patch Size: 4574 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090102/2e58d6e2/perl.gama.bin From tobez at tobez.org Fri Jan 2 17:00:02 2009 From: tobez at tobez.org (Anton Berezin) Date: Fri Jan 2 17:00:08 2009 Subject: Storable byteorder incompatibilities in different FreeBSD installations In-Reply-To: <520894aa0901020758o79bb1233teee539f6d599d10a@mail.gmail.com> References: <520894aa0901020758o79bb1233teee539f6d599d10a@mail.gmail.com> Message-ID: <20090102164439.GF40649@heechee.tobez.org> On Fri, Jan 02, 2009 at 01:58:06PM -0200, Fernan Aguero wrote: > I've been bitten by binary incompatibilitiess (bytorder, and/or byte > sizes of ints, longs, and whatnot) between two perl installations > (both on FreeBSD, using latest perl5.8 from ports). [...] > Binary incompatibilities when reading the Storable binary data have > been observed in the past when running the web application from Linux > boxes (Ubuntu, i386 or amd64). > So why is it that building Perl outside of the ports system makes the > test program report '1234' which is what I would expect from an i386 > box, while it gives '12345678' when running from within the ports > system? Why this unusual byteorder? This is because of PERL_64BITINT (aka -Duse64bitint) is the default with the port. > And now for a pragmatic and urgent question: > iv) how can I use the ports system to build a Perl in different FBSD > boxes that would result in the same binary configuration (byteorder, > shortsize, intsize, etc.) to guarantee it would produce compatible > (i.e. readable from other FBSD boxes) dumps of Perl data structures? Uncheck PERL_64BITINT in the configuration dialog. (make rmconfig first) Apart from that, do you actually use "nstore" variants of Storable functions? If you use it consistently in you application, you might find out that the problem disappears, and it would not matter what platform you use. Cheers, \Anton. -- There is no beauty in entropy. -- Eliezer Yudkowsky From fernan.aguero at gmail.com Sat Jan 3 12:33:23 2009 From: fernan.aguero at gmail.com (Fernan Aguero) Date: Sat Jan 3 12:33:30 2009 Subject: Storable byteorder incompatibilities in different FreeBSD installations In-Reply-To: <20090102164439.GF40649@heechee.tobez.org> References: <520894aa0901020758o79bb1233teee539f6d599d10a@mail.gmail.com> <20090102164439.GF40649@heechee.tobez.org> Message-ID: <520894aa0901030433i7a103ba7i4236ae17b83c6eae@mail.gmail.com> Hi Anton, On Fri, Jan 2, 2009 at 2:44 PM, Anton Berezin wrote: > On Fri, Jan 02, 2009 at 01:58:06PM -0200, Fernan Aguero wrote: > >> I've been bitten by binary incompatibilitiess (bytorder, and/or byte >> sizes of ints, longs, and whatnot) between two perl installations >> (both on FreeBSD, using latest perl5.8 from ports). > > [...] > >> Binary incompatibilities when reading the Storable binary data have >> been observed in the past when running the web application from Linux >> boxes (Ubuntu, i386 or amd64). > >> So why is it that building Perl outside of the ports system makes the >> test program report '1234' which is what I would expect from an i386 >> box, while it gives '12345678' when running from within the ports >> system? Why this unusual byteorder? > > This is because of PERL_64BITINT (aka -Duse64bitint) is the > default with the port. That is only useful in i386. In amd64, it doesn't change anything. With or Without that define, the outcome is always: perl -MConfig -le "print @Config{byteorder}" 12345678 perl -MConfig -le "print @Config{shortsize}" 2 perl -MConfig -le "print @Config{intsize}" 4 perl -MConfig -le "print @Config{longsize}" 8 perl -MConfig -le "print @Config{longlongsize}" 8 [tested in FreeBSD-7.1 RC1, amd64] In FreeBSD-6.3, i386, unchecking PERL_64BITINT would give: perl -MConfig -le "print @Config{byteorder}" 1234 perl -MConfig -le "print @Config{longsize}" 4 [all others being equal] In FreeBSD-6.3, i386 with PERL_64BITINT: perl -MConfig -le "print @Config{byteorder}" 12345678 perl -MConfig -le "print @Config{longsize}" 4 [all others being equal] Apart from the byteorder issue, the other issue which I raised in my post, was also the incompatibility in 'longsize' between two perl instances built from ports, in different boxes. In this case, the perl built in a FBSD-6.3, i386 box has a longsize of 4, whereas the same perl built in FBSD-7.1, amd64 has a longsize of 8. In both cases they were compiled with PERL_64BITINT (the default for the port), and in both cases the byteorder is the same! How can I build a perl with a byteorder of 12345678, and a longsize of 4, in an amd64 platform? Is that possible at all? Looking at the output of perl -V in these different Perls, in the Compiler section I see (from the diff attached in my previous message, this is from a build in i386) - intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234 + intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=12345678 Can we toggle these compiler options? >> And now for a pragmatic and urgent question: >> iv) how can I use the ports system to build a Perl in different FBSD >> boxes that would result in the same binary configuration (byteorder, >> shortsize, intsize, etc.) to guarantee it would produce compatible >> (i.e. readable from other FBSD boxes) dumps of Perl data structures? > > Uncheck PERL_64BITINT in the configuration dialog. (make rmconfig > first) > > Apart from that, do you actually use "nstore" variants of Storable > functions? If you use it consistently in you application, you > might find out that the problem disappears, and it would not > matter what platform you use. I know about nstore, and I am switching my code to use nstore for future releases. But, as it stands now, I've already made the mistake of using plain 'store' in all my production code, which means I have lots of data already written in the DB that I need to be able to read with binary-compatible perl/Storable instances. I can do that currently using the perl instance I have in FBSD-6, i386. But I was wondering if it's possible to make the port build a perl with a different 'binary' configuration. You might want to think about this problem in the following terms: i) you have lots of data dumped from perl in a specific binary format ii) your old hardware is gone/lost iii) you need to build a perl in a new box, perhaps in a different platform, that would read these Storable dumps. Is this possible using the FreeBSD perl port? In my case, this would be translated to: can I build a perl instance with a byteorder of 12345678, and a longsize of 4 in a FreeBSD-7.1, amd64 box? Cheers, Fernan > Cheers, > \Anton. -- fernan From tobez at tobez.org Sat Jan 3 13:57:19 2009 From: tobez at tobez.org (Anton Berezin) Date: Sat Jan 3 13:57:26 2009 Subject: Storable byteorder incompatibilities in different FreeBSD installations In-Reply-To: <520894aa0901030433i7a103ba7i4236ae17b83c6eae@mail.gmail.com> References: <520894aa0901020758o79bb1233teee539f6d599d10a@mail.gmail.com> <20090102164439.GF40649@heechee.tobez.org> <520894aa0901030433i7a103ba7i4236ae17b83c6eae@mail.gmail.com> Message-ID: <20090103135718.GC41513@heechee.tobez.org> Fernan, On Sat, Jan 03, 2009 at 10:33:22AM -0200, Fernan Aguero wrote: > Apart from the byteorder issue, the other issue which I raised in my > post, was also the incompatibility in 'longsize' between two perl > instances built from ports, in different boxes. > > In this case, the perl built in a FBSD-6.3, i386 box has a longsize of > 4, whereas the same perl built in FBSD-7.1, amd64 has a longsize of 8. > In both cases they were compiled with PERL_64BITINT (the default for > the port), and in both cases the byteorder is the same! > > How can I build a perl with a byteorder of 12345678, and a longsize of > 4, in an amd64 platform? Is that possible at all? Not really. Amd64 is a 64-bit platform, meaning sizeof(long) = 8. I am pretty positive that the same is true for x86-64 Linux. That's more or less what "12345678" indicates. At any rate, this is the application design issue. The practical solution in your case would be to take an offline copy of the DB, and to go through every record and convert it into a KNOWN to you binary format. I have not done the relevant testing, so I do not even know whether nstore() will do what you want - after all, it only handles the byteorder issues, not integer size issues. It is dangerous to make assumptions about bytesizes of various structures on different architectures - you've got to do some sort of conversion yourself, "native to known" during the store operation, and "known to native" during the retrieve operation. This is just a common sense design principle. Cheers, \Anton. -- There is no beauty in entropy. -- Eliezer Yudkowsky From fernan.aguero at gmail.com Sat Jan 3 14:22:03 2009 From: fernan.aguero at gmail.com (Fernan Aguero) Date: Sat Jan 3 14:22:09 2009 Subject: Storable byteorder incompatibilities in different FreeBSD installations In-Reply-To: <20090103135718.GC41513@heechee.tobez.org> References: <520894aa0901020758o79bb1233teee539f6d599d10a@mail.gmail.com> <20090102164439.GF40649@heechee.tobez.org> <520894aa0901030433i7a103ba7i4236ae17b83c6eae@mail.gmail.com> <20090103135718.GC41513@heechee.tobez.org> Message-ID: <520894aa0901030622k173d9eu2a2792758abbcfee@mail.gmail.com> On Sat, Jan 3, 2009 at 11:57 AM, Anton Berezin wrote: > Fernan, > > On Sat, Jan 03, 2009 at 10:33:22AM -0200, Fernan Aguero wrote: > >> Apart from the byteorder issue, the other issue which I raised in my >> post, was also the incompatibility in 'longsize' between two perl >> instances built from ports, in different boxes. >> >> In this case, the perl built in a FBSD-6.3, i386 box has a longsize of >> 4, whereas the same perl built in FBSD-7.1, amd64 has a longsize of 8. >> In both cases they were compiled with PERL_64BITINT (the default for >> the port), and in both cases the byteorder is the same! >> >> How can I build a perl with a byteorder of 12345678, and a longsize of >> 4, in an amd64 platform? Is that possible at all? > > Not really. Amd64 is a 64-bit platform, meaning sizeof(long) = 8. I am > pretty positive that the same is true for x86-64 Linux. That's more or less > what "12345678" indicates. > > At any rate, this is the application design issue. The practical solution > in your case would be to take an offline copy of the DB, and to go through > every record and convert it into a KNOWN to you binary format. I have not > done the relevant testing, so I do not even know whether nstore() will do > what you want - after all, it only handles the byteorder issues, not integer > size issues. I am doing these tests as we speak, and will convert all my data using nstore/nfreeze. Thanks. > Cheers, > \Anton. -- fernan From edwin at FreeBSD.org Mon Jan 5 01:40:13 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Mon Jan 5 01:40:24 2009 Subject: ports/130175: Update math/PDL to version 2.4.4 Message-ID: <200901050140.n051eCUh038538@freefall.freebsd.org> Synopsis: Update math/PDL to version 2.4.4 Responsible-Changed-From-To: freebsd-ports-bugs->perl Responsible-Changed-By: edwin Responsible-Changed-When: Mon Jan 5 01:40:12 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=130175 From bugmaster at FreeBSD.org Mon Jan 5 11:08:01 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 5 11:10:12 2009 Subject: Current problem reports assigned to perl@FreeBSD.org Message-ID: <200901051107.n05B7xEs004092@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/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/129366 perl devel/p5-ExtUtils-MakeMaker - port trying Install non- o ports/121472 perl Loading perl scripts causes irc/xchat segmentation fau 4 problems total. From bugmaster at FreeBSD.org Mon Jan 12 03:08:02 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 12 03:10:16 2009 Subject: Current problem reports assigned to perl@FreeBSD.org Message-ID: <200901121107.n0CB7x4v093287@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/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/129366 perl devel/p5-ExtUtils-MakeMaker - port trying Install non- o ports/121472 perl Loading perl scripts causes irc/xchat segmentation fau 4 problems total. From edwin at FreeBSD.org Wed Jan 14 11:10:18 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Wed Jan 14 11:10:29 2009 Subject: ports/130558: [PATCH] net/p5-Net-Amazon-S3: Add missing dependencies Message-ID: <200901141910.n0EJAGK6040960@freefall.freebsd.org> Synopsis: [PATCH] net/p5-Net-Amazon-S3: Add missing dependencies Responsible-Changed-From-To: freebsd-ports-bugs->perl Responsible-Changed-By: edwin Responsible-Changed-When: Wed Jan 14 19:10:15 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=130558 From pav at FreeBSD.org Wed Jan 14 12:59:31 2009 From: pav at FreeBSD.org (Pav Lucistnik) Date: Wed Jan 14 13:00:02 2009 Subject: [Fwd: p5-ExtUtils-MakeMaker-6.48 failed on amd64 6] Message-ID: <1231965141.61866.12.camel@hood.oook.cz> -------- P?eposlan? zpr?va -------- > Od: User Ports-amd64 > Komu: cvs@oook.cz > P?edm?t: p5-ExtUtils-MakeMaker-6.48 failed on amd64 6 > Datum: Wed, 14 Jan 2009 12:07:17 GMT > > You can also find this build log at > > http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.6.20090114102347/p5-ExtUtils-MakeMaker-6.48.log > > building p5-ExtUtils-MakeMaker-6.48 on gohan12.freebsd.org > in directory /x/pkgbuild/6/20090114102347/chroot/59 > building for: 6.4-STABLE amd64 > maintained by: perl@FreeBSD.org > port directory: /usr/ports/devel/p5-ExtUtils-MakeMaker > Makefile ident: $FreeBSD: ports/devel/p5-ExtUtils-MakeMaker/Makefile,v 1.16 2008/10/28 16:48:58 erwin Exp $ > build started at Wed Jan 14 12:05:52 UTC 2009 > FETCH_DEPENDS= > PATCH_DEPENDS=perl-5.8.9.tbz > EXTRACT_DEPENDS=perl-5.8.9.tbz > BUILD_DEPENDS=perl-5.8.9.tbz > RUN_DEPENDS=perl-5.8.9.tbz > prefixes: LOCALBASE=usr/local X11BASE=usr/local > add_pkg > ================================================================ > ======================================== > => ExtUtils-MakeMaker-6.48.tar.gz doesn't seem to exist in /tmp/distfiles/. > => Attempting to fetch from ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/. > ExtUtils-MakeMaker-6.48.tar.gz 248 kB 3356 kBps > => MD5 Checksum OK for ExtUtils-MakeMaker-6.48.tar.gz. > => SHA256 Checksum OK for ExtUtils-MakeMaker-6.48.tar.gz. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Extracting for p5-ExtUtils-MakeMaker-6.48 > => MD5 Checksum OK for ExtUtils-MakeMaker-6.48.tar.gz. > => SHA256 Checksum OK for ExtUtils-MakeMaker-6.48.tar.gz. > ===> p5-ExtUtils-MakeMaker-6.48 depends on file: /usr/local/bin/perl5.8.9 - found > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Patching for p5-ExtUtils-MakeMaker-6.48 > ===> p5-ExtUtils-MakeMaker-6.48 depends on file: /usr/local/bin/perl5.8.9 - found > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> p5-ExtUtils-MakeMaker-6.48 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Configuring for p5-ExtUtils-MakeMaker-6.48 > Checking if your kit is complete... > Looks good > Using included version of ExtUtils::Packlist (1.43) as it is newer than the installed version (undef). > Writing Makefile for ExtUtils::MakeMaker > ===> Building for p5-ExtUtils-MakeMaker-6.48 > cp lib/ExtUtils/MM_OS2.pm blib/lib/ExtUtils/MM_OS2.pm > cp lib/ExtUtils/MakeMaker.pm blib/lib/ExtUtils/MakeMaker.pm > cp lib/ExtUtils/MM_VOS.pm blib/lib/ExtUtils/MM_VOS.pm > cp lib/ExtUtils/MM_Unix.pm blib/lib/ExtUtils/MM_Unix.pm > cp lib/ExtUtils/Mksymlists.pm blib/lib/ExtUtils/Mksymlists.pm > cp lib/ExtUtils/MM.pm blib/lib/ExtUtils/MM.pm > cp lib/ExtUtils/MM_Win32.pm blib/lib/ExtUtils/MM_Win32.pm > cp lib/ExtUtils/MM_UWIN.pm blib/lib/ExtUtils/MM_UWIN.pm > cp lib/ExtUtils/testlib.pm blib/lib/ExtUtils/testlib.pm > cp lib/ExtUtils/MY.pm blib/lib/ExtUtils/MY.pm > cp inc/ExtUtils/Packlist.pm blib/lib/ExtUtils/Packlist.pm > cp lib/ExtUtils/MakeMaker/vmsish.pm blib/lib/ExtUtils/MakeMaker/vmsish.pm > cp lib/ExtUtils/MM_DOS.pm blib/lib/ExtUtils/MM_DOS.pm > cp lib/ExtUtils/MM_Cygwin.pm blib/lib/ExtUtils/MM_Cygwin.pm > cp lib/ExtUtils/MM_MacOS.pm blib/lib/ExtUtils/MM_MacOS.pm > cp lib/ExtUtils/MM_VMS.pm blib/lib/ExtUtils/MM_VMS.pm > cp lib/ExtUtils/MM_Win95.pm blib/lib/ExtUtils/MM_Win95.pm > cp lib/ExtUtils/MM_BeOS.pm blib/lib/ExtUtils/MM_BeOS.pm > cp lib/ExtUtils/Liblist.pm blib/lib/ExtUtils/Liblist.pm > cp lib/ExtUtils/MakeMaker/Tutorial.pod blib/lib/ExtUtils/MakeMaker/Tutorial.pod > cp lib/ExtUtils/MM_AIX.pm blib/lib/ExtUtils/MM_AIX.pm > cp lib/ExtUtils/MM_Darwin.pm blib/lib/ExtUtils/MM_Darwin.pm > cp lib/ExtUtils/Liblist/Kid.pm blib/lib/ExtUtils/Liblist/Kid.pm > cp lib/ExtUtils/Mkbootstrap.pm blib/lib/ExtUtils/Mkbootstrap.pm > cp lib/ExtUtils/MM_QNX.pm blib/lib/ExtUtils/MM_QNX.pm > cp lib/ExtUtils/MakeMaker/FAQ.pod blib/lib/ExtUtils/MakeMaker/FAQ.pod > cp lib/ExtUtils/Command/MM.pm blib/lib/ExtUtils/Command/MM.pm > cp lib/ExtUtils/MakeMaker/Config.pm blib/lib/ExtUtils/MakeMaker/Config.pm > cp lib/ExtUtils/MakeMaker/bytes.pm blib/lib/ExtUtils/MakeMaker/bytes.pm > cp lib/ExtUtils/MM_NW5.pm blib/lib/ExtUtils/MM_NW5.pm > cp lib/ExtUtils/MM_Any.pm blib/lib/ExtUtils/MM_Any.pm > Manifying blib/man3/ExtUtils::MakeMaker.3 > Manifying blib/man3/ExtUtils::MM_OS2.3 > Manifying blib/man3/ExtUtils::MM_VOS.3 > Manifying blib/man3/ExtUtils::MM_Unix.3 > Manifying blib/man3/ExtUtils::Mksymlists.3 > Manifying blib/man3/ExtUtils::MM.3 > Manifying blib/man3/ExtUtils::MM_Win32.3 > Manifying blib/man3/ExtUtils::MM_UWIN.3 > Manifying blib/man3/ExtUtils::testlib.3 > Manifying blib/man3/ExtUtils::MM_Cygwin.3 > Manifying blib/man3/ExtUtils::MM_DOS.3 > Manifying blib/man3/ExtUtils::MakeMaker::vmsish.3 > Manifying blib/man3/ExtUtils::Packlist.3 > Manifying blib/man3/ExtUtils::MY.3 > Manifying blib/man3/ExtUtils::MM_MacOS.3 > Manifying blib/man3/ExtUtils::MM_VMS.3 > Manifying blib/man3/ExtUtils::MM_Win95.3 > Manifying blib/man3/ExtUtils::MM_BeOS.3 > Manifying blib/man3/ExtUtils::Liblist.3 > Manifying blib/man3/ExtUtils::MM_Darwin.3 > Manifying blib/man3/ExtUtils::MM_AIX.3 > Manifying blib/man3/ExtUtils::MakeMaker::Tutorial.3 > Manifying blib/man3/ExtUtils::Mkbootstrap.3 > Manifying blib/man3/ExtUtils::MakeMaker::FAQ.3 > Manifying blib/man3/ExtUtils::MM_QNX.3 > Manifying blib/man3/ExtUtils::Command::MM.3 > Manifying blib/man3/ExtUtils::MakeMaker::Config.3 > Manifying blib/man3/ExtUtils::MakeMaker::bytes.3 > Manifying blib/man3/ExtUtils::MM_NW5.3 > Manifying blib/man3/ExtUtils::MM_Any.3 > ================================================================ > ======================================== > make: don't know how to make regression-test(continuing) > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > skipping perl-5.8.9, already added > ===> Installing for p5-ExtUtils-MakeMaker-6.48 > ===> p5-ExtUtils-MakeMaker-6.48 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Generating temporary packing list > ===> Checking if devel/p5-ExtUtils-MakeMaker already installed > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_OS2.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MakeMaker.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_VOS.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_Unix.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/Mksymlists.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_Win32.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_UWIN.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/testlib.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MY.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/Packlist.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_DOS.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_Cygwin.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_MacOS.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_VMS.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_Win95.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_BeOS.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/Liblist.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_AIX.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_Darwin.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/Mkbootstrap.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_QNX.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_NW5.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MM_Any.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MakeMaker/vmsish.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MakeMaker/Tutorial.pod > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MakeMaker/FAQ.pod > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MakeMaker/Config.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/MakeMaker/bytes.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/Liblist/Kid.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/ExtUtils/Command/MM.pm > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MakeMaker.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_OS2.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_VOS.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_Unix.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::Mksymlists.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_Win32.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_UWIN.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::testlib.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_Cygwin.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_DOS.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MakeMaker::vmsish.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::Packlist.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MY.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_MacOS.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_VMS.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_Win95.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_BeOS.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::Liblist.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_Darwin.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_AIX.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MakeMaker::Tutorial.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::Mkbootstrap.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MakeMaker::FAQ.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_QNX.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::Command::MM.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MakeMaker::Config.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MakeMaker::bytes.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_NW5.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::MM_Any.3 > Writing /usr/local/lib/perl5/site_perl/5.8.9/mach/auto/ExtUtils/MakeMaker/.packlist > ===> Compressing manual pages for p5-ExtUtils-MakeMaker-6.48 > gzip: can't stat: /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::Installed.3: No such file or directory > gzip: can't stat: /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::Install.3: No such file or directory > gzip: can't stat: /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::Manifest.3: No such file or directory > gzip: can't stat: /usr/local/lib/perl5/5.8.9/man/man3/ExtUtils::Command.3: No such file or directory > ===> Registering installation for p5-ExtUtils-MakeMaker-6.48 > ================================================================ > ======================================== > ===> Building package for p5-ExtUtils-MakeMaker-6.48 > tar: lib/perl5/5.8.9/man/man3/ExtUtils::Installed.3.gz: Cannot stat: No such file or directory > tar: lib/perl5/5.8.9/man/man3/ExtUtils::Install.3.gz: Cannot stat: No such file or directory > tar: lib/perl5/5.8.9/man/man3/ExtUtils::Manifest.3.gz: Cannot stat: No such file or directory > tar: lib/perl5/5.8.9/man/man3/ExtUtils::Command.3.gz: Cannot stat: No such file or directory > tar: lib/perl5/site_perl/5.8.9/ExtUtils/Install.pm: Cannot stat: No such file or directory > tar: lib/perl5/site_perl/5.8.9/ExtUtils/Installed.pm: Cannot stat: No such file or directory > tar: lib/perl5/site_perl/5.8.9/ExtUtils/MANIFEST.SKIP: Cannot stat: No such file or directory > tar: lib/perl5/site_perl/5.8.9/ExtUtils/Manifest.pm: Cannot stat: No such file or directory > tar: lib/perl5/site_perl/5.8.9/ExtUtils/Command.pm: Cannot stat: No such file or directory > tar: Error exit delayed from previous errors. > pkg_create: make_dist: tar command failed with code 256 > Creating package /tmp/packages/All/p5-ExtUtils-MakeMaker-6.48.tbz > Registering depends: perl-5.8.9. > Creating bzip'd tar ball in '/tmp/packages/All/p5-ExtUtils-MakeMaker-6.48.tbz' > *** Error code 1 > > Stop in /a/ports/devel/p5-ExtUtils-MakeMaker. > ================================================================ > build of /usr/ports/devel/p5-ExtUtils-MakeMaker ended at Wed Jan 14 12:07:14 UTC 2009 -- Pav Lucistnik It's the classic Microsoft security-bulletin formula: "The vulnerability is important (never dangerous); you have nothing to fear and no reason to regret trusting us; we have no intention of apologizing for it or even explaining it adequately; now go get your patch, shut up, and be grateful nothing bad has happened. -- The Register -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090114/b52a541d/attachment.pgp From pav at FreeBSD.org Wed Jan 14 13:06:29 2009 From: pav at FreeBSD.org (Pav Lucistnik) Date: Wed Jan 14 13:06:35 2009 Subject: [Fwd: p5-Module-CoreList-2.15 failed on amd64 6] Message-ID: <1231965559.61866.13.camel@hood.oook.cz> -------- P?eposlan? zpr?va -------- > Od: User Ports-amd64 > Komu: cvs@oook.cz > P?edm?t: p5-Module-CoreList-2.15 failed on amd64 6 > Datum: Wed, 14 Jan 2009 12:07:20 GMT > > You can also find this build log at > > http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.6.20090114102347/p5-Module-CoreList-2.15.log > > building p5-Module-CoreList-2.15 on gohan12.freebsd.org > in directory /x/pkgbuild/6/20090114102347/chroot/61 > building for: 6.4-STABLE amd64 > maintained by: lth@FreeBSD.org > port directory: /usr/ports/devel/p5-Module-CoreList > Makefile ident: $FreeBSD: ports/devel/p5-Module-CoreList/Makefile,v 1.18 2008/04/05 09:13:39 lth Exp $ > build started at Wed Jan 14 12:05:58 UTC 2009 > FETCH_DEPENDS= > PATCH_DEPENDS=perl-5.8.9.tbz > EXTRACT_DEPENDS=perl-5.8.9.tbz > BUILD_DEPENDS=perl-5.8.9.tbz > RUN_DEPENDS=perl-5.8.9.tbz > prefixes: LOCALBASE=usr/local X11BASE=usr/local > add_pkg > ================================================================ > ======================================== > => Module-CoreList-2.15.tar.gz doesn't seem to exist in /tmp/distfiles/. > => Attempting to fetch from ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/. > Module-CoreList-2.15.tar.gz 40 kB 1078 kBps > => MD5 Checksum OK for Module-CoreList-2.15.tar.gz. > => SHA256 Checksum OK for Module-CoreList-2.15.tar.gz. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Extracting for p5-Module-CoreList-2.15 > => MD5 Checksum OK for Module-CoreList-2.15.tar.gz. > => SHA256 Checksum OK for Module-CoreList-2.15.tar.gz. > ===> p5-Module-CoreList-2.15 depends on file: /usr/local/bin/perl5.8.9 - found > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Patching for p5-Module-CoreList-2.15 > ===> p5-Module-CoreList-2.15 depends on file: /usr/local/bin/perl5.8.9 - found > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> p5-Module-CoreList-2.15 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Configuring for p5-Module-CoreList-2.15 > Checking if your kit is complete... > Looks good > Writing Makefile for Module::CoreList > ===> Building for p5-Module-CoreList-2.15 > cp lib/Module/CoreList.pm blib/lib/Module/CoreList.pm > cp corelist blib/script/corelist > /usr/local/bin/perl5.8.9 "-MExtUtils::MY" -e "MY->fixin(shift)" blib/script/corelist > Manifying blib/man1/corelist.1 > Manifying blib/man3/Module::CoreList.3 > ================================================================ > ======================================== > make: don't know how to make regression-test(continuing) > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > skipping perl-5.8.9, already added > ===> Installing for p5-Module-CoreList-2.15 > ===> p5-Module-CoreList-2.15 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Generating temporary packing list > ===> Checking if devel/p5-Module-CoreList already installed > Installing /usr/local/lib/perl5/site_perl/5.8.9/Module/CoreList.pm > Installing /usr/local/man/man1/corelist.1 > Installing /usr/local/lib/perl5/5.8.9/man/man3/Module::CoreList.3 > Installing /usr/local/bin/corelist > Writing /usr/local/lib/perl5/site_perl/5.8.9/mach/auto/Module/CoreList/.packlist > ===> Compressing manual pages for p5-Module-CoreList-2.15 > ===> Registering installation for p5-Module-CoreList-2.15 > ================================================================ > ======================================== > ===> Building package for p5-Module-CoreList-2.15 > Creating package /tmp/packages/All/p5-Module-CoreList-2.15.tbz > Registering depends: perl-5.8.9. > Creating bzip'd tar ball in '/tmp/packages/All/p5-Module-CoreList-2.15.tbz' > Deleting p5-Module-CoreList-2.15 > ================================================================ > > === Checking filesystem state > list of files present before this port was installed but missing after it was deinstalled) > ./usr/local/bin/corelist missing > ./usr/local/man/man1/corelist.1.gz missing > ================================================================ > build of /usr/ports/devel/p5-Module-CoreList ended at Wed Jan 14 12:07:18 UTC 2009 -- Pav Lucistnik Any Palm app requiring an 90+ page manual has lost its vision. -- words about DateBk4 on Action Names list -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090114/50a87192/attachment.pgp From pav at FreeBSD.org Wed Jan 14 13:15:08 2009 From: pav at FreeBSD.org (Pav Lucistnik) Date: Wed Jan 14 13:15:17 2009 Subject: [Fwd: p5-Test-Harness-3.14 failed on amd64 6] Message-ID: <1231967699.61866.15.camel@hood.oook.cz> -------- P?eposlan? zpr?va -------- > Od: User Ports-amd64 > Komu: cvs@oook.cz > P?edm?t: p5-Test-Harness-3.14 failed on amd64 6 > Datum: Wed, 14 Jan 2009 12:34:13 GMT > > You can also find this build log at > > http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.6.20090114102347/p5-Test-Harness-3.14.log > > building p5-Test-Harness-3.14 on hammer3.isc.gumbysoft.com > in directory /usr2/pkgbuild/6/20090114102347/chroot/138 > building for: 6.4-STABLE amd64 > maintained by: perl@FreeBSD.org > port directory: /usr/ports/devel/p5-Test-Harness > Makefile ident: $FreeBSD: ports/devel/p5-Test-Harness/Makefile,v 1.36 2008/09/23 12:18:49 miwi Exp $ > build started at Wed Jan 14 12:33:21 UTC 2009 > FETCH_DEPENDS= > PATCH_DEPENDS=perl-5.8.9.tbz > EXTRACT_DEPENDS=perl-5.8.9.tbz > BUILD_DEPENDS=perl-5.8.9.tbz > RUN_DEPENDS=perl-5.8.9.tbz > prefixes: LOCALBASE=usr/local X11BASE=usr/local > add_pkg > ================================================================ > ======================================== > => Test-Harness-3.14.tar.gz doesn't seem to exist in /tmp/distfiles/. > => Attempting to fetch from ftp://freebsd.isc.org/pub/FreeBSD/ports/distfiles/. > Test-Harness-3.14.tar.gz 195 kB 3046 kBps > => MD5 Checksum OK for Test-Harness-3.14.tar.gz. > => SHA256 Checksum OK for Test-Harness-3.14.tar.gz. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Extracting for p5-Test-Harness-3.14 > => MD5 Checksum OK for Test-Harness-3.14.tar.gz. > => SHA256 Checksum OK for Test-Harness-3.14.tar.gz. > ===> p5-Test-Harness-3.14 depends on file: /usr/local/bin/perl5.8.9 - found > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Patching for p5-Test-Harness-3.14 > ===> p5-Test-Harness-3.14 depends on file: /usr/local/bin/perl5.8.9 - found > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> p5-Test-Harness-3.14 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Configuring for p5-Test-Harness-3.14 > Checking if your kit is complete... > Looks good > Writing Makefile for Test::Harness > ===> Building for p5-Test-Harness-3.14 > cp lib/TAP/Parser/Result/Pragma.pm blib/lib/TAP/Parser/Result/Pragma.pm > cp lib/App/Prove/State/Result.pm blib/lib/App/Prove/State/Result.pm > cp lib/TAP/Parser/Iterator/Array.pm blib/lib/TAP/Parser/Iterator/Array.pm > cp lib/TAP/Base.pm blib/lib/TAP/Base.pm > cp lib/TAP/Formatter/Console/ParallelSession.pm blib/lib/TAP/Formatter/Console/ParallelSession.pm > cp lib/TAP/Parser/Result.pm blib/lib/TAP/Parser/Result.pm > cp lib/TAP/Formatter/Console/Session.pm blib/lib/TAP/Formatter/Console/Session.pm > cp lib/TAP/Parser/Result/YAML.pm blib/lib/TAP/Parser/Result/YAML.pm > cp lib/TAP/Parser/Scheduler/Job.pm blib/lib/TAP/Parser/Scheduler/Job.pm > cp lib/TAP/Parser.pm blib/lib/TAP/Parser.pm > cp lib/TAP/Parser/IteratorFactory.pm blib/lib/TAP/Parser/IteratorFactory.pm > cp lib/TAP/Parser/Iterator.pm blib/lib/TAP/Parser/Iterator.pm > cp lib/TAP/Formatter/Color.pm blib/lib/TAP/Formatter/Color.pm > cp lib/TAP/Parser/Iterator/Process.pm blib/lib/TAP/Parser/Iterator/Process.pm > cp lib/TAP/Parser/Grammar.pm blib/lib/TAP/Parser/Grammar.pm > cp HACKING.pod blib/lib/Test/HACKING.pod > cp lib/Test/Harness.pm blib/lib/Test/Harness.pm > cp lib/TAP/Parser/ResultFactory.pm blib/lib/TAP/Parser/ResultFactory.pm > cp lib/TAP/Parser/Utils.pm blib/lib/TAP/Parser/Utils.pm > cp lib/TAP/Parser/Result/Bailout.pm blib/lib/TAP/Parser/Result/Bailout.pm > cp lib/TAP/Object.pm blib/lib/TAP/Object.pm > cp lib/TAP/Parser/Multiplexer.pm blib/lib/TAP/Parser/Multiplexer.pm > cp lib/TAP/Parser/Result/Version.pm blib/lib/TAP/Parser/Result/Version.pm > cp lib/TAP/Parser/YAMLish/Writer.pm blib/lib/TAP/Parser/YAMLish/Writer.pm > cp lib/TAP/Parser/Result/Unknown.pm blib/lib/TAP/Parser/Result/Unknown.pm > cp lib/TAP/Parser/YAMLish/Reader.pm blib/lib/TAP/Parser/YAMLish/Reader.pm > cp lib/TAP/Parser/Scheduler.pm blib/lib/TAP/Parser/Scheduler.pm > cp lib/TAP/Parser/Result/Plan.pm blib/lib/TAP/Parser/Result/Plan.pm > cp lib/TAP/Parser/Source/Perl.pm blib/lib/TAP/Parser/Source/Perl.pm > cp lib/TAP/Parser/Result/Test.pm blib/lib/TAP/Parser/Result/Test.pm > cp lib/App/Prove/State/Result/Test.pm blib/lib/App/Prove/State/Result/Test.pm > cp lib/TAP/Parser/Result/Comment.pm blib/lib/TAP/Parser/Result/Comment.pm > cp lib/TAP/Parser/Source.pm blib/lib/TAP/Parser/Source.pm > cp lib/TAP/Formatter/Console.pm blib/lib/TAP/Formatter/Console.pm > cp lib/TAP/Parser/Iterator/Stream.pm blib/lib/TAP/Parser/Iterator/Stream.pm > cp lib/App/Prove.pm blib/lib/App/Prove.pm > cp lib/App/Prove/State.pm blib/lib/App/Prove/State.pm > cp lib/TAP/Harness.pm blib/lib/TAP/Harness.pm > cp lib/TAP/Parser/Aggregator.pm blib/lib/TAP/Parser/Aggregator.pm > cp lib/TAP/Parser/Scheduler/Spinner.pm blib/lib/TAP/Parser/Scheduler/Spinner.pm > cp bin/prove blib/script/prove > /usr/local/bin/perl5.8.9 "-MExtUtils::MY" -e "MY->fixin(shift)" blib/script/prove > Manifying blib/man1/prove.1 > Manifying blib/man3/TAP::Parser::Result::Pragma.3 > Manifying blib/man3/TAP::Parser::Iterator::Array.3 > Manifying blib/man3/App::Prove::State::Result.3 > Manifying blib/man3/TAP::Base.3 > Manifying blib/man3/TAP::Formatter::Console::ParallelSession.3 > Manifying blib/man3/TAP::Parser::Result.3 > Manifying blib/man3/TAP::Formatter::Console::Session.3 > Manifying blib/man3/TAP::Parser::Scheduler::Job.3 > Manifying blib/man3/TAP::Parser::Result::YAML.3 > Manifying blib/man3/TAP::Parser.3 > Manifying blib/man3/TAP::Parser::IteratorFactory.3 > Manifying blib/man3/TAP::Parser::Iterator.3 > Manifying blib/man3/TAP::Formatter::Color.3 > Manifying blib/man3/TAP::Parser::Iterator::Process.3 > Manifying blib/man3/TAP::Parser::Grammar.3 > Manifying blib/man3/Test::HACKING.3 > Manifying blib/man3/Test::Harness.3 > Manifying blib/man3/TAP::Parser::Result::Bailout.3 > Manifying blib/man3/TAP::Parser::Utils.3 > Manifying blib/man3/TAP::Parser::ResultFactory.3 > Manifying blib/man3/TAP::Parser::Multiplexer.3 > Manifying blib/man3/TAP::Object.3 > Manifying blib/man3/TAP::Parser::YAMLish::Writer.3 > Manifying blib/man3/TAP::Parser::Result::Version.3 > Manifying blib/man3/TAP::Parser::Result::Unknown.3 > Manifying blib/man3/TAP::Parser::YAMLish::Reader.3 > Manifying blib/man3/TAP::Parser::Scheduler.3 > Manifying blib/man3/TAP::Parser::Result::Plan.3 > Manifying blib/man3/TAP::Parser::Source::Perl.3 > Manifying blib/man3/TAP::Parser::Result::Test.3 > Manifying blib/man3/App::Prove::State::Result::Test.3 > Manifying blib/man3/TAP::Formatter::Console.3 > Manifying blib/man3/TAP::Parser::Source.3 > Manifying blib/man3/TAP::Parser::Result::Comment.3 > Manifying blib/man3/TAP::Parser::Iterator::Stream.3 > Manifying blib/man3/App::Prove::State.3 > Manifying blib/man3/App::Prove.3 > Manifying blib/man3/TAP::Harness.3 > Manifying blib/man3/TAP::Parser::Aggregator.3 > Manifying blib/man3/TAP::Parser::Scheduler::Spinner.3 > ================================================================ > ======================================== > make: don't know how to make regression-test(continuing) > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > skipping perl-5.8.9, already added > ===> Installing for p5-Test-Harness-3.14 > ===> p5-Test-Harness-3.14 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Generating temporary packing list > ===> Checking if devel/p5-Test-Harness already installed > Installing /usr/local/lib/perl5/site_perl/5.8.9/Test/HACKING.pod > Installing /usr/local/lib/perl5/site_perl/5.8.9/Test/Harness.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Base.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Object.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Harness.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Result.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/IteratorFactory.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Iterator.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Grammar.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/ResultFactory.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Utils.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Multiplexer.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Scheduler.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Source.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Aggregator.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Result/Pragma.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Result/YAML.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Result/Bailout.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Result/Version.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Result/Unknown.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Result/Plan.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Result/Test.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Result/Comment.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Iterator/Array.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Iterator/Process.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Iterator/Stream.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Scheduler/Job.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Scheduler/Spinner.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/YAMLish/Writer.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/YAMLish/Reader.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Parser/Source/Perl.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Formatter/Color.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Formatter/Console.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Formatter/Console/ParallelSession.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/TAP/Formatter/Console/Session.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/App/Prove.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/App/Prove/State.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/App/Prove/State/Result.pm > Installing /usr/local/lib/perl5/site_perl/5.8.9/App/Prove/State/Result/Test.pm > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Result::Pragma.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Iterator::Array.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/App::Prove::State::Result.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Base.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Formatter::Console::ParallelSession.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Result.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Formatter::Console::Session.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Scheduler::Job.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Result::YAML.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::IteratorFactory.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Iterator.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Formatter::Color.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Iterator::Process.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Grammar.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/Test::HACKING.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/Test::Harness.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Result::Bailout.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Utils.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::ResultFactory.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Multiplexer.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Object.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::YAMLish::Writer.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Result::Version.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Result::Unknown.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::YAMLish::Reader.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Scheduler.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Result::Plan.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Source::Perl.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Result::Test.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/App::Prove::State::Result::Test.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Formatter::Console.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Source.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Result::Comment.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Iterator::Stream.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/App::Prove::State.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/App::Prove.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Harness.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Aggregator.3 > Installing /usr/local/lib/perl5/5.8.9/man/man3/TAP::Parser::Scheduler::Spinner.3 > Installing /usr/local/bin/prove > Writing /usr/local/lib/perl5/site_perl/5.8.9/mach/auto/Test/Harness/.packlist > ===> Compressing manual pages for p5-Test-Harness-3.14 > ===> Registering installation for p5-Test-Harness-3.14 > ================================================================ > ======================================== > ===> Building package for p5-Test-Harness-3.14 > Creating package /tmp/packages/All/p5-Test-Harness-3.14.tbz > Registering depends: perl-5.8.9. > Creating bzip'd tar ball in '/tmp/packages/All/p5-Test-Harness-3.14.tbz' > Deleting p5-Test-Harness-3.14 > ================================================================ > > === Checking filesystem state > list of filesystem changes from before and after port installation and deinstallation > usr/local/bin/prove changed > permissions expected 0755 found 0555 > ================================================================ > build of /usr/ports/devel/p5-Test-Harness ended at Wed Jan 14 12:34:13 UTC 2009 -- Pav Lucistnik Orfax's hip flask contained Old Janx Spirit, a mixture of potions of stupidity, paralysis, naivery, ruination, lose memories, confusion, and slime mold juice, with a twist of lemon. - from a post on Angband Community Forum -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090114/0fbdb2fe/attachment.pgp From pav at FreeBSD.org Wed Jan 14 13:19:26 2009 From: pav at FreeBSD.org (Pav Lucistnik) Date: Wed Jan 14 13:19:32 2009 Subject: [Fwd: p5-VCP-0.9_2 failed on amd64 6] Message-ID: <1231967955.61866.16.camel@hood.oook.cz> -------- P?eposlan? zpr?va -------- > Od: User Ports-amd64 > Komu: cvs@oook.cz > P?edm?t: p5-VCP-0.9_2 failed on amd64 6 > Datum: Wed, 14 Jan 2009 19:19:56 GMT > > You can also find this build log at > > http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.6.20090114102347/p5-VCP-0.9_2.log > > building p5-VCP-0.9_2 on gohan12.freebsd.org > in directory /x/pkgbuild/6/20090114102347/chroot/1028 > building for: 6.4-STABLE amd64 > maintained by: hrs@FreeBSD.org > port directory: /usr/ports/devel/p5-VCP > Makefile ident: $FreeBSD: ports/devel/p5-VCP/Makefile,v 1.9 2007/09/10 00:32:10 linimon Exp $ > build started at Wed Jan 14 19:19:09 UTC 2009 > FETCH_DEPENDS= > PATCH_DEPENDS=perl-5.8.9.tbz > EXTRACT_DEPENDS=perl-5.8.9.tbz > BUILD_DEPENDS=expat-2.0.1.tbz p5-Algorithm-Diff-1.1902.tbz p5-BFD-0.31.tbz p5-Digest-MD5-2.38.tbz p5-Font-AFM-1.20.tbz p5-HTML-Format-2.04.tbz p5-HTML-Parser-3.59.tbz p5-HTML-Tagset-3.20.tbz p5-HTML-Tree-3.23.tbz p5-IPC-Run3-0.042.tbz p5-MIME-Base64-3.07.tbz p5-Pod-Parser-1.35_2.tbz p5-PodToHTML-0.08.tbz p5-Regexp-Shellish-0.93.tbz p5-Scalar-List-Utils-1.19,1.tbz p5-Text-Aligner-0.03.tbz p5-Text-Diff-0.35.tbz p5-Text-Table-1.114.tbz p5-Time-HiRes-1.9719,1.tbz p5-URI-1.37.tbz p5-XML-AutoWriter-0.39.tbz p5-XML-Parser-2.36.tbz perl-5.8.9.tbz > RUN_DEPENDS=expat-2.0.1.tbz p5-Algorithm-Diff-1.1902.tbz p5-BFD-0.31.tbz p5-Digest-MD5-2.38.tbz p5-Font-AFM-1.20.tbz p5-HTML-Format-2.04.tbz p5-HTML-Parser-3.59.tbz p5-HTML-Tagset-3.20.tbz p5-HTML-Tree-3.23.tbz p5-IPC-Run3-0.042.tbz p5-MIME-Base64-3.07.tbz p5-Pod-Parser-1.35_2.tbz p5-PodToHTML-0.08.tbz p5-Regexp-Shellish-0.93.tbz p5-Scalar-List-Utils-1.19,1.tbz p5-Text-Aligner-0.03.tbz p5-Text-Diff-0.35.tbz p5-Text-Table-1.114.tbz p5-Time-HiRes-1.9719,1.tbz p5-URI-1.37.tbz p5-XML-AutoWriter-0.39.tbz p5-XML-Parser-2.36.tbz perl-5.8.9.tbz > prefixes: LOCALBASE=usr/local X11BASE=usr/local > add_pkg > ================================================================ > ======================================== > => VCP-0.9.tar.gz doesn't seem to exist in /tmp/distfiles/. > => Attempting to fetch from ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/. > VCP-0.9.tar.gz 294 kB 11 MBps > => MD5 Checksum OK for VCP-0.9.tar.gz. > => SHA256 Checksum OK for VCP-0.9.tar.gz. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Extracting for p5-VCP-0.9_2 > => MD5 Checksum OK for VCP-0.9.tar.gz. > => SHA256 Checksum OK for VCP-0.9.tar.gz. > ===> p5-VCP-0.9_2 depends on file: /usr/local/bin/perl5.8.9 - found > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Patching for p5-VCP-0.9_2 > ===> p5-VCP-0.9_2 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Applying FreeBSD patches for p5-VCP-0.9_2 > /usr/bin/find /work/a/ports/devel/p5-VCP/work/VCP-0.9 -name "*.orig" -a -exec /bin/rm -f {} \; > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg expat-2.0.1.tbz p5-Algorithm-Diff-1.1902.tbz p5-BFD-0.31.tbz p5-Digest-MD5-2.38.tbz p5-Font-AFM-1.20.tbz p5-HTML-Format-2.04.tbz p5-HTML-Parser-3.59.tbz p5-HTML-Tagset-3.20.tbz p5-HTML-Tree-3.23.tbz p5-IPC-Run3-0.042.tbz p5-MIME-Base64-3.07.tbz p5-Pod-Parser-1.35_2.tbz p5-PodToHTML-0.08.tbz p5-Regexp-Shellish-0.93.tbz p5-Scalar-List-Utils-1.19,1.tbz p5-Text-Aligner-0.03.tbz p5-Text-Diff-0.35.tbz p5-Text-Table-1.114.tbz p5-Time-HiRes-1.9719,1.tbz p5-URI-1.37.tbz p5-XML-AutoWriter-0.39.tbz p5-XML-Parser-2.36.tbz perl-5.8.9.tbz > adding dependencies > pkg_add expat-2.0.1.tbz > pkg_add p5-Algorithm-Diff-1.1902.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > pkg_add p5-BFD-0.31.tbz > pkg_add p5-Digest-MD5-2.38.tbz > pkg_add p5-Font-AFM-1.20.tbz > pkg_add p5-HTML-Format-2.04.tbz > pkg_add p5-HTML-Parser-3.59.tbz > skipping p5-HTML-Parser-3.59, already added > pkg_add p5-HTML-Tagset-3.20.tbz > skipping p5-HTML-Tagset-3.20, already added > pkg_add p5-HTML-Tree-3.23.tbz > skipping p5-HTML-Tree-3.23, already added > pkg_add p5-IPC-Run3-0.042.tbz > pkg_add p5-MIME-Base64-3.07.tbz > pkg_add p5-Pod-Parser-1.35_2.tbz > pkg_add p5-PodToHTML-0.08.tbz > pkg_add p5-Regexp-Shellish-0.93.tbz > pkg_add p5-Scalar-List-Utils-1.19,1.tbz > pkg_add p5-Text-Aligner-0.03.tbz > pkg_add p5-Text-Diff-0.35.tbz > pkg_add p5-Text-Table-1.114.tbz > pkg_add p5-Time-HiRes-1.9719,1.tbz > skipping p5-Time-HiRes-1.9719,1, already added > pkg_add p5-URI-1.37.tbz > skipping p5-URI-1.37, already added > pkg_add p5-XML-AutoWriter-0.39.tbz > pkg_add p5-XML-Parser-2.36.tbz > pkg_add perl-5.8.9.tbz > skipping perl-5.8.9, already added > ===> p5-VCP-0.9_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/mach/XML/Parser.pm - found > ===> p5-VCP-0.9_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/XML/ValidWriter.pm - found > ===> p5-VCP-0.9_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/mach/MIME/Base64.pm - found > ===> p5-VCP-0.9_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/Text/Diff.pm - found > ===> p5-VCP-0.9_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/IPC/Run3.pm - found > ===> p5-VCP-0.9_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/Pod/Links.pm - found > ===> p5-VCP-0.9_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/mach/Digest/MD5.pm - found > ===> p5-VCP-0.9_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/Regexp/Shellish.pm - found > ===> p5-VCP-0.9_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/BFD.pm - found > ===> p5-VCP-0.9_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/Text/Table.pm - found > ===> p5-VCP-0.9_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/mach/List/Util.pm - found > ===> p5-VCP-0.9_2 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Configuring for p5-VCP-0.9_2 > Checking if your kit is complete... > Looks good > Writing Makefile for VCP > ===> Building for p5-VCP-0.9_2 > /usr/local/bin/perl5.8.9 bin/genhelp bin/vcp lib/VCP/Source.pm lib/VCP/Filter.pm lib/VCP/DefaultFilters.pm lib/VCP/Dest.pm lib/VCP/Filter/labelmap.pm lib/VCP/Filter/map.pm lib/VCP/Filter/dumpdata.pm lib/VCP/Filter/sort.pm lib/VCP/Filter/csv_trace.pm lib/VCP/Filter/addlabels.pm lib/VCP/Filter/changesets.pm lib/VCP/Filter/stringedit.pm lib/VCP/Filter/identity.pm lib/VCP/Dest/cvs.pm lib/VCP/Dest/revml.pm lib/VCP/Dest/topo_table.pm lib/VCP/Dest/summary.pm lib/VCP/Dest/p4.pm lib/VCP/Dest/csv.pm lib/VCP/Dest/branch_diagram.pm lib/VCP/Dest/data_dump.pm lib/VCP/Dest/texttable.pm lib/VCP/Dest/vss.pm lib/VCP/Dest/null.pm lib/VCP/Dest/metadb.pm lib/VCP/Source/revml.pm lib/VCP/Source/null.pm lib/VCP/Source/metadb.pm lib/VCP/Source/p4.pm lib/VCP/Source/vss.pm lib/VCP/Source/cvs.pm > writing lib/VCP/Help.pm > lib/VCP/DefaultFilters.pm:102: Unmatched =back > lib/VCP/Filter/dumpdata.pm:48: Unmatched =back > lib/VCP/Filter/csv_trace.pm:141: Unmatched =back > lib/VCP/Dest/revml.pm:41: Unmatched =back > lib/VCP/Dest/summary.pm:49: Unmatched =back > lib/VCP/Dest/csv.pm:143: Unmatched =back > lib/VCP/Dest/data_dump.pm:44: Unmatched =back > lib/VCP/Dest/texttable.pm:158: Unmatched =back > cp lib/VCP/Dest/branch_diagram.pm blib/lib/VCP/Dest/branch_diagram.pm > cp lib/VCP/UI.pm blib/lib/VCP/UI.pm > cp lib/VCP/Dest/data_dump.pm blib/lib/VCP/Dest/data_dump.pm > cp lib/VCP/FilesDB.pm blib/lib/VCP/FilesDB.pm > cp lib/VCP/Filter/labelmap.pm blib/lib/VCP/Filter/labelmap.pm > cp lib/VCP/Filter/map.pm blib/lib/VCP/Filter/map.pm > cp lib/VCP/PodDESCRIPTIONParser.pm blib/lib/VCP/PodDESCRIPTIONParser.pm > cp lib/VCP/Dest/texttable.pm blib/lib/VCP/Dest/texttable.pm > cp lib/VCP/Source/metadb.pm blib/lib/VCP/Source/metadb.pm > cp lib/VCP/Utils/p4.pm blib/lib/VCP/Utils/p4.pm > cp lib/VCP/Dest/vss.pm blib/lib/VCP/Dest/vss.pm > cp lib/VCP/DB_File/sdbm.pm blib/lib/VCP/DB_File/sdbm.pm > cp lib/VCP/Dest/null.pm blib/lib/VCP/Dest/null.pm > cp lib/VCP/RevMapDB.pm blib/lib/VCP/RevMapDB.pm > cp lib/VCP/Process.pod blib/lib/VCP/Process.pod > cp lib/VCP/Utils.pm blib/lib/VCP/Utils.pm > cp lib/RevML/Doctype.pm blib/lib/RevML/Doctype.pm > cp lib/VCP/Debug.pm blib/lib/VCP/Debug.pm > cp lib/VCP/Source/p4.pm blib/lib/VCP/Source/p4.pm > cp lib/VCP/Filter/dumpdata.pm blib/lib/VCP/Filter/dumpdata.pm > cp lib/VCP/Plugin.pm blib/lib/VCP/Plugin.pm > cp lib/VCP/DiffFormat.pm blib/lib/VCP/DiffFormat.pm > cp lib/VCP/ConfigFileUtils.pm blib/lib/VCP/ConfigFileUtils.pm > cp lib/VCP/DB.pm blib/lib/VCP/DB.pm > cp lib/VCP/Dest/cvs.pm blib/lib/VCP/Dest/cvs.pm > cp lib/VCP/Filter/addlabels.pm blib/lib/VCP/Filter/addlabels.pm > cp lib/VCP/HeadRevsDB.pm blib/lib/VCP/HeadRevsDB.pm > cp lib/VCP/Utils/cvs.pm blib/lib/VCP/Utils/cvs.pm > cp lib/VCP/Source.pm blib/lib/VCP/Source.pm > cp lib/VCP/Utils/metadb.pm blib/lib/VCP/Utils/metadb.pm > cp lib/VCP/Newlines.pod blib/lib/VCP/Newlines.pod > cp lib/VCP/RefCountedFile.pm blib/lib/VCP/RefCountedFile.pm > cp lib/VCP/Help.pm blib/lib/VCP/Help.pm > cp lib/VCP/TestUtils.pm blib/lib/VCP/TestUtils.pm > cp lib/VCP/Rev.pm blib/lib/VCP/Rev.pm > cp lib/VCP/Dest/revml.pm blib/lib/VCP/Dest/revml.pm > cp lib/VCP/Filter/sort.pm blib/lib/VCP/Filter/sort.pm > cp lib/VCP/Filter/changesets.pm blib/lib/VCP/Filter/changesets.pm > cp lib/VCP/Dest/topo_table.pm blib/lib/VCP/Dest/topo_table.pm > cp lib/VCP/Logger.pm blib/lib/VCP/Logger.pm > cp lib/VCP/Branches.pod blib/lib/VCP/Branches.pod > cp lib/VCP/Patch.pm blib/lib/VCP/Patch.pm > cp lib/VCP/Filter/stringedit.pm blib/lib/VCP/Filter/stringedit.pm > cp lib/VCP/PodOPTIONSParser.pm blib/lib/VCP/PodOPTIONSParser.pm > cp lib/VCP/Filter/csv_trace.pm blib/lib/VCP/Filter/csv_trace.pm > cp lib/RevML/Writer.pm blib/lib/RevML/Writer.pm > cp lib/VCP/Filter.pm blib/lib/VCP/Filter.pm > cp lib/VCP/DefaultFilters.pm blib/lib/VCP/DefaultFilters.pm > cp lib/VCP/Dest/summary.pm blib/lib/VCP/Dest/summary.pm > cp lib/RevML/Doctype/v0_35.pm blib/lib/RevML/Doctype/v0_35.pm > cp lib/VCP/Dest/metadb.pm blib/lib/VCP/Dest/metadb.pm > cp lib/VCP/DB_File/big_records.pm blib/lib/VCP/DB_File/big_records.pm > cp lib/VCP/Driver.pm blib/lib/VCP/Driver.pm > cp lib/VCP/Utils/revml.pm blib/lib/VCP/Utils/revml.pm > cp lib/VCP/Dest/p4.pm blib/lib/VCP/Dest/p4.pm > cp lib/VCP/UIMachines.pm blib/lib/VCP/UIMachines.pm > cp lib/VCP/Source/vss.pm blib/lib/VCP/Source/vss.pm > cp lib/VCP/MainBranchIdDB.pm blib/lib/VCP/MainBranchIdDB.pm > cp lib/VCP/Maintenance.pod blib/lib/VCP/Maintenance.pod > cp lib/VCP/Dest/csv.pm blib/lib/VCP/Dest/csv.pm > cp lib/VCP/Source/revml.pm blib/lib/VCP/Source/revml.pm > cp lib/VCP.pm blib/lib/VCP.pm > cp lib/VCP/Source/null.pm blib/lib/VCP/Source/null.pm > cp lib/VCP/UI/Text.pm blib/lib/VCP/UI/Text.pm > cp lib/VCP/Utils/vss.pm blib/lib/VCP/Utils/vss.pm > cp lib/VCP/Filter/identity.pm blib/lib/VCP/Filter/identity.pm > cp lib/VCP/Source/cvs.pm blib/lib/VCP/Source/cvs.pm > cp lib/VCP/License.pod blib/lib/VCP/License.pod > cp lib/VCP/DB_File.pm blib/lib/VCP/DB_File.pm > cp lib/VCP/Revs.pm blib/lib/VCP/Revs.pm > cp lib/VCP/Dest.pm blib/lib/VCP/Dest.pm > cp bin/vcp blib/script/vcp > /usr/local/bin/perl5.8.9 "-MExtUtils::MY" -e "MY->fixin(shift)" blib/script/vcp > /usr/local/bin/perl5.8.9 "-Iblib/arch" "-Iblib/lib" "-I/usr/local/lib/perl5/5.8.9/mach" "-I/usr/local/lib/perl5/5.8.9" bin/gentrevml --cvs --batch 0 --no-big-files > t/test-cvs-in-0-no-big-files.revml > NAME > gentrevml - Generate a .revml file used by the t/ scripts > > SYNOPSIS > perl bin/gentrevml --(revml|p4|cvs|vss) [--bootstrap] [--no-a-big-file] [--batch=1] > > DESCRIPTION > The test suite uses a basic RevML file to check to see vcp it can copy > in to and out of a repository correctly. This is done for each > repository class. > > Note that going through a repository may lose some information, so the > test suite can't always compare the input RevML to the output RevML. > > Only the revml->revml case is known to be idempotent. > > I chose to do this over using some base repository because not every > user is going to happen to have that repository, and (2) not every > repository will pass through all information correctly. > > COPYRIGHT > Copyright 2000, 2003 Perforce Software, Inc. All Rights Reserved. > > This will be licensed under a suitable license at a future date. Until > then, you may only use this for evaluation purposes. Besides which, it's > in an early alpha state, so you shouldn't depend on it anyway. > > AUTHOR > Barrie Slaymaker > > *** Error code 2 > > Stop in /work/a/ports/devel/p5-VCP/work/VCP-0.9. > *** Error code 1 > > Stop in /a/ports/devel/p5-VCP. > ================================================================ > build of /usr/ports/devel/p5-VCP ended at Wed Jan 14 19:19:55 UTC 2009 -- Pav Lucistnik A mouse is a device used to point at the xterm you want to type in. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090114/156d7084/attachment.pgp From pav at FreeBSD.org Wed Jan 14 14:26:57 2009 From: pav at FreeBSD.org (Pav Lucistnik) Date: Wed Jan 14 14:27:11 2009 Subject: [Fwd: eperl-2.2.14_1 failed on amd64 6] Message-ID: <1231972009.61866.25.camel@hood.oook.cz> -------- P?eposlan? zpr?va -------- > Od: User Ports-amd64 > Komu: cvs@oook.cz > P?edm?t: eperl-2.2.14_1 failed on amd64 6 > Datum: Wed, 14 Jan 2009 22:19:20 GMT > > You can also find this build log at > > http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.6.20090114102347/eperl-2.2.14_1.log > > building eperl-2.2.14_1 on hammer1.isc.gumbysoft.com > in directory /usr2/pkgbuild/6/20090114102347/chroot/784 > building for: 6.4-STABLE amd64 > maintained by: ports@FreeBSD.org > port directory: /usr/ports/lang/eperl > Makefile ident: $FreeBSD: ports/lang/eperl/Makefile,v 1.46 2009/01/08 17:28:13 erwin Exp $ > build started at Wed Jan 14 22:18:08 UTC 2009 > FETCH_DEPENDS= > PATCH_DEPENDS=perl-5.8.9.tbz > EXTRACT_DEPENDS=perl-5.8.9.tbz > BUILD_DEPENDS=perl-5.8.9.tbz > RUN_DEPENDS=perl-5.8.9.tbz > prefixes: LOCALBASE=usr/local X11BASE=usr/local > add_pkg > ================================================================ > ======================================== > => eperl-2.2.14.tar.gz doesn't seem to exist in /tmp/distfiles/. > => Attempting to fetch from ftp://freebsd.isc.org/pub/FreeBSD/ports/distfiles/. > eperl-2.2.14.tar.gz 194 kB 3942 kBps > => MD5 Checksum OK for eperl-2.2.14.tar.gz. > => SHA256 Checksum OK for eperl-2.2.14.tar.gz. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Extracting for eperl-2.2.14_1 > => MD5 Checksum OK for eperl-2.2.14.tar.gz. > => SHA256 Checksum OK for eperl-2.2.14.tar.gz. > ===> eperl-2.2.14_1 depends on file: /usr/local/bin/perl5.8.9 - found > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Patching for eperl-2.2.14_1 > ===> eperl-2.2.14_1 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Applying FreeBSD patches for eperl-2.2.14_1 > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> eperl-2.2.14_1 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Configuring for eperl-2.2.14_1 > Configuring for ePerl 2.2.14 (02-08-1998) > creating cache ./config.cache > > __ CHECK: Configuration of Perl Language __ > checking for Perl language... /usr/local/bin/perl5.8.9 v5.8.9 > checking for Perl knowledge of system... freebsd-6.4-stable > checking for Perl standard compiler... cc (OVERWRITTEN) > checking for Perl standard optimization flags... -O2 -fno-strict-aliasing -pipe > checking for Perl standard compilation flags... -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include > checking for Perl standard link flags... -Wl,-E -L/usr/local/lib > checking for Perl library files... -lm -lcrypt -lutil > checking for Perl architecture directory... /usr/local/lib/perl5/5.8.9/mach > checking for Perl dynamic loading support... yes > checking for Perl dynamic loading compilation flags... -DPIC -fPIC > checking for Perl dynamic loading link flags... -Wl,-R/usr/local/lib/perl5/5.8.9/mach/CORE > > __ CHECK: System Build Environment __ > checking for build user... root@freebsd.org > checking for build time... 14-Jan-2009 > checking for gcc... cc > checking whether the C compiler (cc -O2 -fno-strict-aliasing -pipe ) works... yes > checking whether the C compiler (cc -O2 -fno-strict-aliasing -pipe ) is a cross-compiler... no > checking whether we are using GNU C... yes > checking whether cc accepts -g... yes > checking for ranlib... ranlib > checking for ar... ar > checking for size... size > checking for compilation debug mode... disabled > checking whether make sets ${MAKE}... yes > checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel > > __ CHECK: Characteristic of System Headers and Libraries __ > checking for working const... yes > checking how to run the C preprocessor... cc -E > checking for ANSI C header files... yes > checking for stdio.h... yes > checking for stdarg.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for ctype.h... yes > checking for unistd.h... yes > checking for time.h... yes > checking for signal.h... yes > checking for pwd.h... yes > checking for grp.h... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for sys/param.h... yes > checking for sys/socket.h... yes > checking for netinet/in.h... yes > checking for netdb.h... yes > checking for bool... no > checking for memmove... yes > checking for seteuid... yes > checking for setegid... yes > checking for strdup... yes > > __ RESULT: Sourcefile Substitution __ > updating cache ./config.cache > creating ./config.status > creating Makefile > creating t/Makefile > creating config_sc.h > creating config_ac.h > > Now please type 'make' to compile. Good luck. > > ===> Building for eperl-2.2.14_1 > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_main.c > /usr/local/bin/perl5.8.9 eperl_perl5_sm.pl >eperl_perl5_sm.h > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_perl5.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_parse.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_pp.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_sys.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_http.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_getopt.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_debug.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_config.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_version.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_readme.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_license.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_logo.c > cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_powered.c > cc -Wl,-R/usr/local/lib/perl5/5.8.9/mach/CORE -Wl,-E -L/usr/local/lib -L/usr/local/lib/perl5/5.8.9/mach/CORE -o eperl eperl_main.o eperl_perl5.o eperl_parse.o eperl_pp.o eperl_sys.o eperl_http.o eperl_getopt.o eperl_debug.o eperl_config.o eperl_version.o eperl_readme.o eperl_license.o eperl_logo.o eperl_powered.o /usr/local/lib/perl5/5.8.9/mach/auto/DynaLoader/DynaLoader.a -lperl -lm -lcrypt -lutil > cc: /usr/local/lib/perl5/5.8.9/mach/auto/DynaLoader/DynaLoader.a: No such file or directory > *** Error code 1 > > Stop in /work/a/ports/lang/eperl/work/eperl-2.2.14. > *** Error code 1 > > Stop in /a/ports/lang/eperl. > ================================================================ > build of /usr/ports/lang/eperl ended at Wed Jan 14 22:19:19 UTC 2009 -- Pav Lucistnik /usr/src scares me. I'm just not man enough to commit there. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090114/be177e3d/attachment.pgp From leeym at FreeBSD.org Wed Jan 14 21:27:45 2009 From: leeym at FreeBSD.org (leeym@FreeBSD.org) Date: Wed Jan 14 21:27:52 2009 Subject: ports/130558: [PATCH] net/p5-Net-Amazon-S3: Add missing dependencies Message-ID: <200901150527.n0F5RiRY016771@freefall.freebsd.org> Synopsis: [PATCH] net/p5-Net-Amazon-S3: Add missing dependencies State-Changed-From-To: open->closed State-Changed-By: leeym State-Changed-When: Thu Jan 15 05:27:37 UTC 2009 State-Changed-Why: Committed, thanks. http://www.freebsd.org/cgi/query-pr.cgi?pr=130558 From gslin at gslin.org Thu Jan 15 11:01:13 2009 From: gslin at gslin.org (Gea-Suan Lin) Date: Thu Jan 15 11:01:27 2009 Subject: [PATCH] net/p5-Net-Amazon-S3: Add missing dependencies Message-ID: <200901140619.n0E6JJ9e029640@staff.pixnet.tw> >Submitter-Id: current-users >Originator: Gea-Suan Lin >Organization: >Confidential: no >Synopsis: [PATCH] net/p5-Net-Amazon-S3: Add missing dependencies >Severity: non-critical >Priority: low >Category: ports >Class: change-request >Release: FreeBSD 7.0-STABLE amd64 >Environment: System: FreeBSD staff.pixnet.tw 7.0-STABLE FreeBSD 7.0-STABLE #1: Wed Jul 16 13:00:27 CST 2008 >Description: - Add missing dependencies. - Bump PORTREVISION. Port maintainer (perl@FreeBSD.org) is cc'd. Generated with FreeBSD Port Tools 0.77 >How-To-Repeat: >Fix: --- p5-Net-Amazon-S3-0.48_1.patch begins here --- diff -ruN --exclude=CVS /usr/ports/net/p5-Net-Amazon-S3/Makefile /usr/home/admin/gslin/work/ports/p5-Net-Amazon-S3/Makefile --- /usr/ports/net/p5-Net-Amazon-S3/Makefile 2008-12-07 01:38:49.000000000 +0800 +++ /usr/home/admin/gslin/work/ports/p5-Net-Amazon-S3/Makefile 2009-01-14 14:18:05.000000000 +0800 @@ -7,6 +7,7 @@ PORTNAME= Net-Amazon-S3 PORTVERSION= 0.48 +PORTREVISION= 1 CATEGORIES= net perl5 MASTER_SITES= CPAN PKGNAMEPREFIX= p5- @@ -15,8 +16,13 @@ COMMENT= Use the Amazon S3 - Simple Storage Service RUN_DEPENDS= p5-Class-Accessor>=0:${PORTSDIR}/devel/p5-Class-Accessor \ + p5-Data-Stream-Bulk>=0:${PORTSDIR}/devel/p5-Data-Stream-Bulk \ + p5-DateTime-Format-ISO8601>=0:${PORTSDIR}/devel/p5-DateTime-Format-ISO8601 \ p5-Digest-HMAC>=0:${PORTSDIR}/security/p5-Digest-HMAC \ p5-LWP-UserAgent-Determined>=0:${PORTSDIR}/www/p5-LWP-UserAgent-Determined \ + p5-Moose>=0:${PORTSDIR}/devel/p5-Moose \ + p5-MooseX-StrictConstructor>=0:${PORTSDIR}/devel/p5-MooseX-StrictConstructor \ + p5-Regexp-Common>=0:${PORTSDIR}/textproc/p5-Regexp-Common \ p5-URI>=0:${PORTSDIR}/net/p5-URI \ p5-XML-LibXML>=0:${PORTSDIR}/textproc/p5-XML-LibXML \ p5-libwww>=0:${PORTSDIR}/www/p5-libwww --- p5-Net-Amazon-S3-0.48_1.patch ends here --- From pav at FreeBSD.org Thu Jan 15 14:42:12 2009 From: pav at FreeBSD.org (Pav Lucistnik) Date: Thu Jan 15 14:42:20 2009 Subject: [Fwd: perlftlib-1.2 failed on amd64 6] Message-ID: <1232059326.42745.13.camel@hood.oook.cz> -------- P?eposlan? zpr?va -------- > Od: User Ports-amd64 > Komu: cvs@oook.cz > P?edm?t: perlftlib-1.2 failed on amd64 6 > Datum: Thu, 15 Jan 2009 01:08:08 GMT > > You can also find this build log at > > http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.6.20090114102347/perlftlib-1.2.log > > building perlftlib-1.2 on gohan12.freebsd.org > in directory /x/pkgbuild/6/20090114102347/chroot/1443 > building for: 6.4-STABLE amd64 > maintained by: ports@FreeBSD.org > port directory: /usr/ports/print/perlftlib > Makefile ident: $FreeBSD: ports/print/perlftlib/Makefile,v 1.24 2008/07/30 03:15:15 vs Exp $ > build started at Thu Jan 15 01:06:48 UTC 2009 > FETCH_DEPENDS= > PATCH_DEPENDS=perl-5.8.9.tbz > EXTRACT_DEPENDS=perl-5.8.9.tbz > BUILD_DEPENDS=freetype-1.3.1_4.tbz perl-5.8.9.tbz > RUN_DEPENDS=freetype-1.3.1_4.tbz ja-jcode.pl-2.13.tbz perl-5.8.9.tbz > prefixes: LOCALBASE=usr/local X11BASE=usr/local > add_pkg > ================================================================ > ======================================== > => perlftlib-1.2.tar.gz doesn't seem to exist in /tmp/distfiles/. > => Attempting to fetch from ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/. > perlftlib-1.2.tar.gz 24 kB 667 kBps > => MD5 Checksum OK for perlftlib-1.2.tar.gz. > => SHA256 Checksum OK for perlftlib-1.2.tar.gz. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Extracting for perlftlib-1.2 > => MD5 Checksum OK for perlftlib-1.2.tar.gz. > => SHA256 Checksum OK for perlftlib-1.2.tar.gz. > ===> perlftlib-1.2 depends on file: /usr/local/bin/perl5.8.9 - found > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Patching for perlftlib-1.2 > ===> perlftlib-1.2 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Applying FreeBSD patches for perlftlib-1.2 > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg freetype-1.3.1_4.tbz perl-5.8.9.tbz > adding dependencies > pkg_add freetype-1.3.1_4.tbz > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> perlftlib-1.2 depends on file: /usr/local/bin/perl5.8.9 - found > ===> perlftlib-1.2 depends on shared library: ttf.4 - found > ===> Configuring for perlftlib-1.2 > ===> Building for perlftlib-1.2 > cd FreeType; /usr/local/bin/perl5.8.9 Makefile.PL > Checking if your kit is complete... > Looks good > Writing Makefile for FreeType > cd FreeType; make > cp FreeType.pm blib/lib/FreeType.pm > AutoSplitting blib/lib/FreeType.pm (blib/lib/auto/FreeType) > /usr/local/bin/perl5.8.9 /usr/local/lib/perl5/5.8.9/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.8.9/ExtUtils/typemap -typemap typemap FreeType.xs > FreeType.xsc && mv FreeType.xsc FreeType.c > Please specify prototyping behavior for FreeType.xs (see perlxs manual) > cc -c -I/usr/local/include/freetype1/freetype -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -O2 -fno-strict-aliasing -pipe -DVERSION=\"1.2\" -DXS_VERSION=\"1.2\" -DPIC -fPIC "-I/usr/local/lib/perl5/5.8.9/mach/CORE" FreeType.c > FreeType.c: In function `XS_FreeType_TT_Get_Glyph_Bitmap': > FreeType.c:1250: warning: static declaration of 'XS_FreeType_TT_Get_Glyph_Pixmap' follows non-static declaration > FreeType.c:1248: warning: previous declaration of 'XS_FreeType_TT_Get_Glyph_Pixmap' was here > FreeType.c: In function `XS_FreeType_TT_Get_Glyph_Pixmap': > FreeType.c:1294: warning: static declaration of 'XS_FreeType_TT_New_Outline' follows non-static declaration > FreeType.c:1292: warning: previous declaration of 'XS_FreeType_TT_New_Outline' was here > FreeType.c:1322: warning: static declaration of 'XS_FreeType_TT_Done_Outline' follows non-static declaration > FreeType.c:1320: warning: previous declaration of 'XS_FreeType_TT_Done_Outline' was here > FreeType.c:1345: warning: static declaration of 'XS_FreeType_TT_Copy_Outline' follows non-static declaration > FreeType.c:1343: warning: previous declaration of 'XS_FreeType_TT_Copy_Outline' was here > FreeType.c:1379: warning: static declaration of 'XS_FreeType_TT_Get_Outline_Bitmap' follows non-static declaration > FreeType.c:1377: warning: previous declaration of 'XS_FreeType_TT_Get_Outline_Bitmap' was here > FreeType.c: In function `XS_FreeType_TT_Get_Outline_Bitmap': > FreeType.c:1429: warning: static declaration of 'XS_FreeType_TT_Get_Outline_Pixmap' follows non-static declaration > FreeType.c:1427: warning: previous declaration of 'XS_FreeType_TT_Get_Outline_Pixmap' was here > FreeType.c: In function `XS_FreeType_TT_Get_Outline_Pixmap': > FreeType.c:1479: warning: static declaration of 'XS_FreeType_TT_Get_Outline_BBox' follows non-static declaration > FreeType.c:1477: warning: previous declaration of 'XS_FreeType_TT_Get_Outline_BBox' was here > FreeType.c:1512: warning: static declaration of 'XS_FreeType_TT_Transform_Outline' follows non-static declaration > FreeType.c:1510: warning: previous declaration of 'XS_FreeType_TT_Transform_Outline' was here > FreeType.c:1553: warning: static declaration of 'XS_FreeType_TT_Translate_Outline' follows non-static declaration > FreeType.c:1551: warning: previous declaration of 'XS_FreeType_TT_Translate_Outline' was here > FreeType.c:1585: warning: static declaration of 'XS_FreeType_TT_Transform_Vector' follows non-static declaration > FreeType.c:1583: warning: previous declaration of 'XS_FreeType_TT_Transform_Vector' was here > FreeType.c:1621: warning: static declaration of 'XS_FreeType_TT_Get_CharMap_Count' follows non-static declaration > FreeType.c:1619: warning: previous declaration of 'XS_FreeType_TT_Get_CharMap_Count' was here > FreeType.c:1654: warning: static declaration of 'XS_FreeType_TT_Get_CharMap_ID' follows non-static declaration > FreeType.c:1652: warning: previous declaration of 'XS_FreeType_TT_Get_CharMap_ID' was here > FreeType.c:1694: warning: static declaration of 'XS_FreeType_TT_Get_CharMap' follows non-static declaration > FreeType.c:1692: warning: previous declaration of 'XS_FreeType_TT_Get_CharMap' was here > FreeType.c:1732: warning: static declaration of 'XS_FreeType_TT_Char_Index' follows non-static declaration > FreeType.c:1730: warning: previous declaration of 'XS_FreeType_TT_Char_Index' was here > FreeType.c:1766: warning: static declaration of 'XS_FreeType_TT_Get_Name_Count' follows non-static declaration > FreeType.c:1764: warning: previous declaration of 'XS_FreeType_TT_Get_Name_Count' was here > FreeType.c:1799: warning: static declaration of 'XS_FreeType_TT_Get_Name_ID' follows non-static declaration > FreeType.c:1797: warning: previous declaration of 'XS_FreeType_TT_Get_Name_ID' was here > FreeType.c:1845: warning: static declaration of 'XS_FreeType_TT_Get_Name_String' follows non-static declaration > FreeType.c:1843: warning: previous declaration of 'XS_FreeType_TT_Get_Name_String' was here > FreeType.c:1892: warning: static declaration of 'boot_FreeType' follows non-static declaration > FreeType.c:1890: warning: previous declaration of 'boot_FreeType' was here > FreeType.c:1945: error: syntax error at end of input > *** Error code 1 > > Stop in /work/a/ports/print/perlftlib/work/perlftlib-1.2/FreeType. > *** Error code 1 > > Stop in /work/a/ports/print/perlftlib/work/perlftlib-1.2. > *** Error code 1 > > Stop in /a/ports/print/perlftlib. > ================================================================ > build of /usr/ports/print/perlftlib ended at Thu Jan 15 01:08:07 UTC 2009 -- Pav Lucistnik Alignment: Neutral Greedy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090115/3fc11647/attachment.pgp From pav at FreeBSD.org Thu Jan 15 14:50:11 2009 From: pav at FreeBSD.org (Pav Lucistnik) Date: Thu Jan 15 14:50:18 2009 Subject: [Fwd: p5-HTML-Embperl-1.3.6_2 failed on amd64 6] Message-ID: <1232059801.42745.15.camel@hood.oook.cz> -------- P?eposlan? zpr?va -------- > Od: User Ports-amd64 > Komu: cvs@oook.cz > P?edm?t: p5-HTML-Embperl-1.3.6_2 failed on amd64 6 > Datum: Thu, 15 Jan 2009 02:50:24 GMT > > You can also find this build log at > > http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.6.20090114102347/p5-HTML-Embperl-1.3.6_2.log > > building p5-HTML-Embperl-1.3.6_2 on hammer3.isc.gumbysoft.com > in directory /usr2/pkgbuild/6/20090114102347/chroot/522 > building for: 6.4-STABLE amd64 > maintained by: perl@FreeBSD.org > port directory: /usr/ports/www/p5-HTML-Embperl > Makefile ident: $FreeBSD: ports/www/p5-HTML-Embperl/Makefile,v 1.20 2008/04/17 14:29:56 araujo Exp $ > build started at Thu Jan 15 02:49:09 UTC 2009 > FETCH_DEPENDS= > PATCH_DEPENDS=perl-5.8.9.tbz > EXTRACT_DEPENDS=perl-5.8.9.tbz > BUILD_DEPENDS=apache-1.3.41.tbz expat-2.0.1.tbz mod_perl-1.30.tbz p5-Compress-Raw-Zlib-2.015.tbz p5-Compress-Zlib-2.015.tbz p5-HTML-Parser-3.59.tbz p5-HTML-Tagset-3.20.tbz p5-IO-Compress-Base-2.015.tbz p5-IO-Compress-Zlib-2.015.tbz p5-URI-1.37.tbz p5-libwww-5.822.tbz perl-5.8.9.tbz > RUN_DEPENDS=apache-1.3.41.tbz expat-2.0.1.tbz mod_perl-1.30.tbz p5-Apache-Session-1.87.tbz p5-Compress-Raw-Zlib-2.015.tbz p5-Compress-Zlib-2.015.tbz p5-HTML-Parser-3.59.tbz p5-HTML-Tagset-3.20.tbz p5-IO-Compress-Base-2.015.tbz p5-IO-Compress-Zlib-2.015.tbz p5-PathTools-3.2900.tbz p5-URI-1.37.tbz p5-libwww-5.822.tbz perl-5.8.9.tbz > prefixes: LOCALBASE=usr/local X11BASE=usr/local > add_pkg > ================================================================ > ======================================== > => HTML-Embperl-1.3.6.tar.gz doesn't seem to exist in /tmp/distfiles/. > => Attempting to fetch from ftp://freebsd.isc.org/pub/FreeBSD/ports/distfiles/. > HTML-Embperl-1.3.6.tar.gz 349 kB 7044 kBps > => MD5 Checksum OK for HTML-Embperl-1.3.6.tar.gz. > => SHA256 Checksum OK for HTML-Embperl-1.3.6.tar.gz. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Extracting for p5-HTML-Embperl-1.3.6_2 > => MD5 Checksum OK for HTML-Embperl-1.3.6.tar.gz. > => SHA256 Checksum OK for HTML-Embperl-1.3.6.tar.gz. > ===> p5-HTML-Embperl-1.3.6_2 depends on file: /usr/local/bin/perl5.8.9 - found > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg perl-5.8.9.tbz > adding dependencies > pkg_add perl-5.8.9.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Patching for p5-HTML-Embperl-1.3.6_2 > ===> p5-HTML-Embperl-1.3.6_2 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Applying FreeBSD patches for p5-HTML-Embperl-1.3.6_2 > Deleting perl-5.8.9 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ======================================== > add_pkg apache-1.3.41.tbz expat-2.0.1.tbz mod_perl-1.30.tbz p5-Compress-Raw-Zlib-2.015.tbz p5-Compress-Zlib-2.015.tbz p5-HTML-Parser-3.59.tbz p5-HTML-Tagset-3.20.tbz p5-IO-Compress-Base-2.015.tbz p5-IO-Compress-Zlib-2.015.tbz p5-URI-1.37.tbz p5-libwww-5.822.tbz perl-5.8.9.tbz > adding dependencies > pkg_add apache-1.3.41.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > > ===> COMPATIBILITY NOTE: > As of version 1.3.24, the RedirectMatch directive requires an > absolute URL target location per RFC 2068. Uses of RedirectMatch that > specify a relative URL will fail and must be corrected to function. > > ===> BE CAREFULL HOW TO BOOT on 1.3.29_4 or after: > To run apache www server from startup, add apache_enable="YES" > in your /etc/rc.conf. > > pkg_add expat-2.0.1.tbz > skipping expat-2.0.1, already added > pkg_add mod_perl-1.30.tbz > [activating module `perl' in /usr/local/etc/apache/httpd.conf] > cp /usr/local/etc/apache/httpd.conf.new /usr/local/etc/apache/httpd.conf > rm /usr/local/etc/apache/httpd.conf.new > pkg_add p5-Compress-Raw-Zlib-2.015.tbz > skipping p5-Compress-Raw-Zlib-2.015, already added > pkg_add p5-Compress-Zlib-2.015.tbz > skipping p5-Compress-Zlib-2.015, already added > pkg_add p5-HTML-Parser-3.59.tbz > skipping p5-HTML-Parser-3.59, already added > pkg_add p5-HTML-Tagset-3.20.tbz > skipping p5-HTML-Tagset-3.20, already added > pkg_add p5-IO-Compress-Base-2.015.tbz > skipping p5-IO-Compress-Base-2.015, already added > pkg_add p5-IO-Compress-Zlib-2.015.tbz > skipping p5-IO-Compress-Zlib-2.015, already added > pkg_add p5-URI-1.37.tbz > skipping p5-URI-1.37, already added > pkg_add p5-libwww-5.822.tbz > skipping p5-libwww-5.822, already added > pkg_add perl-5.8.9.tbz > skipping perl-5.8.9, already added > ===> p5-HTML-Embperl-1.3.6_2 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/mach/mod_perl.pm - found > ===> p5-HTML-Embperl-1.3.6_2 depends on file: /usr/local/bin/perl5.8.9 - found > ===> Configuring for p5-HTML-Embperl-1.3.6_2 > Will use /usr/local/include/apache for Apache Headers > Apache Version Server version: Apache/1.3.41 (Unix) > + Load dynamic module mod_actions.c > (/usr/local/libexec/apache/mod_actions.so) > + Load dynamic module mod_cgi.c > (/usr/local/libexec/apache/mod_cgi.so) > + Load dynamic module mod_alias.c > (/usr/local/libexec/apache/mod_alias.so) > + Load dynamic module mod_env.c > (/usr/local/libexec/apache/mod_env.so) > + Load dynamic module mod_perl.c > (/usr/local/libexec/apache/libperl.so) > + Load dynamic module mod_mime.c > (/usr/local/libexec/apache/mod_mime.so) > + Load dynamic module mod_dir.c > (/usr/local/libexec/apache/mod_dir.so) > + mod_perl was build with USE_DSO > Test start /usr/local/sbin/httpd > Test httpd will run as user nobody and group wheel > Test httpd will listen on port 8531 > Found mod_perl Version 1.30 > Found LWP::UserAgent Version 5.822 > Found HTML::HeadParser Version 3.59 > Apache::Session not installed on this system > -> Disable tests for persistent data storage > Found File::Spec Version 3.29 > Found CGI Version 3.42 > Checking if your kit is complete... > Looks good > Writing Makefile for HTML::Embperl > ===> Building for p5-HTML-Embperl-1.3.6_2 > cp CVS.pod blib/lib/HTML/Embperl/CVS.pod > cp Embperl.pod blib/lib/HTML/Embperl.pod > cp IntroEmbperlObject.pod blib/lib/HTML/Embperl/IntroEmbperlObject.pod > cp Faq.pod blib/lib/HTML/Embperl/Faq.pod > cp Embperl/Module.pm blib/lib/HTML/Embperl/Module.pm > cp Embperl/Session.pm blib/lib/HTML/Embperl/Session.pm > cp FeaturesD.pod blib/lib/HTML/Embperl/FeaturesD.pod > cp INSTALL.pod blib/lib/HTML/Embperl/INSTALL.pod > cp Changes.pod blib/lib/HTML/Embperl/Changes.pod > cp NEWS.pod blib/lib/HTML/Embperl/NEWS.pod > cp Embperl.pm blib/lib/HTML/Embperl.pm > cp Intro.pod blib/lib/HTML/Embperl/Intro.pod > cp EmbperlD.pod blib/lib/HTML/EmbperlD.pod > cp IntroD.pod blib/lib/HTML/Embperl/IntroD.pod > cp Features.pod blib/lib/HTML/Embperl/Features.pod > cp EmbperlObject.pm blib/lib/HTML/EmbperlObject.pm > cp Embperl/Mail.pm blib/lib/HTML/Embperl/Mail.pm > cp TipsAndTricks.pod blib/lib/HTML/Embperl/TipsAndTricks.pod > /usr/local/bin/perl5.8.9 /usr/local/lib/perl5/5.8.9/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.8.9/ExtUtils/typemap -typemap typemap Embperl.xs > Embperl.xsc && mv Embperl.xsc Embperl.c > cc -c -I/usr/local/include/apache -I/usr/local/include/apache/regex -I/usr/local/include/apache/os/unix -I/work/a/ports/www/p5-HTML-Embperl/work/HTML-Embperl-1.3.6/xs -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DVERSION=\"1.3.6\" -DXS_VERSION=\"1.3.6\" -DPIC -fPIC "-I/usr/local/lib/perl5/5.8.9/mach/CORE" -DAPACHE -o Embperl.o Embperl.c > Embperl.c: In function `XS_HTML__Embperl_SetupRequest': > Embperl.c:330: warning: static declaration of 'XS_HTML__Embperl_CurrReq' follows non-static declaration > Embperl.c:328: warning: previous declaration of 'XS_HTML__Embperl_CurrReq' was here > Embperl.c:360: warning: static declaration of 'XS_HTML__Embperl_Clock' follows non-static declaration > Embperl.c:358: warning: previous declaration of 'XS_HTML__Embperl_Clock' was here > Embperl.c:387: warning: static declaration of 'XS_HTML__Embperl_GetPackageOfFile' follows non-static declaration > Embperl.c:385: warning: previous declaration of 'XS_HTML__Embperl_GetPackageOfFile' was here > Embperl.c:417: warning: static declaration of 'XS_HTML__Embperl_logerror' follows non-static declaration > Embperl.c:415: warning: previous declaration of 'XS_HTML__Embperl_logerror' was here > Embperl.c:475: warning: static declaration of 'XS_HTML__Embperl_log' follows non-static declaration > Embperl.c:473: warning: previous declaration of 'XS_HTML__Embperl_log' was here > Embperl.c:500: warning: static declaration of 'XS_HTML__Embperl_output' follows non-static declaration > Embperl.c:498: warning: previous declaration of 'XS_HTML__Embperl_output' was here > Embperl.c:540: warning: static declaration of 'XS_HTML__Embperl_logevalerr' follows non-static declaration > Embperl.c:538: warning: previous declaration of 'XS_HTML__Embperl_logevalerr' was here > Embperl.c:570: warning: static declaration of 'XS_HTML__Embperl_getlineno' follows non-static declaration > Embperl.c:568: warning: previous declaration of 'XS_HTML__Embperl_getlineno' was here > Embperl.c:596: warning: static declaration of 'XS_HTML__Embperl_flushlog' follows non-static declaration > Embperl.c:594: warning: previous declaration of 'XS_HTML__Embperl_flushlog' was here > Embperl.c:619: warning: static declaration of 'XS_HTML__Embperl_Sourcefile' follows non-static declaration > Embperl.c:617: warning: previous declaration of 'XS_HTML__Embperl_Sourcefile' was here > Embperl.c:648: warning: static declaration of 'XS_HTML__Embperl_ProcessSub' follows non-static declaration > Embperl.c:646: warning: previous declaration of 'XS_HTML__Embperl_ProcessSub' was here > Embperl.c:677: warning: static declaration of 'XS_HTML__Embperl_exit' follows non-static declaration > Embperl.c:675: warning: previous declaration of 'XS_HTML__Embperl_exit' was here > Embperl.c:733: warning: static declaration of 'XS_HTML__Embperl__Req_CurrPackage' follows non-static declaration > Embperl.c:731: warning: previous declaration of 'XS_HTML__Embperl__Req_CurrPackage' was here > Embperl.c:768: warning: static declaration of 'XS_HTML__Embperl__Req_ExportHash' follows non-static declaration > Embperl.c:766: warning: previous declaration of 'XS_HTML__Embperl__Req_ExportHash' was here > Embperl.c:805: warning: static declaration of 'XS_HTML__Embperl__Req_Sourcefile' follows non-static declaration > Embperl.c:803: warning: previous declaration of 'XS_HTML__Embperl__Req_Sourcefile' was here > Embperl.c:840: warning: static declaration of 'XS_HTML__Embperl__Req_Path' follows non-static declaration > Embperl.c:838: warning: previous declaration of 'XS_HTML__Embperl__Req_Path' was here > Embperl.c:890: warning: static declaration of 'XS_HTML__Embperl__Req_PathNdx' follows non-static declaration > Embperl.c:888: warning: previous declaration of 'XS_HTML__Embperl__Req_PathNdx' was here > Embperl.c:931: warning: static declaration of 'XS_HTML__Embperl__Req_ReqFilename' follows non-static declaration > Embperl.c:929: warning: previous declaration of 'XS_HTML__Embperl__Req_ReqFilename' was here > Embperl.c:966: warning: static declaration of 'XS_HTML__Embperl__Req_Debug' follows non-static declaration > Embperl.c:964: warning: previous declaration of 'XS_HTML__Embperl__Req_Debug' was here > Embperl.c:998: warning: static declaration of 'XS_HTML__Embperl__Req_ApacheReq' follows non-static declaration > Embperl.c:996: warning: previous declaration of 'XS_HTML__Embperl__Req_ApacheReq' was here > Embperl.c:1035: warning: static declaration of 'XS_HTML__Embperl__Req_ErrArray' follows non-static declaration > Embperl.c:1033: warning: previous declaration of 'XS_HTML__Embperl__Req_ErrArray' was here > Embperl.c:1067: warning: static declaration of 'XS_HTML__Embperl__Req_FormArray' follows non-static declaration > Embperl.c:1065: warning: previous declaration of 'XS_HTML__Embperl__Req_FormArray' was here > Embperl.c:1099: warning: static declaration of 'XS_HTML__Embperl__Req_FormHash' follows non-static declaration > Embperl.c:1097: warning: previous declaration of 'XS_HTML__Embperl__Req_FormHash' was here > Embperl.c:1131: warning: static declaration of 'XS_HTML__Embperl__Req_EnvHash' follows non-static declaration > Embperl.c:1129: warning: previous declaration of 'XS_HTML__Embperl__Req_EnvHash' was here > Embperl.c:1163: warning: static declaration of 'XS_HTML__Embperl__Req_LogFileStartPos' follows non-static declaration > Embperl.c:1161: warning: previous declaration of 'XS_HTML__Embperl__Req_LogFileStartPos' was here > Embperl.c:1195: warning: static declaration of 'XS_HTML__Embperl__Req_VirtLogURI' follows non-static declaration > Embperl.c:1193: warning: previous declaration of 'XS_HTML__Embperl__Req_VirtLogURI' was here > Embperl.c:1230: warning: static declaration of 'XS_HTML__Embperl__Req_CookieName' follows non-static declaration > Embperl.c:1228: warning: previous declaration of 'XS_HTML__Embperl__Req_CookieName' was here > Embperl.c:1265: warning: static declaration of 'XS_HTML__Embperl__Req_SessionMgnt' follows non-static declaration > Embperl.c:1263: warning: previous declaration of 'XS_HTML__Embperl__Req_SessionMgnt' was here > Embperl.c:1299: warning: static declaration of 'XS_HTML__Embperl__Req_SubReq' follows non-static declaration > Embperl.c:1297: warning: previous declaration of 'XS_HTML__Embperl__Req_SubReq' was here > Embperl.c:1331: warning: static declaration of 'XS_HTML__Embperl__Req_Error' follows non-static declaration > Embperl.c:1329: warning: previous declaration of 'XS_HTML__Embperl__Req_Error' was here > Embperl.c:1365: warning: static declaration of 'XS_HTML__Embperl__Req_ProcessBlock' follows non-static declaration > Embperl.c:1363: warning: previous declaration of 'XS_HTML__Embperl__Req_ProcessBlock' was here > Embperl.c:1400: warning: static declaration of 'XS_HTML__Embperl__Req_ProcessSub' follows non-static declaration > Embperl.c:1398: warning: previous declaration of 'XS_HTML__Embperl__Req_ProcessSub' was here > Embperl.c:1435: warning: static declaration of 'XS_HTML__Embperl__Req_logevalerr' follows non-static declaration > Embperl.c:1433: warning: previous declaration of 'XS_HTML__Embperl__Req_logevalerr' was here > Embperl.c:1473: warning: static declaration of 'XS_HTML__Embperl__Req_logerror' follows non-static declaration > Embperl.c:1471: warning: previous declaration of 'XS_HTML__Embperl__Req_logerror' was here > Embperl.c:1539: warning: static declaration of 'XS_HTML__Embperl__Req_getloghandle' follows non-static declaration > Embperl.c:1537: warning: previous declaration of 'XS_HTML__Embperl__Req_getloghandle' was here > Embperl.c:1571: warning: static declaration of 'XS_HTML__Embperl__Req_getlogfilepos' follows non-static declaration > Embperl.c:1569: warning: previous declaration of 'XS_HTML__Embperl__Req_getlogfilepos' was here > Embperl.c:1604: warning: static declaration of 'XS_HTML__Embperl__Req_output' follows non-static declaration > Embperl.c:1602: warning: previous declaration of 'XS_HTML__Embperl__Req_output' was here > Embperl.c:1634: warning: static declaration of 'XS_HTML__Embperl__Req_log' follows non-static declaration > Embperl.c:1632: warning: previous declaration of 'XS_HTML__Embperl__Req_log' was here > Embperl.c:1665: warning: static declaration of 'XS_HTML__Embperl__Req_flushlog' follows non-static declaration > Embperl.c:1663: warning: previous declaration of 'XS_HTML__Embperl__Req_flushlog' was here > Embperl.c:1694: warning: static declaration of 'XS_HTML__Embperl__Req_getlineno' follows non-static declaration > Embperl.c:1692: warning: previous declaration of 'XS_HTML__Embperl__Req_getlineno' was here > Embperl.c:1726: warning: static declaration of 'XS_HTML__Embperl__Req_log_svs' follows non-static declaration > Embperl.c:1724: warning: previous declaration of 'XS_HTML__Embperl__Req_log_svs' was here > Embperl.c:1756: warning: static declaration of 'XS_HTML__Embperl__Req_Escape' follows non-static declaration > Embperl.c:1754: warning: previous declaration of 'XS_HTML__Embperl__Req_Escape' was here > Embperl.c:1794: warning: static declaration of 'XS_HTML__Embperl__Req_ExecuteReq' follows non-static declaration > Embperl.c:1792: warning: previous declaration of 'XS_HTML__Embperl__Req_ExecuteReq' was here > Embperl.c:1828: warning: static declaration of 'XS_HTML__Embperl__Req_Abort' follows non-static declaration > Embperl.c:1826: warning: previous declaration of 'XS_HTML__Embperl__Req_Abort' was here > Embperl.c:1861: warning: static declaration of 'XS_HTML__Embperl__Req_FreeRequest' follows non-static declaration > Embperl.c:1859: warning: previous declaration of 'XS_HTML__Embperl__Req_FreeRequest' was here > Embperl.c:2021: warning: static declaration of 'boot_HTML__Embperl' follows non-static declaration > Embperl.c:2019: warning: previous declaration of 'boot_HTML__Embperl' was here > Embperl.c:2111: error: syntax error at end of input > *** Error code 1 > > Stop in /work/a/ports/www/p5-HTML-Embperl/work/HTML-Embperl-1.3.6. > *** Error code 1 > > Stop in /a/ports/www/p5-HTML-Embperl. > ================================================================ > build of /usr/ports/www/p5-HTML-Embperl ended at Thu Jan 15 02:50:22 UTC 2009 -- Pav Lucistnik It's ten o'clock; do you know where your processes are? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090115/dae29ee5/attachment.pgp From pav at FreeBSD.org Thu Jan 15 14:56:06 2009 From: pav at FreeBSD.org (Pav Lucistnik) Date: Thu Jan 15 14:56:13 2009 Subject: [Fwd: p5-XML-Xerces-2.7.0 failed on amd64 6] Message-ID: <1232060149.42745.16.camel@hood.oook.cz> -------- 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 -- Pav Lucistnik 25 And the Lord spoke unto the Angel that guarded the eastern gate, saying, Where is the flaming sword which was given unto thee? 26 And the Angel said, I had here only a moment ago, I must have put it down some where, forget my own head next. 27 And the Lord did not ask him again. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090115/68d4178d/attachment.pgp From pav at FreeBSD.org Thu Jan 15 14:58:41 2009 From: pav at FreeBSD.org (Pav Lucistnik) Date: Thu Jan 15 14:58:50 2009 Subject: [Fwd: wml-2.0.12,1 failed on amd64 6] Message-ID: <1232060306.42745.18.camel@hood.oook.cz> -------- P?eposlan? zpr?va -------- > Od: User Ports-amd64 > Komu: cvs@oook.cz > P?edm?t: wml-2.0.12,1 failed on amd64 6 > Datum: Thu, 15 Jan 2009 03:02:32 GMT > > Excerpt from the build log at > > http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.6.20090114102347/wml-2.0.12,1.log > > building wml-2.0.12,1 on gohan11.freebsd.org > in directory /x/pkgbuild/6/20090114102347/chroot/4391 > building for: 6.4-STABLE amd64 > maintained by: rodrigo@bebik.net > port directory: /usr/ports/www/wml > Makefile ident: $FreeBSD: ports/www/wml/Makefile,v 1.67 2009/01/10 22:58:13 wxs Exp $ > > [... lines trimmed ...] > > Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > pkg_add perl-5.8.9.tbz > skipping perl-5.8.9, already added > pkg_add png-1.2.34.tbz > ===> wml-2.0.12,1 depends on executable: lynx - found > ===> wml-2.0.12,1 depends on file: /usr/local/lib/perl5/site_perl/5.8.9/mach/XML/Parser.pm - found > ===> wml-2.0.12,1 depends on executable: gmake - found > ===> wml-2.0.12,1 depends on file: /usr/local/bin/perl5.8.9 - found > ===> wml-2.0.12,1 depends on shared library: png.5 - found > ===> Configuring for wml-2.0.12,1 > [: missing ] > Configuring for WML 2.0.12 (16-Apr-2008) > checking whether to enable maintainer-specific portions of Makefiles... no > > CHECK: Build Environment > checking for built user... root@freebsd.FreeBSD.org > checking for built date... 15-Jan-2009 > checking build system type... amd64-unknown-freebsd6.4 > checking host system type... amd64-unknown-freebsd6.4 > checking target system type... amd64-unknown-freebsd6.4 > > CHECK: Build Utilities > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking how to run the C preprocessor... gcc -E > checking for ranlib... ranlib > checking whether make sets $(MAKE)... yes > > CHECK: Perl Language > checking for Perl language... /usr/local/bin/perl5.8.9 v5.008 > checking for MakeMaker's private install paths... ok > > RESULT: Substituting Files > configure: creating ./config.status > config.status: creating Makefile > config.status: creating wml_frontend/Makefile > config.status: creating wml_backend/Makefile > config.status: creating wml_backend/p1_ipp/Makefile > config.status: creating wml_backend/p5_divert/Makefile > config.status: creating wml_backend/p6_asubst/Makefile > config.status: creating wml_backend/p7_htmlfix/Makefile > config.status: creating wml_backend/p8_htmlstrip/Makefile > config.status: creating wml_backend/p9_slice/Makefile > config.status: creating wml_common/Makefile > config.status: creating wml_docs/Makefile > config.status: creating wml_aux/Makefile > config.status: creating wml_aux/htmlinfo/Makefile > config.status: creating wml_aux/htmlclean/Makefile > config.status: creating wml_aux/linklint/Makefile > config.status: creating wml_aux/map2html/Makefile > config.status: creating wml_aux/txt2html/Makefile > config.status: creating wml_aux/tidy/Makefile > config.status: creating wml_aux/weblint/Makefile > config.status: creating wml_aux/freetable/Makefile > config.status: creating wml_misc/Makefile > config.status: creating wml_include/Makefile > config.status: creating wml_test/Makefile > === configuring in wml_backend/p2_mp4h (/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h) > configure: running /bin/sh ./configure '--prefix=/usr/local' '--with-perl=/usr/local/bin/perl5.8.9' '--with-catdir=man' '--with-tidy=/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/tidy/tidy' --cache-file=/dev/null --srcdir=. > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... ./install-sh -c -d > checking for gawk... no > checking for mawk... no > checking for nawk... nawk > checking whether make sets $(MAKE)... yes > checking for style of include used by make... GNU > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking dependency style of gcc... gcc3 > checking for function prototypes... yes > checking how to run the C preprocessor... gcc -E > checking for grep that handles long lines and -e... /usr/bin/grep > checking for egrep... /usr/bin/grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for string.h... (cached) yes > checking whether NLS is requested... yes > checking for msgfmt... /usr/local/bin/msgfmt > checking for gmsgfmt... /usr/local/bin/msgfmt > checking for xgettext... /usr/local/bin/xgettext > checking for msgmerge... /usr/local/bin/msgmerge > checking build system type... x86_64-unknown-freebsd6.4 > checking host system type... x86_64-unknown-freebsd6.4 > checking for ld used by GCC... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for shared library run path origin... done > checking for CFPreferencesCopyAppValue... no > checking for CFLocaleCopyCurrent... no > checking for GNU gettext in libc... no > checking for iconv... no, consider installing GNU libiconv > checking for GNU gettext in libintl... no > checking whether to use NLS... no > checking for xgettext... (cached) /usr/local/bin/xgettext > checking for msgmerge... (cached) /usr/local/bin/msgmerge > checking for msgfmt... (cached) /usr/local/bin/msgfmt > checking for perl... /usr/bin/perl > checking for XML::Parser... ok > shtool:echo:Warning: unable to determine terminal sequence for bold mode > Configuring for mp4h 1.3.0 (06-Jul-2002) > checking for gcc... (cached) gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking for gcc option to accept ISO C89... (cached) none needed > checking dependency style of gcc... (cached) gcc3 > checking how to run the C preprocessor... gcc -E > checking for a sed that does not truncate output... /usr/bin/sed > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for /usr/bin/ld option to reload object files... -r > checking for BSD-compatible nm... /usr/bin/nm -B > checking whether ln -s works... yes > checking how to recognize dependent libraries... pass_all > checking dlfcn.h usability... yes > checking dlfcn.h presence... yes > checking for dlfcn.h... yes > checking for g++... g++ > checking whether we are using the GNU C++ compiler... yes > checking whether g++ accepts -g... yes > checking dependency style of g++... gcc3 > checking how to run the C++ preprocessor... g++ -E > checking for g77... no > checking for xlf... no > checking for f77... f77 > checking whether we are using the GNU Fortran 77 compiler... yes > checking whether f77 accepts -g... yes > checking the maximum length of command line arguments... 196608 > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for objdir... .libs > checking for ar... ar > checking for ranlib... ranlib > checking for strip... strip > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC > checking if gcc PIC flag -fPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes > checking whether -lc should be explicitly linked in... yes > checking dynamic linker characteristics... freebsd6.4 ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > configure: creating libtool > appending configuration tag "CXX" to libtool > checking for ld used by g++... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes > checking for g++ option to produce PIC... -fPIC > checking if g++ PIC flag -fPIC works... yes > checking if g++ static flag -static works... yes > checking if g++ supports -c -o file.o... yes > checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes > checking dynamic linker characteristics... freebsd6.4 ld.so > checking how to hardcode library paths into programs... immediate > appending configuration tag "F77" to libtool > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for f77 option to produce PIC... -fPIC > checking if f77 PIC flag -fPIC works... yes > checking if f77 static flag -static works... yes > checking if f77 supports -c -o file.o... yes > checking whether the f77 linker (/usr/bin/ld) supports shared libraries... yes > checking dynamic linker characteristics... freebsd6.4 ld.so > checking how to hardcode library paths into programs... immediate > checking whether make sets $(MAKE)... (cached) yes > checking for a BSD-compatible install... /usr/bin/install -c > > shtool:echo:Warning: unable to determine terminal sequence for bold mode > Checking for headers and libraries > checking for library containing strerror... none required > checking for ANSI C header files... (cached) yes > checking for size_t... yes > checking for an ANSI C-conforming const... yes > checking limits.h usability... yes > checking limits.h presence... yes > checking for limits.h... yes > checking locale.h usability... yes > checking locale.h presence... yes > checking for locale.h... yes > checking for memory.h... (cached) yes > checking stdarg.h usability... yes > checking stdarg.h presence... yes > checking for stdarg.h... yes > checking for string.h... (cached) yes > checking for unistd.h... (cached) yes > checking time.h usability... yes > checking time.h presence... yes > checking for time.h... yes > checking pwd.h usability... yes > checking pwd.h presence... yes > checking for pwd.h... yes > checking grp.h usability... yes > checking grp.h presence... yes > checking for grp.h... yes > checking dirent.h usability... yes > checking dirent.h presence... yes > checking for dirent.h... yes > checking sys/param.h usability... yes > checking sys/param.h presence... yes > checking for sys/param.h... yes > checking for sys/stat.h... (cached) yes > checking for sys/types.h... (cached) yes > checking sys/times.h usability... yes > checking sys/times.h presence... yes > checking for sys/times.h... yes > checking for mkstemp... yes > checking for strchr... yes > checking for strerror... yes > checking for tmpfile... yes > checking for getpwuid... yes > checking for getgrgid... yes > checking for bcopy... yes > checking for memmove... yes > checking for working alloca.h... no > checking for alloca... yes > checking for vprintf... yes > checking for _doprnt... no > checking for strtol... yes > checking for obstack... no > checking for xmalloc... no > checking for xstrdup... no > checking for getopt_long... yes > checking for HTML postprocessing... /work/a/ports/www/wml/work/wml-2.0.12/wml_aux/tidy/tidy > checking if support for loadable modules is requested... yes > checking for dlopen... yes > checking if malloc debugging is wanted... no > > shtool:echo:Warning: unable to determine terminal sequence for bold mode > Checking for loadable modules support > checking libintl.h usability... no > checking libintl.h presence... no > checking for libintl.h... no > checking for dirent.h that defines DIR... yes > checking for library containing opendir... none required > checking which extension is used for loadable modules... .so > checking which variable specifies run-time library path... LD_LIBRARY_PATH > checking for the default library search path... /lib /usr/lib > checking for objdir... .libs > checking whether libtool supports -dlopen/-dlpreopen... yes > checking for shl_load... no > checking for shl_load in -ldld... no > checking for dlopen in -ldl... no > checking for dlerror... yes > checking for _ prefix in compiled symbols... no > checking whether deplibs are loaded by dlopen... yes > checking argz.h usability... no > checking argz.h presence... no > checking for argz.h... no > checking for error_t... no > checking for argz_append... no > checking for argz_create_sep... no > checking for argz_insert... no > checking for argz_next... no > checking for argz_stringify... no > checking assert.h usability... yes > checking assert.h presence... yes > checking for assert.h... yes > checking ctype.h usability... yes > checking ctype.h presence... yes > checking for ctype.h... yes > checking errno.h usability... yes > checking errno.h presence... yes > checking for errno.h... yes > checking malloc.h usability... no > checking malloc.h presence... no > checking for malloc.h... no > checking for memory.h... (cached) yes > checking for stdlib.h... (cached) yes > checking stdio.h usability... yes > checking stdio.h presence... yes > checking for stdio.h... yes > checking for unistd.h... (cached) yes > checking dl.h usability... no > checking dl.h presence... no > checking for dl.h... no > checking sys/dl.h usability... no > checking sys/dl.h presence... no > checking for sys/dl.h... no > checking dld.h usability... no > checking dld.h presence... no > checking for dld.h... no > checking mach-o/dyld.h usability... no > checking mach-o/dyld.h presence... no > checking for mach-o/dyld.h... no > checking for string.h... (cached) yes > checking for strchr... (cached) yes > checking for strrchr... yes > checking for memcpy... yes > checking for memmove... (cached) yes > checking for strcmp... yes > checking for closedir... yes > checking for opendir... yes > checking for readdir... yes > checking which modules to compile... system > configure: creating ./config.status > config.status: creating Makefile > config.status: creating intl/Makefile > config.status: WARNING: intl/Makefile.in seems to ignore the --datarootdir setting > config.status: creating pcre/Makefile > config.status: creating lib/Makefile > config.status: creating src/Makefile > config.status: creating po/Makefile.in > config.status: creating modules/Makefile > config.status: creating modules/system/Makefile > config.status: creating modules/intl/Makefile > config.status: creating doc/Makefile > config.status: creating tests/Makefile > config.status: creating config.h > config.status: executing depfiles commands > config.status: executing po-directories commands > config.status: creating po/POTFILES > config.status: creating po/Makefile > config.status: executing intltool commands > ./config.status: cannot open ./intltool-extract.in: No such file or directory > mv: rename intltool-extract.out to intltool-extract: No such file or directory > ./config.status: cannot open ./intltool-merge.in: No such file or directory > mv: rename intltool-merge.out to intltool-merge: No such file or directory > ./config.status: cannot open ./intltool-update.in: No such file or directory > mv: rename intltool-update.out to intltool-update: No such file or directory > config.status: executing po/stamp-it commands > > shtool:echo:Warning: unable to determine terminal sequence for bold mode > Now please type make to compile mp4h > > === configuring in wml_backend/p3_eperl (/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p3_eperl) > configure: running /bin/sh ./configure '--prefix=/usr/local' '--with-perl=/usr/local/bin/perl5.8.9' '--with-catdir=man' '--with-tidy=/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/tidy/tidy' --cache-file=/dev/null --srcdir=. > Configuring for ePerl 2.2.14 (02-Aug-1998) > > CHECK: Configuration of Perl Language > checking for Perl language... /usr/local/bin/perl5.8.9 v5.008 > checking for Perl knowledge of system... freebsd-6.4-stable > checking for Perl standard compiler... cc > checking for Perl standard optimization flags... -O2 -fno-strict-aliasing -pipe > checking for Perl standard compilation flags... -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include > checking for Perl standard link flags... -Wl,-E -L/usr/local/lib > checking for Perl library files... -lm -lcrypt -lutil > checking for Perl architecture directory... /usr/local/lib/perl5/5.8.9/mach > checking for Perl dynamic loading support... yes > checking for Perl dynamic loading compilation flags... -DPIC -fPIC > checking for Perl dynamic loading link flags... -Wl,-R/usr/local/lib/perl5/5.8.9/mach/CORE > > CHECK: System Build Environment > checking for build user... root@freebsd.FreeBSD.org > checking for build time... 15-Jan-2009 > checking for gcc... cc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether cc accepts -g... yes > checking for cc option to accept ISO C89... none needed > checking for ranlib... ranlib > checking for ar... ar > checking for size... size > checking for compilation debug mode... disabled > checking whether make sets $(MAKE)... yes > > CHECK: Characteristic of System Headers and Libraries > checking for an ANSI C-conforming const... yes > checking how to run the C preprocessor... cc -E > checking for grep that handles long lines and -e... /usr/bin/grep > checking for egrep... /usr/bin/grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking stdio.h usability... yes > checking stdio.h presence... yes > checking for stdio.h... yes > checking stdarg.h usability... yes > checking stdarg.h presence... yes > checking for stdarg.h... yes > checking for stdlib.h... (cached) yes > checking for string.h... (cached) yes > checking ctype.h usability... yes > checking ctype.h presence... yes > checking for ctype.h... yes > checking for unistd.h... (cached) yes > checking time.h usability... yes > checking time.h presence... yes > checking for time.h... yes > checking signal.h usability... yes > checking signal.h presence... yes > checking for signal.h... yes > checking pwd.h usability... yes > checking pwd.h presence... yes > checking for pwd.h... yes > checking grp.h usability... yes > checking grp.h presence... yes > checking for grp.h... yes > checking for sys/types.h... (cached) yes > checking for sys/stat.h... (cached) yes > checking sys/param.h usability... yes > checking sys/param.h presence... yes > checking for sys/param.h... yes > checking sys/socket.h usability... yes > checking sys/socket.h presence... yes > checking for sys/socket.h... yes > checking netinet/in.h usability... yes > checking netinet/in.h presence... yes > checking for netinet/in.h... yes > checking netdb.h usability... yes > checking netdb.h presence... yes > checking for netdb.h... yes > checking for bool... no > checking for memmove... yes > checking for seteuid... yes > checking for setegid... yes > checking for strdup... yes > > RESULT: Sourcefile Substitution > configure: creating ./config.status > config.status: creating Makefile > config.status: creating config_sc.h > config.status: creating config_ac.h > === configuring in wml_backend/p4_gm4 (/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p4_gm4) > configure: running /bin/sh ./configure '--prefix=/usr/local' '--with-perl=/usr/local/bin/perl5.8.9' '--with-catdir=man' '--with-tidy=/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/tidy/tidy' --cache-file=/dev/null --srcdir=. > loading cache /dev/null > checking for mawk... no > checking for gawk... no > checking for nawk... nawk > checking for gcc... gcc > checking whether the C compiler (gcc ) works... yes > checking whether the C compiler (gcc ) is a cross-compiler... no > checking whether we are using GNU C... yes > checking whether gcc accepts -g... yes > checking for a BSD compatible install... /usr/bin/install -c > checking whether make sets ${MAKE}... yes > checking for ranlib... ranlib > checking how to run the C preprocessor... gcc -E > checking for AIX... no > checking for POSIXized ISC... no > checking for minix/config.h... no > checking for gcc option to accept ANSI C... > checking for function prototypes... yes > checking for working const... yes > checking for Cygwin environment... no > checking for mingw32 environment... no > checking for executable suffix... no > checking for limits.h... yes > checking for memory.h... yes > checking for siginfo.h... no > checking for string.h... yes > checking for unistd.h... yes > checking for ANSI C header files... yes > checking return type of signal handlers... void > checking for size_t... yes > checking for mkstemp... yes > checking for sigaction... yes > checking for sigaltstack... yes > checking for sigstack... no > checking for sigvec... yes > checking for strerror... yes > checking for tmpfile... yes > checking for working alloca.h... no > checking for alloca... yes > checking for vprintf... yes > checking for strtol... yes > checking ecvt declaration... no > checking for ecvt... no > checking if changeword is wanted... no > checking if malloc debugging is wanted... no > updating cache /dev/null > creating ./config.status > creating Makefile > creating lib/Makefile > creating src/Makefile > creating config.h > === configuring in wml_aux/iselect (/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/iselect) > configure: running /bin/sh ./configure '--prefix=/usr/local' '--with-perl=/usr/local/bin/perl5.8.9' '--with-catdir=man' '--with-tidy=/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/tidy/tidy' --cache-file=/dev/null --srcdir=. > Configuring for iSelect 1.2.0 (01-Jul-2000) > Copyright (c) 1996-1999 Ralf S. Engelschall, All Rights Reserved. > loading cache /dev/null > > CHECK: Build Environment > checking for gcc... gcc > checking whether the C compiler (gcc ) works... yes > checking whether the C compiler (gcc ) is a cross-compiler... no > checking whether we are using GNU C... yes > checking whether gcc accepts -g... yes > checking how to run the C preprocessor... gcc -E > checking for compilation debug mode... disabled > checking whether make sets ${MAKE}... yes > > CHECK: Curses Environment > checking for additional include dir... none particular > checking for additional library dir... none particular > checking for ncurses.h... yes > checking for initscr in -lncurses... yes > checking for slcurses.h... no > checking for SLcurses_initscr in -lslang... no > checking which Curses to use... GNU NCurses > > CHECK: System Ingredients > checking for working const... yes > checking for ANSI C header files... yes > checking for stdio.h... yes > checking for stddef.h... yes > checking for string.h... yes > checking for strings.h... yes > checking for stdlib.h... yes > > RESULT: Sourcefile Substitution > updating cache /dev/null > creating ./config.status > creating Makefile > creating config_sc.h > creating config_ac.h > === configuring in wml_common/gd (/work/a/ports/www/wml/work/wml-2.0.12/wml_common/gd) > configure: running /bin/sh ./configure '--prefix=/usr/local' '--with-perl=/usr/local/bin/perl5.8.9' '--with-catdir=man' '--with-tidy=/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/tidy/tidy' --cache-file=/dev/null --srcdir=. > loading cache /dev/null > > CHECK: Build Utilities > checking for gcc... gcc > checking whether the C compiler (gcc ) works... yes > checking whether the C compiler (gcc ) is a cross-compiler... no > checking whether we are using GNU C... yes > checking whether gcc accepts -g... yes > checking how to run the C preprocessor... gcc -E > checking for ranlib... ranlib > checking whether make sets ${MAKE}... yes > > CHECK: PNG Support > checking for png_write_image in -lpng... no > checking for png.h... no > updating cache /dev/null > creating ./config.status > creating Makefile.PL > creating libgd/Makefile.PL > > Now please type 'make' to compile. Good luck. > > ===> Building for wml-2.0.12,1 > ===> wml_frontend (all) > gmake[1]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_frontend' > sed -e '/^=head1/,/^=cut/d' \ > -e '/^__END__/,$d' \ > -e 's|\@WML_VERSION\@|2.0.12 (16-Apr-2008)|g' \ > -e 's|\@WML_CONFIG_ARGS\@|/usr/local/share/config.site /usr/local/etc/config.site|g' \ > -e 's|\@perlprog\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@perlvers\@|5.008|g' \ > -e 's|\@built_system\@|amd64-whatever-freebsd6.4|g' \ > -e 's|\@built_user\@|root@freebsd.FreeBSD.org|g' \ > -e 's|\@built_date\@|15-Jan-2009|g' \ > -e 's|\@compat\@|@compat@|g' \ > -e 's|\@prefix\@|/usr/local|g' \ > -e 's|\@bindir\@|/usr/local/bin|g' \ > -e 's|\@libdir\@|/usr/local/lib/wml|g' \ > -e 's|\@mandir\@|/usr/local/man|g' \ > -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > wmk.pl && chmod a+x wmk.pl > sed -e '/^=head1/,/^=cut/d' \ > -e '/^__END__/,$d' \ > -e 's|\@WML_VERSION\@|2.0.12 (16-Apr-2008)|g' \ > -e 's|\@WML_CONFIG_ARGS\@|/usr/local/share/config.site /usr/local/etc/config.site|g' \ > -e 's|\@perlprog\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@perlvers\@|5.008|g' \ > -e 's|\@built_system\@|amd64-whatever-freebsd6.4|g' \ > -e 's|\@built_user\@|root@freebsd.FreeBSD.org|g' \ > -e 's|\@built_date\@|15-Jan-2009|g' \ > -e 's|\@compat\@|@compat@|g' \ > -e 's|\@prefix\@|/usr/local|g' \ > -e 's|\@bindir\@|/usr/local/bin|g' \ > -e 's|\@libdir\@|/usr/local/lib/wml|g' \ > -e 's|\@mandir\@|/usr/local/man|g' \ > -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > wml.pl && chmod a+x wml.pl > sed -e '/^=head1/,/^=cut/d' \ > -e '/^__END__/,$d' \ > -e 's|\@WML_VERSION\@|2.0.12 (16-Apr-2008)|g' \ > -e 's|\@WML_CONFIG_ARGS\@|/usr/local/share/config.site /usr/local/etc/config.site|g' \ > -e 's|\@perlprog\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@perlvers\@|5.008|g' \ > -e 's|\@built_system\@|amd64-whatever-freebsd6.4|g' \ > -e 's|\@built_user\@|root@freebsd.FreeBSD.org|g' \ > -e 's|\@built_date\@|15-Jan-2009|g' \ > -e 's|\@compat\@|@compat@|g' \ > -e 's|\@prefix\@|/usr/local|g' \ > -e 's|\@bindir\@|/usr/local/bin|g' \ > -e 's|\@libdir\@|/usr/local/lib/wml|g' \ > -e 's|\@mandir\@|/usr/local/man|g' \ > -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > wmb.pl && chmod a+x wmb.pl > sed -e '/^=head1/,/^=cut/d' \ > -e '/^__END__/,$d' \ > -e 's|\@WML_VERSION\@|2.0.12 (16-Apr-2008)|g' \ > -e 's|\@WML_CONFIG_ARGS\@|/usr/local/share/config.site /usr/local/etc/config.site|g' \ > -e 's|\@perlprog\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@perlvers\@|5.008|g' \ > -e 's|\@built_system\@|amd64-whatever-freebsd6.4|g' \ > -e 's|\@built_user\@|root@freebsd.FreeBSD.org|g' \ > -e 's|\@built_date\@|15-Jan-2009|g' \ > -e 's|\@compat\@|@compat@|g' \ > -e 's|\@prefix\@|/usr/local|g' \ > -e 's|\@bindir\@|/usr/local/bin|g' \ > -e 's|\@libdir\@|/usr/local/lib/wml|g' \ > -e 's|\@mandir\@|/usr/local/man|g' \ > -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > wmd.pl && chmod a+x wmd.pl > sed -e '/^=head1/,/^=cut/d' \ > -e '/^__END__/,$d' \ > -e 's|\@WML_VERSION\@|2.0.12 (16-Apr-2008)|g' \ > -e 's|\@WML_CONFIG_ARGS\@|/usr/local/share/config.site /usr/local/etc/config.site|g' \ > -e 's|\@perlprog\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@perlvers\@|5.008|g' \ > -e 's|\@built_system\@|amd64-whatever-freebsd6.4|g' \ > -e 's|\@built_user\@|root@freebsd.FreeBSD.org|g' \ > -e 's|\@built_date\@|15-Jan-2009|g' \ > -e 's|\@compat\@|@compat@|g' \ > -e 's|\@prefix\@|/usr/local|g' \ > -e 's|\@bindir\@|/usr/local/bin|g' \ > -e 's|\@libdir\@|/usr/local/lib/wml|g' \ > -e 's|\@mandir\@|/usr/local/man|g' \ > -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > wmu.pl && chmod a+x wmu.pl > cp wmk.src wmk.pod > pod2man --section=1 --center="EN Tools" --release="EN Tools" wmk.pod |\ > sed -e 's|\@WML_VERSION\@|2.0.12 (16-Apr-2008)|g' > wmk.1 > rm -f wmk.pod > cp wml.src wml.pod > pod2man --section=1 --center="EN Tools" --release="EN Tools" wml.pod |\ > sed -e 's|\@WML_VERSION\@|2.0.12 (16-Apr-2008)|g' > wml.1 > rm -f wml.pod > cp wmb.src wmb.pod > pod2man --section=1 --center="EN Tools" --release="EN Tools" wmb.pod |\ > sed -e 's|\@WML_VERSION\@|2.0.12 (16-Apr-2008)|g' > wmb.1 > rm -f wmb.pod > cp wmd.src wmd.pod > pod2man --section=1 --center="EN Tools" --release="EN Tools" wmd.pod |\ > sed -e 's|\@WML_VERSION\@|2.0.12 (16-Apr-2008)|g' > wmd.1 > rm -f wmd.pod > cp wmu.src wmu.pod > pod2man --section=1 --center="EN Tools" --release="EN Tools" wmu.pod |\ > sed -e 's|\@WML_VERSION\@|2.0.12 (16-Apr-2008)|g' > wmu.1 > rm -f wmu.pod > cp wmd_missing.src wmd_missing.pod > pod2man --section=1 --center="EN Tools" --release="EN Tools" wmd_missing.pod |\ > sed -e 's|\@WML_VERSION\@|2.0.12 (16-Apr-2008)|g' > wmd_missing.1 > rm -f wmd_missing.pod > gmake[1]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_frontend' > <=== wml_frontend > ===> wml_aux (all) > gmake[1]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux' > ===> wml_aux/iselect (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/iselect' > gcc -O2 -I. -o iselect_main.o -c iselect_main.c > gcc -O2 -I. -o iselect_browse.o -c iselect_browse.c > gcc -O2 -I. -o iselect_keys.o -c iselect_keys.c > gcc -O2 -I. -o iselect_getopt.o -c iselect_getopt.c > gcc -O2 -I. -o iselect_version.o -c iselect_version.c > gcc -O2 -I. -o iselect_help.o -c iselect_help.c > gcc -O2 -I. -o iselect_readme.o -c iselect_readme.c > gcc -o iselect iselect_main.o iselect_browse.o iselect_keys.o iselect_getopt.o iselect_version.o iselect_help.o iselect_readme.o -lncurses > set -e; \ > V=`./etc/shtool version -lc -d long iselect_version.c`; \ > pod2man --section=1 \ > --center="Ralf S. Engelschall" \ > --release="EN" \ > iselect.pod | sed -e "s|\@V\@|$V|g" >iselect.1 > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/iselect' > <=== wml_aux/iselect > ===> wml_aux/htmlclean (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/htmlclean' > sed -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > htmlclean.pl && chmod a+x htmlclean.pl > cp htmlclean.src htmlclean.pod > pod2man --section=1 --center="EN Tools" --release="EN Tools" htmlclean.pod >htmlclean.1 > rm -f htmlclean.pod > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/htmlclean' > <=== wml_aux/htmlclean > ===> wml_aux/htmlinfo (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/htmlinfo' > sed -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > htmlinfo.pl && chmod a+x htmlinfo.pl > cp htmlinfo.src htmlinfo.pod > pod2man --section=1 --center="EN Tools" --release="EN Tools" htmlinfo.pod >htmlinfo.1 > rm -f htmlinfo.pod > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/htmlinfo' > <=== wml_aux/htmlinfo > ===> wml_aux/linklint (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/linklint' > sed -e 's|\@libdir\@|/usr/local/lib/wml|g' \ > -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > linklint.pl && chmod a+x linklint.pl > pod2man --section=1 linklint.pod > linklint.1 > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/linklint' > <=== wml_aux/linklint > ===> wml_aux/map2html (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/map2html' > sed -e '/^=head1/,/^=cut/d' \ > -e '/^__END__/,$d' \ > -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@libdir\@|/usr/local/lib/wml|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > map2html.pl && chmod a+x map2html.pl > cp map2html.src map2html.pod > pod2man --section=1 --center="EN Tools" --release="EN Tools" map2html.pod >map2html.1 > rm -f map2html.pod > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/map2html' > <=== wml_aux/map2html > ===> wml_aux/tidy (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/tidy' > gcc -g -O2 -c -o attrs.o attrs.c > gcc -g -O2 -c -o istack.o istack.c > gcc -g -O2 -c -o parser.o parser.c > gcc -g -O2 -c -o tags.o tags.c > gcc -g -O2 -c -o entities.o entities.c > gcc -g -O2 -c -o lexer.o lexer.c > gcc -g -O2 -c -o pprint.o pprint.c > gcc -g -O2 -c -o clean.o clean.c > gcc -g -O2 -c -o localize.o localize.c > gcc -g -O2 -c -o config.o config.c > gcc -g -O2 -c -o tidy.o tidy.c > gcc -g -O2 -o tidy attrs.o istack.o parser.o tags.o entities.o lexer.o pprint.o clean.o localize.o config.o tidy.o -lc > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/tidy' > <=== wml_aux/tidy > ===> wml_aux/txt2html (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/txt2html' > sed -e '/^=head1/,/^=cut/d' \ > -e '/^__END__/,$d' \ > -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@libdir\@|/usr/local/lib/wml|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > txt2html.pl && chmod a+x txt2html.pl > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/txt2html' > <=== wml_aux/txt2html > ===> wml_aux/weblint (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/weblint' > sed -e 's|\@libdir\@|/usr/local/lib/wml|g' \ > -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > weblint.pl && chmod a+x weblint.pl > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/weblint' > <=== wml_aux/weblint > ===> wml_aux/freetable (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/freetable' > sed -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > freetable.pl && chmod a+x freetable.pl > cp freetable.src freetable.pod > pod2man --section=1 \ > --center="GNU/Linux Freedomization Project" \ > --release="GNU/Linux Freedomization Project" \ > freetable.pod > freetable.1 > rm -f freetable.pod > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux/freetable' > <=== wml_aux/freetable > gmake[1]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_aux' > <=== wml_aux > ===> wml_backend (all) > gmake[1]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend' > ===> wml_backend/p1_ipp (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p1_ipp' > sed -e '/^=head1/,/^=cut/d' \ > -e '/^__END__/,$d' \ > -e 's|\@PATH_PERL\@|/usr/local/bin/perl5.8.9|g' \ > -e 's|\@INSTALLPRIVLIB\@|/usr/local/lib/wml/perl/lib|g' \ > -e 's|\@INSTALLARCHLIB\@|/usr/local/lib/wml/perl/lib/amd64-freebsd|g' \ > ipp.pl && chmod a+x ipp.pl > cp ipp.src ipp.pod > pod2man --section=1 --center="EN Tools" --release="EN Tools" ipp.pod |\ > sed -e 's/^.ds N" """""/.ds N" ""/g' \ > -e 's/^.ds T" """""/.ds T" ""/g' >ipp.1 > rm -f ipp.pod > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p1_ipp' > <=== wml_backend/p1_ipp > ===> wml_backend/p2_mp4h (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h' > gmake all-recursive > gmake[3]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h' > Making all in pcre > gmake[4]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/pcre' > gcc -DHAVE_CONFIG_H -DSUPPORT_UTF8 -I. -I.. -g -O2 -MT dftables.o -MD -MP -MF .deps/dftables.Tpo -c -o dftables.o dftables.c > mv -f .deps/dftables.Tpo .deps/dftables.Po > /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o dftables dftables.o > mkdir .libs > gcc -g -O2 -o dftables dftables.o > ./dftables > chartables.c > gmake all-am > gmake[5]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/pcre' > gcc -DHAVE_CONFIG_H -DSUPPORT_UTF8 -I. -I.. -g -O2 -MT maketables.o -MD -MP -MF .deps/maketables.Tpo -c -o maketables.o maketables.c > mv -f .deps/maketables.Tpo .deps/maketables.Po > gcc -DHAVE_CONFIG_H -DSUPPORT_UTF8 -I. -I.. -g -O2 -MT study.o -MD -MP -MF .deps/study.Tpo -c -o study.o study.c > mv -f .deps/study.Tpo .deps/study.Po > gcc -DHAVE_CONFIG_H -DSUPPORT_UTF8 -I. -I.. -g -O2 -MT pcre.o -MD -MP -MF .deps/pcre.Tpo -c -o pcre.o pcre.c > mv -f .deps/pcre.Tpo .deps/pcre.Po > rm -f libpcre.a > ar cru libpcre.a maketables.o study.o pcre.o > ranlib libpcre.a > gmake[5]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/pcre' > gmake[4]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/pcre' > Making all in lib > gmake[4]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/lib' > gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT error.o -MD -MP -MF .deps/error.Tpo -c -o error.o error.c > mv -f .deps/error.Tpo .deps/error.Po > gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT obstack.o -MD -MP -MF .deps/obstack.Tpo -c -o obstack.o obstack.c > mv -f .deps/obstack.Tpo .deps/obstack.Po > gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT xmalloc.o -MD -MP -MF .deps/xmalloc.Tpo -c -o xmalloc.o xmalloc.c > mv -f .deps/xmalloc.Tpo .deps/xmalloc.Po > gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT xstrdup.o -MD -MP -MF .deps/xstrdup.Tpo -c -o xstrdup.o xstrdup.c > mv -f .deps/xstrdup.Tpo .deps/xstrdup.Po > rm -f libmp4h.a > ar cru libmp4h.a error.o obstack.o xmalloc.o xstrdup.o > ranlib libmp4h.a > gmake[4]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/lib' > Making all in src > gmake[4]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/src' > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT builtin.o -MD -MP -MF .deps/builtin.Tpo -c -o builtin.o builtin.c > mv -f .deps/builtin.Tpo .deps/builtin.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT debug.o -MD -MP -MF .deps/debug.Tpo -c -o debug.o debug.c > mv -f .deps/debug.Tpo .deps/debug.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT devel.o -MD -MP -MF .deps/devel.Tpo -c -o devel.o devel.c > mv -f .deps/devel.Tpo .deps/devel.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT freeze.o -MD -MP -MF .deps/freeze.Tpo -c -o freeze.o freeze.c > mv -f .deps/freeze.Tpo .deps/freeze.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT input.o -MD -MP -MF .deps/input.Tpo -c -o input.o input.c > mv -f .deps/input.Tpo .deps/input.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT macro.o -MD -MP -MF .deps/macro.Tpo -c -o macro.o macro.c > mv -f .deps/macro.Tpo .deps/macro.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT module.o -MD -MP -MF .deps/module.Tpo -c -o module.o module.c > mv -f .deps/module.Tpo .deps/module.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT ltdl.o -MD -MP -MF .deps/ltdl.Tpo -c -o ltdl.o ltdl.c > mv -f .deps/ltdl.Tpo .deps/ltdl.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT mp4h.o -MD -MP -MF .deps/mp4h.Tpo -c -o mp4h.o mp4h.c > mv -f .deps/mp4h.Tpo .deps/mp4h.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT output.o -MD -MP -MF .deps/output.Tpo -c -o output.o output.c > mv -f .deps/output.Tpo .deps/output.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT path.o -MD -MP -MF .deps/path.Tpo -c -o path.o path.c > mv -f .deps/path.Tpo .deps/path.Po > gcc -DHAVE_CONFIG_H -I. -I.. -I../pcre -I../lib -g -O2 -MT symtab.o -MD -MP -MF .deps/symtab.Tpo -c -o symtab.o symtab.c > mv -f .deps/symtab.Tpo .deps/symtab.Po > /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -export-dynamic -o mp4h builtin.o debug.o devel.o freeze.o input.o macro.o module.o ltdl.o mp4h.o output.o path.o symtab.o -lm ../lib/libmp4h.a ../pcre/libpcre.a > mkdir .libs > gcc -g -O2 -o mp4h builtin.o debug.o devel.o freeze.o input.o macro.o module.o ltdl.o mp4h.o output.o path.o symtab.o -Wl,--export-dynamic -lm ../lib/libmp4h.a ../pcre/libpcre.a > gmake[4]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/src' > Making all in po > gmake[4]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/po' > gmake[4]: Nothing to be done for `all'. > gmake[4]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/po' > Making all in doc > gmake[4]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/doc' > ../src/mp4h -X 0 -I . -D srcdir="." -D format=pod ./mp4h.mp4h \ > | sed -e 's/_LT_//g' > mp4h.pod > pod2man --section=1 \ > --center="HTML Tools" \ > --release="HTML Tools" \ > mp4h.pod > mp4h.1 > ../src/mp4h -X 0 -I . -D srcdir="." -D format=html ./mp4h.mp4h > mp4h.html > /work/a/ports/www/wml/work/wml-2.0.12/wml_aux/tidy/tidy -m mp4h.html > > Tidy (vers 4th August 2000) Parsing "mp4h.html" > > mp4h.html: Document content looks like HTML 4.01 Transitional > no warnings or errors were found > > gmake[4]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/doc' > Making all in modules > gmake[4]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/modules' > Making all in intl > gmake[5]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/modules/intl' > gmake[5]: Nothing to be done for `all'. > gmake[5]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/modules/intl' > Making all in system > gmake[5]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/modules/system' > /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib -I../../src -g -O2 -MT sh.lo -MD -MP -MF .deps/sh.Tpo -c -o sh.lo sh.c > mkdir .libs > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib -I../../src -g -O2 -MT sh.lo -MD -MP -MF .deps/sh.Tpo -c sh.c -fPIC -DPIC -o .libs/sh.o > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib -I../../src -g -O2 -MT sh.lo -MD -MP -MF .deps/sh.Tpo -c sh.c -o sh.o >/dev/null 2>&1 > mv -f .deps/sh.Tpo .deps/sh.Plo > /bin/sh ../../libtool --tag=CC --mode=link gcc -g -O2 -module -o sh.la -rpath /usr/local/lib/mp4h/1.3.0/system sh.lo > gcc -shared .libs/sh.o -Wl,-soname -Wl,sh.so.0 -o .libs/sh.so.0 > (cd .libs && rm -f sh.so && ln -s sh.so.0 sh.so) > (cd .libs && rm -f sh.so && ln -s sh.so.0 sh.so) > ar cru .libs/sh.a sh.o > ranlib .libs/sh.a > creating sh.la > (cd .libs && rm -f sh.la && ln -s ../sh.la sh.la) > /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib -I../../src -g -O2 -MT exec.lo -MD -MP -MF .deps/exec.Tpo -c -o exec.lo exec.c > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib -I../../src -g -O2 -MT exec.lo -MD -MP -MF .deps/exec.Tpo -c exec.c -fPIC -DPIC -o .libs/exec.o > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib -I../../src -g -O2 -MT exec.lo -MD -MP -MF .deps/exec.Tpo -c exec.c -o exec.o >/dev/null 2>&1 > mv -f .deps/exec.Tpo .deps/exec.Plo > /bin/sh ../../libtool --tag=CC --mode=link gcc -g -O2 -module -o exec.la -rpath /usr/local/lib/mp4h/1.3.0/system exec.lo > gcc -shared .libs/exec.o -Wl,-soname -Wl,exec.so.0 -o .libs/exec.so.0 > (cd .libs && rm -f exec.so && ln -s exec.so.0 exec.so) > (cd .libs && rm -f exec.so && ln -s exec.so.0 exec.so) > ar cru .libs/exec.a exec.o > ranlib .libs/exec.a > creating exec.la > (cd .libs && rm -f exec.la && ln -s ../exec.la exec.la) > sed -e '/^=head1/,/^=cut/d' -e '/^##EOF##/,$d' sh.src > sh.mp4hp > cat sh.src > system:sh.pod && pod2man --section=3 \ > --center="mp4h modules" \ > --release="mp4h modules" \ > system:sh.pod > systemsh.3 && rm -f system:sh.pod > sed -e '/^=head1/,/^=cut/d' -e '/^##EOF##/,$d' exec.src > exec.mp4hp > cat exec.src > system:exec.pod && pod2man --section=3 \ > --center="mp4h modules" \ > --release="mp4h modules" \ > system:exec.pod > systemexec.3 && rm -f system:exec.pod > gmake[5]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/modules/system' > gmake[5]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/modules' > gmake[5]: Nothing to be done for `all-am'. > gmake[5]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/modules' > gmake[4]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/modules' > Making all in tests > gmake[4]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/tests' > gmake[4]: Nothing to be done for `all'. > gmake[4]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h/tests' > gmake[4]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h' > gmake[4]: Nothing to be done for `all-am'. > gmake[4]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h' > gmake[3]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h' > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p2_mp4h' > <=== wml_backend/p2_mp4h > ===> wml_backend/p3_eperl (all) > gmake[2]: Entering directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p3_eperl' > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_main.c > /usr/local/bin/perl5.8.9 eperl_perl5_sm.pl >eperl_perl5_sm.h > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_perl5.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_parse.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_pp.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_sys.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_http.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_getopt.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_debug.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_config.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_version.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_readme.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_license.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_logo.c > cc -O2 -fno-strict-aliasing -pipe -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I. -c eperl_powered.c > cc -Wl,-R/usr/local/lib/perl5/5.8.9/mach/CORE -Wl,-E -L/usr/local/lib -L/usr/local/lib/perl5/5.8.9/mach/CORE -o eperl eperl_main.o eperl_perl5.o eperl_parse.o eperl_pp.o eperl_sys.o eperl_http.o eperl_getopt.o eperl_debug.o eperl_config.o eperl_version.o eperl_readme.o eperl_license.o eperl_logo.o eperl_powered.o /usr/local/lib/perl5/5.8.9/mach/auto/DynaLoader/DynaLoader.a -lperl -lm -lcrypt -lutil > cc: /usr/local/lib/perl5/5.8.9/mach/auto/DynaLoader/DynaLoader.a: No such file or directory > gmake[2]: *** [eperl] Error 1 > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p3_eperl' > gmake[1]: *** [all] Error 1 > gmake[1]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend' > gmake: *** [all] Error 1 > *** Error code 2 > > Stop in /a/ports/www/wml. > ================================================================ > build of /usr/ports/www/wml ended at Thu Jan 15 03:02:29 UTC 2009 -- Pav Lucistnik > With a 10 MHz 386 the downloading speed would most likely drop > to a crawl or stop with the decoding process etc. I think most 10MHz 386 users are quite accustomed to things dropping to a crawl. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090115/c0e64723/attachment-0001.pgp From QAT at FreeBSD.org Thu Jan 15 22:47:51 2009 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Thu Jan 15 22:47:57 2009 Subject: devel/p5-Tree-DAG_Node - fails: mtree Message-ID: <20090116064113.1BF548FC71@release.ixsystems.com> Hi, Excerpt from http://QAT.TecNik93.com/logs/7-STABLE-FPT-NPD/p5-Tree-DAG_Node-1.06.log : building p5-Tree-DAG_Node-1.06 in directory /usr/local/tinderbox/7-STABLE-FPT-NPD maintained by: perl@FreeBSD.org building for: 7.1-PRERELEASE amd64 Makefile ident: $FreeBSD: ports/devel/p5-Tree-DAG_Node/Makefile,v 1.6 2007/12/18 17:01:28 miwi Exp $ port directory: /usr/ports/devel/p5-Tree-DAG_Node ................................................... Skipping /usr/bin/perl5 Done. Creating various symlinks in /usr/bin... Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl Symlinking /usr/local/bin/perl5.8.9 to /usr/bin/perl5 Done. Cleaning up /etc/make.conf... Done. Spamming /etc/make.conf... Done. Cleaning up /etc/manpath.config... Done. Spamming /etc/manpath.config... Done. mtree: lib: No such file or directory ===> p5-Tree-DAG_Node-1.06 depends on file: /usr/local/bin/perl5.8.9 - found ===> Configuring for p5-Tree-DAG_Node-1.06 Checking if your kit is complete... Looks good Writing Makefile for Tree::DAG_Node ===> Building for p5-Tree-DAG_Node-1.06 cp lib/Tree/DAG_Node.pm blib/lib/Tree/DAG_Node.pm Manifying blib/man3/Tree::DAG_Node.3 ================================================================ ======================================== make: don't know how to make regression-test(continuing) ================================================================ Fatal error: filesystem was touched prior to 'make install' phase lib extra libexec extra media extra mnt extra opt extra proc extra rescue extra root extra sbin extra tmp extra usr extra var extra work extra ================================================================ ================================================================ build of /usr/ports/devel/p5-Tree-DAG_Node ended at Fri Jan 16 06:41:11 UTC 2009 The tarballed WRKDIR can be found here: http://QAT.TecNik93.com/wrkdirs/7-STABLE-FPT-NPD/p5-Tree-DAG_Node-1.06.tbz PortsMon page for the port: http://portsmon.freebsd.org/portoverview.py?category=devel&portname=p5-Tree-DAG_Node The build which triggered this BotMail was done under tinderbox-3.1.2_1; dsversion: 3.1 on RELENG_7 on amd64 with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From QAT at FreeBSD.org Thu Jan 15 22:50:31 2009 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Thu Jan 15 22:50:37 2009 Subject: www/p5-libwww - fails: mtree Message-ID: <20090116063700.D75858FC71@release.ixsystems.com> Hi, Excerpt from http://QAT.TecNik93.com/logs/7-STABLE-FPT-NPD/p5-libwww-5.823.log : building p5-libwww-5.823 in directory /usr/local/tinderbox/7-STABLE-FPT-NPD maintained by: perl@FreeBSD.org building for: 7.1-PRERELEASE amd64 Makefile ident: $FreeBSD: ports/www/p5-libwww/Makefile,v 1.86 2009/01/15 09:13:33 jadawin Exp $ port directory: /usr/ports/www/p5-libwww ................................................... Manifying blib/man3/LWP::MemberMixin.3 Manifying blib/man3/LWP::Debug.3 Manifying blib/man3/Net::HTTP.3 Manifying blib/man3/HTTP::Daemon.3 Manifying blib/man3/HTTP::Cookies.3 Manifying blib/man3/LWP::ConnCache.3 Manifying blib/man3/File::Listing.3 Manifying blib/man3/WWW::RobotRules::AnyDBM_File.3 Manifying blib/man3/lwpcook.3 Manifying blib/man3/LWP::MediaTypes.3 Manifying blib/man3/HTTP::Date.3 Manifying blib/man3/WWW::RobotRules.3 Manifying blib/man3/HTTP::Request.3 Manifying blib/man3/HTTP::Negotiate.3 Manifying blib/man3/HTTP::Config.3 Manifying blib/man3/HTTP::Response.3 Manifying blib/man3/HTTP::Headers.3 Manifying blib/man3/LWP::Simple.3 Manifying blib/man3/Bundle::LWP.3 ================================================================ ======================================== make: don't know how to make regression-test(continuing) ================================================================ Fatal error: filesystem was touched prior to 'make install' phase lib extra libexec extra media extra mnt extra opt extra proc extra rescue extra root extra sbin extra tmp extra usr extra var extra work extra ================================================================ ================================================================ build of /usr/ports/www/p5-libwww ended at Fri Jan 16 06:36:59 UTC 2009 The tarballed WRKDIR can be found here: http://QAT.TecNik93.com/wrkdirs/7-STABLE-FPT-NPD/p5-libwww-5.823.tbz PortsMon page for the port: http://portsmon.freebsd.org/portoverview.py?category=www&portname=p5-libwww The build which triggered this BotMail was done under tinderbox-3.1.2_1; dsversion: 3.1 on RELENG_7 on amd64 with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From QAT at FreeBSD.org Thu Jan 15 22:51:31 2009 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Thu Jan 15 22:51:37 2009 Subject: cvs commit: ports/www/p5-libwww Makefile distinfo In-Reply-To: <200901150913.n0F9DXB7011334@repoman.freebsd.org> References: In-Reply-To: <200901150913.n0F9DXB7011334@repoman.freebsd.org> Message-ID: <20090116064451.72F788FC71@release.ixsystems.com> Hi, Excerpt from http://QAT.TecNik93.com/logs/7-STABLE-FPT-NPD/p5-libwww-5.823.log : building p5-libwww-5.823 in directory /usr/local/tinderbox/7-STABLE-FPT-NPD maintained by: perl@FreeBSD.org building for: 7.1-PRERELEASE amd64 Makefile ident: $FreeBSD: ports/www/p5-libwww/Makefile,v 1.86 2009/01/15 09:13:33 jadawin Exp $ port directory: /usr/ports/www/p5-libwww ................................................... Manifying blib/man3/LWP::MemberMixin.3 Manifying blib/man3/LWP::Debug.3 Manifying blib/man3/Net::HTTP.3 Manifying blib/man3/HTTP::Daemon.3 Manifying blib/man3/HTTP::Cookies.3 Manifying blib/man3/LWP::ConnCache.3 Manifying blib/man3/File::Listing.3 Manifying blib/man3/WWW::RobotRules::AnyDBM_File.3 Manifying blib/man3/lwpcook.3 Manifying blib/man3/LWP::MediaTypes.3 Manifying blib/man3/HTTP::Date.3 Manifying blib/man3/WWW::RobotRules.3 Manifying blib/man3/HTTP::Request.3 Manifying blib/man3/HTTP::Negotiate.3 Manifying blib/man3/HTTP::Config.3 Manifying blib/man3/HTTP::Response.3 Manifying blib/man3/HTTP::Headers.3 Manifying blib/man3/LWP::Simple.3 Manifying blib/man3/Bundle::LWP.3 ================================================================ ======================================== make: don't know how to make regression-test(continuing) ================================================================ Fatal error: filesystem was touched prior to 'make install' phase lib extra libexec extra media extra mnt extra opt extra proc extra rescue extra root extra sbin extra tmp extra usr extra var extra work extra ================================================================ ================================================================ build of /usr/ports/www/p5-libwww ended at Fri Jan 16 06:44:49 UTC 2009 The tarballed WRKDIR can be found here: http://QAT.TecNik93.com/wrkdirs/7-STABLE-FPT-NPD/p5-libwww-5.823.tbz PortsMon page for the port: http://portsmon.freebsd.org/portoverview.py?category=www&portname=p5-libwww The build which triggered this BotMail was done under tinderbox-3.1.2_1; dsversion: 3.1 on RELENG_7 on amd64 with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From QAT at FreeBSD.org Thu Jan 15 22:52:35 2009 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Thu Jan 15 22:52:41 2009 Subject: security/p5-Digest-MD5 - fails: mtree Message-ID: <20090116064556.B6FA58FC71@release.ixsystems.com> Hi, Excerpt from http://QAT.TecNik93.com/logs/7-STABLE-FPT-NPD/p5-Digest-MD5-2.38.log : building p5-Digest-MD5-2.38 in directory /usr/local/tinderbox/7-STABLE-FPT-NPD maintained by: perl@FreeBSD.org building for: 7.1-PRERELEASE amd64 Makefile ident: $FreeBSD: ports/security/p5-Digest-MD5/Makefile,v 1.38 2008/11/14 19:29:58 jadawin Exp $ port directory: /usr/ports/security/p5-Digest-MD5 ................................................... mtree: lib: No such file or directory ===> p5-Digest-MD5-2.38 depends on file: /usr/local/bin/perl5.8.9 - found ===> Configuring for p5-Digest-MD5-2.38 Perl's config says that U32 access must be aligned. Checking if your kit is complete... Looks good Writing Makefile for Digest::MD5 ===> Building for p5-Digest-MD5-2.38 cp MD5.pm blib/lib/Digest/MD5.pm /usr/local/bin/perl5.8.9 /usr/local/lib/perl5/5.8.9/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.8.9/ExtUtils/typemap -typemap typemap MD5.xs > MD5.xsc && mv MD5.xsc MD5.c cc -c -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DVERSION=\"2.38\" -DXS_VERSION=\"2.38\" -DPIC -fPIC "-I/usr/local/lib/perl5/5.8.9/mach/CORE" -DU32_ALIGNMENT_REQUIRED MD5.c Running Mkbootstrap for Digest::MD5 () chmod 644 MD5.bs rm -f blib/arch/auto/Digest/MD5/MD5.so cc -shared -L/usr/local/lib MD5.o -o blib/arch/auto/Digest/MD5/MD5.so chmod 755 blib/arch/auto/Digest/MD5/MD5.so cp MD5.bs blib/arch/auto/Digest/MD5/MD5.bs chmod 644 blib/arch/auto/Digest/MD5/MD5.bs Manifying blib/man3/Digest::MD5.3 ================================================================ ======================================== make: don't know how to make regression-test(continuing) ================================================================ Fatal error: filesystem was touched prior to 'make install' phase lib extra libexec extra media extra mnt extra opt extra proc extra rescue extra root extra sbin extra tmp extra usr extra var extra work extra ================================================================ ================================================================ build of /usr/ports/security/p5-Digest-MD5 ended at Fri Jan 16 06:45:54 UTC 2009 The tarballed WRKDIR can be found here: http://QAT.TecNik93.com/wrkdirs/7-STABLE-FPT-NPD/p5-Digest-MD5-2.38.tbz PortsMon page for the port: http://portsmon.freebsd.org/portoverview.py?category=security&portname=p5-Digest-MD5 The build which triggered this BotMail was done under tinderbox-3.1.2_1; dsversion: 3.1 on RELENG_7 on amd64 with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From QAT at FreeBSD.org Thu Jan 15 22:55:33 2009 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Thu Jan 15 22:55:41 2009 Subject: devel/p5-PathTools - fails: mtree Message-ID: <20090116063030.A31298FC71@release.ixsystems.com> Hi, Excerpt from http://QAT.TecNik93.com/logs/7-STABLE-FPT-NPD/p5-PathTools-3.2900.log : building p5-PathTools-3.2900 in directory /usr/local/tinderbox/7-STABLE-FPT-NPD maintained by: perl@FreeBSD.org building for: 7.1-PRERELEASE amd64 Makefile ident: $FreeBSD: ports/devel/p5-PathTools/Makefile,v 1.35 2008/11/11 07:15:35 clsung Exp $ port directory: /usr/ports/devel/p5-PathTools ................................................... /usr/local/bin/perl5.8.9 /usr/local/lib/perl5/5.8.9/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.8.9/ExtUtils/typemap Cwd.xs > Cwd.xsc && mv Cwd.xsc Cwd.c cc -c -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DVERSION=\"3.29\" -DXS_VERSION=\"3.29\" -DPIC -fPIC "-I/usr/local/lib/perl5/5.8.9/mach/CORE" Cwd.c Running Mkbootstrap for Cwd () chmod 644 Cwd.bs rm -f blib/arch/auto/Cwd/Cwd.so cc -shared -L/usr/local/lib Cwd.o -o blib/arch/auto/Cwd/Cwd.so chmod 755 blib/arch/auto/Cwd/Cwd.so cp Cwd.bs blib/arch/auto/Cwd/Cwd.bs chmod 644 blib/arch/auto/Cwd/Cwd.bs Manifying blib/man3/File::Spec::Mac.3 Manifying blib/man3/File::Spec::OS2.3 Manifying blib/man3/File::Spec::VMS.3 Manifying blib/man3/File::Spec::Cygwin.3 Manifying blib/man3/File::Spec::Epoc.3 Manifying blib/man3/File::Spec::Functions.3 Manifying blib/man3/File::Spec.3 Manifying blib/man3/Cwd.3 Manifying blib/man3/File::Spec::Unix.3 Manifying blib/man3/File::Spec::Win32.3 ================================================================ ======================================== make: don't know how to make regression-test(continuing) ================================================================ Fatal error: filesystem was touched prior to 'make install' phase lib extra libexec extra media extra mnt extra opt extra proc extra rescue extra root extra sbin extra tmp extra usr extra var extra work extra ================================================================ ================================================================ build of /usr/ports/devel/p5-PathTools ended at Fri Jan 16 06:30:28 UTC 2009 The tarballed WRKDIR can be found here: http://QAT.TecNik93.com/wrkdirs/7-STABLE-FPT-NPD/p5-PathTools-3.2900.tbz PortsMon page for the port: http://portsmon.freebsd.org/portoverview.py?category=devel&portname=p5-PathTools The build which triggered this BotMail was done under tinderbox-3.1.2_1; dsversion: 3.1 on RELENG_7 on amd64 with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From kmenzel at whisolutions.com Fri Jan 16 06:47:55 2009 From: kmenzel at whisolutions.com (Ken Menzel) Date: Fri Jan 16 06:48:03 2009 Subject: [Fwd: p5-XML-Xerces-2.7.0 failed on amd64 6] In-Reply-To: <1232060149.42745.16.camel@hood.oook.cz> References: <1232060149.42745.16.camel@hood.oook.cz> Message-ID: <49709981.2010105@whisolutions.com> 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 pav at FreeBSD.org Fri Jan 16 07:30:42 2009 From: pav at FreeBSD.org (Pav Lucistnik) Date: Fri Jan 16 07:31:15 2009 Subject: [Fwd: p5-XML-Xerces-2.7.0 failed on amd64 6] In-Reply-To: <49709981.2010105@whisolutions.com> References: <1232060149.42745.16.camel@hood.oook.cz> <49709981.2010105@whisolutions.com> Message-ID: <1232117639.1546.15.camel@pav.hide.vol.cz> 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 > >> > > > > > -- Pav Lucistnik Pilot to Co-Pilot: Boo. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090116/a17e9703/attachment-0001.pgp From bugmaster at FreeBSD.org Mon Jan 19 03:08:08 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 19 03:10:11 2009 Subject: Current problem reports assigned to perl@FreeBSD.org Message-ID: <200901191108.n0JB86pW064284@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/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/129366 perl devel/p5-ExtUtils-MakeMaker - port trying Install non- o ports/121472 perl Loading perl scripts causes irc/xchat segmentation fau 4 problems total. From skv at FreeBSD.org Mon Jan 19 07:35:16 2009 From: skv at FreeBSD.org (skv@FreeBSD.org) Date: Mon Jan 19 07:35:21 2009 Subject: ports/129366: devel/p5-ExtUtils-MakeMaker - port trying Install non-exists files Message-ID: <200901191535.n0JFZE2w069559@freefall.freebsd.org> Synopsis: devel/p5-ExtUtils-MakeMaker - port trying Install non-exists files State-Changed-From-To: open->closed State-Changed-By: skv State-Changed-When: Mon Jan 19 15:34:44 UTC 2009 State-Changed-Why: Fixed in more correct way. Thanks for reporting! http://www.freebsd.org/cgi/query-pr.cgi?pr=129366 From wxs at FreeBSD.org Mon Jan 19 12:03:20 2009 From: wxs at FreeBSD.org (Wesley Shields) Date: Mon Jan 19 12:03:26 2009 Subject: [Fwd: wml-2.0.12,1 failed on amd64 6] In-Reply-To: <20090119195426.GG9406@atarininja.org> References: <1232060306.42745.18.camel@hood.oook.cz> <20090119195426.GG9406@atarininja.org> Message-ID: <20090119195837.GH9406@atarininja.org> On Mon, Jan 19, 2009 at 02:54:26PM -0500, Wesley Shields wrote: > On Thu, Jan 15, 2009 at 11:58:26PM +0100, Pav Lucistnik wrote: > > [...] > > > > cc: /usr/local/lib/perl5/5.8.9/mach/auto/DynaLoader/DynaLoader.a: No such file or directory > > > gmake[2]: *** [eperl] Error 1 > > > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p3_eperl' > > > gmake[1]: *** [all] Error 1 > > > gmake[1]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend' > > > gmake: *** [all] Error 1 > > > *** Error code 2 > > > > > > Stop in /a/ports/www/wml. > > > ================================================================ > > > build of /usr/ports/www/wml ended at Thu Jan 15 03:02:29 UTC 2009 > > The attached patch fixes this problem and has been tested on my > tinderbox to build correctly. Rodrigo, can you please verify that this > does not cause any run-time regressions and approve it for commit? > > It makes the check for the dynamic loader support correct (it's gone in > perl 5.8.9) and removes the built-in GD support (there was a build > failure in this after you fix the dynamic loader issue). > > Thanks! > > -- WXS Here's the attachment... -- WXS From wxs at FreeBSD.org Mon Jan 19 12:08:19 2009 From: wxs at FreeBSD.org (Wesley Shields) Date: Mon Jan 19 12:08:26 2009 Subject: [Fwd: wml-2.0.12,1 failed on amd64 6] In-Reply-To: <1232060306.42745.18.camel@hood.oook.cz> References: <1232060306.42745.18.camel@hood.oook.cz> Message-ID: <20090119195426.GG9406@atarininja.org> On Thu, Jan 15, 2009 at 11:58:26PM +0100, Pav Lucistnik wrote: [...] > > cc: /usr/local/lib/perl5/5.8.9/mach/auto/DynaLoader/DynaLoader.a: No such file or directory > > gmake[2]: *** [eperl] Error 1 > > gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p3_eperl' > > gmake[1]: *** [all] Error 1 > > gmake[1]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend' > > gmake: *** [all] Error 1 > > *** Error code 2 > > > > Stop in /a/ports/www/wml. > > ================================================================ > > build of /usr/ports/www/wml ended at Thu Jan 15 03:02:29 UTC 2009 The attached patch fixes this problem and has been tested on my tinderbox to build correctly. Rodrigo, can you please verify that this does not cause any run-time regressions and approve it for commit? It makes the check for the dynamic loader support correct (it's gone in perl 5.8.9) and removes the built-in GD support (there was a build failure in this after you fix the dynamic loader issue). Thanks! -- WXS From sem at FreeBSD.org Tue Jan 20 06:34:32 2009 From: sem at FreeBSD.org (Sergey Matveychuk) Date: Tue Jan 20 06:34:39 2009 Subject: [Fwd: wml-2.0.12,1 failed on amd64 6] In-Reply-To: <20090119195837.GH9406@atarininja.org> References: <1232060306.42745.18.camel@hood.oook.cz> <20090119195426.GG9406@atarininja.org> <20090119195837.GH9406@atarininja.org> Message-ID: <4975D80A.8010902@FreeBSD.org> Could you fill a PR for this? Your attachment is dropped. Wesley Shields wrote: > On Mon, Jan 19, 2009 at 02:54:26PM -0500, Wesley Shields wrote: >> On Thu, Jan 15, 2009 at 11:58:26PM +0100, Pav Lucistnik wrote: >> >> [...] >> >>>> cc: /usr/local/lib/perl5/5.8.9/mach/auto/DynaLoader/DynaLoader.a: No such file or directory >>>> gmake[2]: *** [eperl] Error 1 >>>> gmake[2]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend/p3_eperl' >>>> gmake[1]: *** [all] Error 1 >>>> gmake[1]: Leaving directory `/work/a/ports/www/wml/work/wml-2.0.12/wml_backend' >>>> gmake: *** [all] Error 1 >>>> *** Error code 2 >>>> >>>> Stop in /a/ports/www/wml. >>>> ================================================================ >>>> build of /usr/ports/www/wml ended at Thu Jan 15 03:02:29 UTC 2009 >> The attached patch fixes this problem and has been tested on my >> tinderbox to build correctly. Rodrigo, can you please verify that this >> does not cause any run-time regressions and approve it for commit? >> >> It makes the check for the dynamic loader support correct (it's gone in >> perl 5.8.9) and removes the built-in GD support (there was a build >> failure in this after you fix the dynamic loader issue). >> >> Thanks! >> >> -- WXS > > Here's the attachment... > > -- WXS > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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" -- Dixi. Sem. From wxs at FreeBSD.org Tue Jan 20 13:02:13 2009 From: wxs at FreeBSD.org (Wesley Shields) Date: Tue Jan 20 13:02:19 2009 Subject: [Fwd: wml-2.0.12,1 failed on amd64 6] In-Reply-To: <4975D80A.8010902@FreeBSD.org> References: <1232060306.42745.18.camel@hood.oook.cz> <20090119195426.GG9406@atarininja.org> <20090119195837.GH9406@atarininja.org> <4975D80A.8010902@FreeBSD.org> Message-ID: <20090120210327.GC46918@atarininja.org> On Tue, Jan 20, 2009 at 04:56:26PM +0300, Sergey Matveychuk wrote: > Could you fill a PR for this? > Your attachment is dropped. While the patch is a good start to getting this port to work it's not complete yet. Unfortunately I don't have the time to work on this right now so I'll be marking it as broken until the maintainer can get it working again. -- WXS From edwin at FreeBSD.org Wed Jan 21 14:20:13 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Wed Jan 21 14:20:19 2009 Subject: ports/130842: [PATCH] devel/p5-Test-Harness: install prove script without conflict with core perl Message-ID: <200901212220.n0LMKC0J054826@freefall.freebsd.org> Synopsis: [PATCH] devel/p5-Test-Harness: install prove script without conflict with core perl Responsible-Changed-From-To: freebsd-ports-bugs->perl Responsible-Changed-By: edwin Responsible-Changed-When: Wed Jan 21 22:20:12 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=130842 From vovkasm at gmail.com Wed Jan 21 14:35:20 2009 From: vovkasm at gmail.com (Vladimir Timofeev) Date: Wed Jan 21 14:35:26 2009 Subject: [PATCH] devel/p5-Test-Harness: install prove script without conflict with core perl Message-ID: <200901212217.n0LMHGMj005108@zoo.rambler.ru> >Submitter-Id: current-users >Originator: Vladimir Timofeev >Organization: >Confidential: no >Synopsis: [PATCH] devel/p5-Test-Harness: install prove script without conflict with core perl >Severity: non-critical >Priority: low >Category: ports >Class: change-request >Release: FreeBSD 6.2-RELEASE-p1 amd64 >Environment: System: FreeBSD zoo.rambler.ru 6.2-RELEASE-p1 FreeBSD 6.2-RELEASE-p1 #1: Thu Feb 15 17:00:27 MSK 2007 >Description: This patch install bin/prove script as bin/p5prove for perl-5.8 and bin/prove for older perls. This allow to us using new prove's functions, for ex. colorized output, and saved states Idea from devel/p5-Module-CoreList. Port maintainer (perl@FreeBSD.org) is cc'd. Generated with FreeBSD Port Tools 0.77 >How-To-Repeat: >Fix: --- p5-Test-Harness-3.14_2.patch begins here --- Index: Makefile =================================================================== RCS file: /home/ncvs/ports/devel/p5-Test-Harness/Makefile,v retrieving revision 1.37 diff -u -r1.37 Makefile --- Makefile 15 Jan 2009 12:07:14 -0000 1.37 +++ Makefile 21 Jan 2009 22:07:19 -0000 @@ -7,7 +7,7 @@ PORTNAME= Test-Harness PORTVERSION= 3.14 -PORTREVISION= 1 +PORTREVISION= 2 CATEGORIES= devel perl5 MASTER_SITES= CPAN PKGNAMEPREFIX= p5- @@ -17,7 +17,6 @@ PERL_CONFIGURE= yes -MAN1= prove.1 MAN3= App::Prove.3 \ App::Prove::State.3 \ App::Prove::State::Result.3 \ @@ -62,21 +61,18 @@ .include .if ${PERL_LEVEL} >= 500800 -.undef MAN1 -PLIST_SUB+= PL_FILES="@comment " +PLIST_SUB= P5_PREFIX="p5" +MAN1= p5prove.1 pre-patch: - @${PERL} -pi -e "s,'bin/prove',," ${WRKSRC}/Makefile.PL + @${MV} ${WRKSRC}/bin/prove ${WRKSRC}/bin/p5prove + @${PERL} -pi -e "s,^bin/prove$$,bin/p5prove," ${WRKSRC}/MANIFEST + @${PERL} -pi -e "s,'bin/prove','bin/p5prove'," ${WRKSRC}/Makefile.PL .else -PLIST_SUB+= PL_FILES="" +MAN1= prove.1 +PLIST_SUB= P5_PREFIX="" .endif post-patch: @${REINPLACE_CMD} -e '/INSTALLDIRS/d' ${WRKSRC}/${CONFIGURE_SCRIPT} -post-configure: -.if ${PERL_LEVEL} >= 500800 - @${REINPLACE_CMD} -E -e '/(DESTINSTALLSITEMAN1DIR|DESTINSTALLSCRIPT)/d' \ - ${WRKSRC}/${MAKEFILE} -.endif - .include Index: pkg-plist =================================================================== RCS file: /home/ncvs/ports/devel/p5-Test-Harness/pkg-plist,v retrieving revision 1.16 diff -u -r1.16 pkg-plist --- pkg-plist 23 Sep 2008 12:18:49 -0000 1.16 +++ pkg-plist 21 Jan 2009 22:07:19 -0000 @@ -1,4 +1,4 @@ -%%PL_FILES%%bin/prove +bin/%%P5_PREFIX%%prove %%SITE_PERL%%/App/Prove.pm %%SITE_PERL%%/App/Prove/State.pm %%SITE_PERL%%/App/Prove/State/Result.pm --- p5-Test-Harness-3.14_2.patch ends here --- From rodrigo at bebik.net Thu Jan 22 17:16:23 2009 From: rodrigo at bebik.net (Rodrigo OSORIO (ros)) Date: Thu Jan 22 17:16:29 2009 Subject: In-Reply-To: <20090120210327.GC46918@atarininja.org> References: <1232060306.42745.18.camel@hood.oook.cz> <20090119195426.GG9406@atarininja.org> <20090119195837.GH9406@atarininja.org> <4975D80A.8010902@FreeBSD.org> <20090120210327.GC46918@atarininja.org> Message-ID: <20090123005719.GA45059@hodja.bebik.net> Hi, I work the past days on wml and found the reason the port fail. That's the move from Perl 5.8.8 to 5.8.9 who remove some files who affect wml. So, after a long lookup in the port makefiles I found some minimal changes we can do to run WML with the new perl version, half part comming from the patch sent by WXS. After the first version failure, I want to take more time to test my changes in different installs and architectures. - rodrigo On 20/01/09 16:03 -0500, Wesley Shields wrote: > On Tue, Jan 20, 2009 at 04:56:26PM +0300, Sergey Matveychuk wrote: > > Could you fill a PR for this? > > Your attachment is dropped. > > While the patch is a good start to getting this port to work it's not > complete yet. Unfortunately I don't have the time to work on this right > now so I'll be marking it as broken until the maintainer can get it > working again. > > -- WXS From wxs at FreeBSD.org Thu Jan 22 17:59:25 2009 From: wxs at FreeBSD.org (Wesley Shields) Date: Thu Jan 22 17:59:31 2009 Subject: In-Reply-To: <20090123005719.GA45059@hodja.bebik.net> References: <1232060306.42745.18.camel@hood.oook.cz> <20090119195426.GG9406@atarininja.org> <20090119195837.GH9406@atarininja.org> <4975D80A.8010902@FreeBSD.org> <20090120210327.GC46918@atarininja.org> <20090123005719.GA45059@hodja.bebik.net> Message-ID: <20090123020043.GA94145@atarininja.org> On Fri, Jan 23, 2009 at 01:57:19AM +0100, Rodrigo OSORIO (ros) wrote: > Hi, > > I work the past days on wml and found the reason the port fail. > That's the move from Perl 5.8.8 to 5.8.9 who remove some files > who affect wml. So, after a long lookup in the port makefiles > I found some minimal changes we can do to run WML with the new > perl version, half part comming from the patch sent by WXS. > > After the first version failure, I want to take more time to > test my changes in different installs and architectures. Excellent! Please send me the patch when you have tested it and I'll get the port updated. Thank you for looking into this. -- WXS From kris at FreeBSD.org Sat Jan 24 02:07:54 2009 From: kris at FreeBSD.org (Kris Kennaway) Date: Sat Jan 24 02:08:00 2009 Subject: Status of perl 5.10 Message-ID: <497AE877.1050103@FreeBSD.org> Hi guys, Can someone give us an update on what is the status of preparation for importing perl 5.10? Who is working on it; what are the remaining obstacles; what can we do in future to avoid the delays? Without pointing fingers at individuals, it has become quite a disgrace to us as a project that we still do not have this in the ports tree after more than a year, and we'd like to determine how we can fix this ASAP. Thanks, Kris, for portmgr From estrabd at gmail.com Sat Jan 24 05:35:50 2009 From: estrabd at gmail.com (B. Estrade) Date: Sat Jan 24 05:35:56 2009 Subject: Status of perl 5.10 In-Reply-To: <497AE877.1050103@FreeBSD.org> References: <497AE877.1050103@FreeBSD.org> Message-ID: <20090124131813.GF8987@bc3.lsu.edu> On Sat, Jan 24, 2009 at 10:07:51AM +0000, Kris Kennaway wrote: > Hi guys, > > Can someone give us an update on what is the status of preparation for > importing perl 5.10? Who is working on it; what are the remaining > obstacles; what can we do in future to avoid the delays? > > Without pointing fingers at individuals, it has become quite a disgrace > to us as a project that we still do not have this in the ports tree > after more than a year, and we'd like to determine how we can fix this ASAP. It looks like 5.8 was recently updated to 5.8.9. As a big time Perl user and list lurker, I can say that in general there seem to be very few people clamoring for 5.10. I'm not saying that it shouldn't be available, but since it is meant to be more of a path to Perl 6 rather than a maintenance release of the current Perl standard version (i.e., 5.8), I don't think it is quite the disgrace you make it out to be. Parrot is also not /that/ out of date, though the latest current release is 0.9.0 where as the one in Ports is 0.8.2. I regularly smoke test Parrot on FreeBSD 7 using the head of their repo, and everything usually works out of the box anyway. Something important to actually be following is the continued progress of Perl6 (Raduko) and the current efforts that are underway to move it from parrot/languages to its own repo trunk. With all of that said, and since I am pretty aware of the state of Perl and its ilk at any given point in time, I'd be happy to assist whomever looks over Perl and/or Parrot as long as some handholding and patience is abundant in the beginning. Cheers, Brett > > Thanks, > > Kris, for portmgr > _______________________________________________ > 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 kris at FreeBSD.org Sat Jan 24 05:45:27 2009 From: kris at FreeBSD.org (Kris Kennaway) Date: Sat Jan 24 05:45:34 2009 Subject: Status of perl 5.10 In-Reply-To: <20090124131813.GF8987@bc3.lsu.edu> References: <497AE877.1050103@FreeBSD.org> <20090124131813.GF8987@bc3.lsu.edu> Message-ID: <497B1B74.1060300@FreeBSD.org> B. Estrade wrote: > On Sat, Jan 24, 2009 at 10:07:51AM +0000, Kris Kennaway wrote: >> Hi guys, >> >> Can someone give us an update on what is the status of preparation for >> importing perl 5.10? Who is working on it; what are the remaining >> obstacles; what can we do in future to avoid the delays? >> >> Without pointing fingers at individuals, it has become quite a disgrace >> to us as a project that we still do not have this in the ports tree >> after more than a year, and we'd like to determine how we can fix this ASAP. > > It looks like 5.8 was recently updated to 5.8.9. As a big time Perl > user and list lurker, I can say that in general there seem to be very > few people clamoring for 5.10. I'm not saying that it shouldn't be > available, but since it is meant to be more of a path to Perl 6 rather > than a maintenance release of the current Perl standard version (i.e., > 5.8), I don't think it is quite the disgrace you make it out to be. It does come up fairly often on the mailing lists I read, and given that I know there were plans last year for working on the import, something clearly changed or went wrong with those plans. I agree that continuing to keep up with future development is also important. Thanks for your offer of help, hopefully the perl@freebsd.org community will be able to take advantage of it. Kris > > Parrot is also not /that/ out of date, though the latest current > release is 0.9.0 where as the one in Ports is 0.8.2. I regularly smoke > test Parrot on FreeBSD 7 using the head of their repo, and everything > usually works out of the box anyway. > > Something important to actually be following is the continued progress > of Perl6 (Raduko) and the current efforts that are underway to move it > from parrot/languages to its own repo trunk. > > With all of that said, and since I am pretty aware of the state of > Perl and its ilk at any given point in time, I'd be happy to assist > whomever looks over Perl and/or Parrot as long as some handholding and > patience is abundant in the beginning. > > Cheers, > Brett > >> Thanks, >> >> Kris, for portmgr >> _______________________________________________ >> 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 lawrence.auster at att.net Sun Jan 25 07:47:05 2009 From: lawrence.auster at att.net (Lawrence Auster) Date: Sun Jan 25 07:48:07 2009 Subject: Why are the Zionist leaders in Israel so happy about the new President? Message-ID: <20090125151635.LENK2046.cdptpa-omta04.mail.rr.com@2ao1z> Why is the President of Israel, the terrorist who just oversaw the Zionist mass murder and maiming of thousands of Palestinians so happy that Obama is President of the USA? by David Duke Read the excerpt from the Israeli News about how President Perez and Israel think that Obama’s becoming U.S. President is great day for Israel. "Israel’s President Shimon Peres ecstatic over the election of Obama" Ronen Medzini Israel News Jan. 21 “Today is a great day not only for the United States of America, but for the entire world,” President Shimon Peres wrote in a letter addressed to Barack Obama on the day of his inauguration as president of the United States. “Obama was elected by the United States, but as a matter of fact, he was chosen by the whole of humankind,” Why is Peres so ecstatic? Why shouldn’t he be, he knows that Obama is completely in the grip of the extremist Jewish Zionists in America, and he knows that the greater Obama’s popularity and idol worship, the more Obama can do for the International Zionist Cause. Any thinking and caring human being who realizes that the Zionist-controlled American foreign policy has been a disaster for the robbed and murdered people of Palestine, Lebanon, Iraq and a catastrophe for the 50,000 American wounded in Iraq and Afghanistan, as well as an economic catastrophe for the hardworking Americans who pay trillions to finance these wars for Israel — must wake up the fact that supporting Obama and increasing his popularity will only aid Zionist terrorism, war, and their murder and oppression of the Palestinians. It will also hasten the economic suffering of billions of people around the world as his popularity enables him to more easily aid the Zionist International Bankers steal the wealth of the United States, Europe and the world. Obama is totally in the bloodstained and green ink- stained hands of the Zionists. The hard truth is that the more good will and support Obama has also gives more power to support the Zionist agenda! Mark my words. The Obama Presidency will be disaster for America and for the world. Obama was put into office by the Zionists. His top two cohorts for years have been the radical Jews David Axelrod and Rahm Emmanuel. Both have long records of radical Zionism and have been attack dogs against anyone perceived as having the slightest opposition to Israel. One such victim was Sen. Charles Percy, who both men worked to defeat and destroy because he dared to only be 99 percent rather than 100 percent pro-Israel. Rahm Emmanuel, a dual citizen of Israel who went to fight for Israel, he has a long pedigree of Jewish extremism. His father served in the Irgun Terrorist Gang and he himself is named after an Irgun terrorist. Zionist leaders in Chicago actually call Obama “the first Jewish President” and boast that Jews were key players in Obama’s every step up the ladder to President. from the very earliest days, extremist Jews were the largest contributors to his campaign. In the beginning of his Presidential bid, three Hollywood Jews that constantly make movies about Jewish suffering, but never about the Zionist terrorism and theft against the Palestinian people, Steven Spielberg, David Geffen, and Jeffrey Katzenberg raised 1.2 million for Obama in a single Hollywood party. By the time Obama’s campaign was in full swing, he had huge support from the criminal Zionist International Banking firms such as Goldman Sachs and Lehman brothers. Goldman Sachs was Obama’s biggest single contributor, and his vast war chest came not from American manufacturing firms like GM or even American oil companies, (not one was in his top twenty) it was overwhelmingly dominated by Zionist international bankers, the same ones whose thievery and fraud are giving the world this economic depression. For those looking for meaningful social and political change, do you really think it will come from this man who has already been bought heart, head and soul by the most powerful czars of the international financial establishment and the biggest globalists in the world? I know that many are desperate for change, so desperate that you want to believe anything. But in the face of these facts can’t you see that Obama will be even more dangerous to freedom and justice than even George Bush and his band of Neocons were. What better way to wipe out George Bush’s hated legacy and make the world believe that America has really changed than with the election of Obama. But, all the real Zionist power, Zionist media power, and Zionist financial power in America is still in place, even stronger than ever. Many Americans and others around the world who want to do good are now telling us how wonderful Obama will be as president. What a great change it will be from the old policies. This is because of the Zionist-Controlled media hype, promoting Obama. The fact is that these poor sods are ignorantly helping the radical Zionist agenda in Israel and around the world. Every day that you don’t help expose Obama for the Zionist servant that he actually is, his popularity will be a greater danger to peace and freedom. If the Zionist terrorist Shimon Perez is happy about the coronation of Obama, then why in the hell should you be? –David Duke Source : http://www.davidduke.com/general/7303_7303.html ------------------------------------- You or someone using your email adress is currently subscribed to the Lawrence Auster Newletter. If you wish to unsubscribe from our mailing list, please let us know by calling to 1 212 865 1284 Thanks, Lawrence Auster, 238 W 101 St Apt. 3B New York, NY 10025 Contact: lawrence.auster@att.net ------------------------------------- From pgollucci at p6m7g8.com Sun Jan 25 13:32:43 2009 From: pgollucci at p6m7g8.com (Philip M. Gollucci) Date: Sun Jan 25 13:32:50 2009 Subject: Status of perl 5.10 In-Reply-To: <497B1B74.1060300@FreeBSD.org> References: <497AE877.1050103@FreeBSD.org> <20090124131813.GF8987@bc3.lsu.edu> <497B1B74.1060300@FreeBSD.org> Message-ID: <497CD7D6.5000403@p6m7g8.com> >>> Can someone give us an update on what is the status of preparation >>> for importing perl 5.10? Who is working on it; what are the >>> remaining obstacles; what can we do in future to avoid the delays? w/ mod_perl hat (and p5p-), I think the largest obstacle really is setting CONFLICTS and getting -exp runs. I mean perl 5.10 compiles on freebsd. Creating the port can be done fairly quickly. leaving lang/perl5.8 as the default. If portmgr@ wants to do an -exp run, I take a whack at it today. Its going to react fairly similiar to the 5.8.9 import, the only differnce is *MORE* modules are now dual life and in core. Which means more ugly .if PERL_VER >. -- ------------------------------------------------------------------------ 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollucci@p6m7g8.com) c: 703.336.9354 Consultant - P6M7G8 Inc. http://p6m7g8.net Senior Sys Admin - RideCharge, Inc. http://ridecharge.com Contractor - PositiveEnergyUSA http://positiveenergyusa.com ASF Member - Apache Software Foundation http://apache.org FreeBSD Committer - FreeBSD Foundation http://freebsd.org Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. From bugmaster at FreeBSD.org Mon Jan 26 03:08:07 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 26 03:09:50 2009 Subject: Current problem reports assigned to perl@FreeBSD.org Message-ID: <200901261108.n0QB83Bf025554@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/130842 perl [PATCH] devel/p5-Test-Harness: install prove script wi 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 mat at mat.cc Tue Jan 27 02:03:40 2009 From: mat at mat.cc (Mathieu Arnold) Date: Tue Jan 27 02:03:47 2009 Subject: Status of perl 5.10 In-Reply-To: <497CD7D6.5000403@p6m7g8.com> References: <497AE877.1050103@FreeBSD.org> <20090124131813.GF8987@bc3.lsu.edu> <497B1B74.1060300@FreeBSD.org> <497CD7D6.5000403@p6m7g8.com> Message-ID: <71920C28EEEA8FADF465A072@ATuin.in.mat.cc> +--On 25 janvier 2009 16:21:26 -0500 "Philip M. Gollucci" wrote: |>>> Can someone give us an update on what is the status of preparation |>>> for importing perl 5.10? Who is working on it; what are the |>>> remaining obstacles; what can we do in future to avoid the delays? | w/ mod_perl hat (and p5p-), I think the largest obstacle really is | setting CONFLICTS | and getting -exp runs. | | I mean perl 5.10 compiles on freebsd. Creating the port can be done | fairly quickly. | leaving lang/perl5.8 as the default. If portmgr@ wants to do an -exp | run, I take a whack at it today. | | Its going to react fairly similiar to the 5.8.9 import, the only | differnce is *MORE* | modules are now dual life and in core. Which means more ugly .if | PERL_VER >. I think you all should ask the perl maintainer, that is, which is, if I'm not mistaken, skv@ who took over from tobez@ so that he could do the 5.10 import. -- Mathieu Arnold From guru at unixarea.de Tue Jan 27 05:27:05 2009 From: guru at unixarea.de (Matthias Apitz) Date: Tue Jan 27 05:27:12 2009 Subject: errors on pkg_create for p5-* ports Message-ID: <20090127131500.GA22386@rebelion.Sisis.de> Hello, After installing 7.1R ports (portupgraded) I'm trying to create packages of all the ~1000 installed packages; 8 packages, all belonging to bsdpan-* packages from ports/www/p5-* (exact list below) are giving errors; what could I do? the command has been always 'pkg_create -Rnb xxxxx'; thx matthias bsdpan-URI-1.37: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/URI.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::Escape.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::Heuristic.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::QueryParam.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::Split.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::URL.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::WithBase.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::data.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::file.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::ldap.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-Compress-Raw-Zlib-2.015: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/Compress::Raw::Zlib.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-IO-Compress-Base-2.015: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/File::GlobMapper.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Compress::Base.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::AnyUncompress.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::Base.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-IO-Compress-Zlib-2.015: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Compress::Deflate.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Compress::Gzip.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Compress::RawDeflate.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Compress::Zip.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::AnyInflate.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::Gunzip.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::Inflate.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::RawInflate.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::Unzip.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-Compress-Zlib-2.015: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/Compress::Zlib.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-HTML-Tagset-3.20: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::Tagset.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-HTML-Parser-3.59: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::Entities.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::Filter.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::HeadParser.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::LinkExtor.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::Parser.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::PullParser.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::TokeParser.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-libwww-perl-5.823: ... tar: Removing leading '/' from member names bsdpan-XML-Parser-2.36: ... tar: Removing leading '/' from member names -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ SPAMer of the year: Subject: Alle Software ist Deutsche Sprachen >From: -40 % die Neujahrsaktion From guru at unixarea.de Tue Jan 27 06:14:54 2009 From: guru at unixarea.de (Matthias Apitz) Date: Tue Jan 27 06:15:00 2009 Subject: errors on pkg_create for p5-* ports In-Reply-To: <20090127135924.GA28672@heechee.tobez.org> References: <20090127131500.GA22386@rebelion.Sisis.de> <20090127135924.GA28672@heechee.tobez.org> Message-ID: <20090127141452.GA24178@rebelion.Sisis.de> El d?a Tuesday, January 27, 2009 a las 02:59:24PM +0100, Anton Berezin escribi?: > Matthias, > > On Tue, Jan 27, 2009 at 02:15:00PM +0100, Matthias Apitz wrote: > > > After installing 7.1R ports (portupgraded) I'm trying to create packages > > of all the ~1000 installed packages; 8 packages, all belonging to > > bsdpan-* packages from ports/www/p5-* (exact list below) are giving > > errors; what could I do? > > Something is very interesting here. If you used ports to install those > modules, there will be no bsdpan packages, there will be p5 packages. > > If you installed modules directly from CPAN, there will be bsdpan packages. > > So before trying to figure out the problem with pkg_create, it would be > useful to figure out how the modules in question were installed, and if the > answer is "directly from CPAN", why the "real" ports were not used for the > task. Your question remembers me what I've posted on January 18 to the kde-freebsd list: > Hello, > > The building of the KDE 3.5.10 master port x11/kde3 fails in > misc/shared-mime-info with: > > # cd /usr/ports/X11/kde3 > # make install BATCH=yes > > .... > checking for perl... /usr/bin/perl > checking for XML::Parser... configure: error: XML::Parser perl module > is > required for intltool > ===> Script "configure" failed unexpectedly. > > (this is with portsnap fetch+extract and portupgrade) > > I did by hand: > > # perl -MCPAN -e shell > at cpan> prompt type in: > install XML::Parser > > which made it happy; > > is this a known issue? (Cc: maintainer gnome@FreeBSD.org) Well this explains why there is stuff directly from CPAN and why the "real" has not been used; any idea how to avoid this CPAN access? > > Another interesting question is whether a previous version of lang/perl5.8 > (5.8.8) was installed at some point, and whether perl-after-upgrade script > was run after the upgrade to 5.8.9 (as per ports/UPDATING entry). I don't think so that there have been 5.8.8 installed; I installed the base system, portupgraded and went directly to the KDE3 master port which caused the above error; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ SPAMer of the year: Subject: Alle Software ist Deutsche Sprachen >From: -40 % die Neujahrsaktion From tobez at tobez.org Tue Jan 27 06:15:14 2009 From: tobez at tobez.org (Anton Berezin) Date: Tue Jan 27 06:15:21 2009 Subject: errors on pkg_create for p5-* ports In-Reply-To: <20090127131500.GA22386@rebelion.Sisis.de> References: <20090127131500.GA22386@rebelion.Sisis.de> Message-ID: <20090127135924.GA28672@heechee.tobez.org> Matthias, On Tue, Jan 27, 2009 at 02:15:00PM +0100, Matthias Apitz wrote: > After installing 7.1R ports (portupgraded) I'm trying to create packages > of all the ~1000 installed packages; 8 packages, all belonging to > bsdpan-* packages from ports/www/p5-* (exact list below) are giving > errors; what could I do? Something is very interesting here. If you used ports to install those modules, there will be no bsdpan packages, there will be p5 packages. If you installed modules directly from CPAN, there will be bsdpan packages. So before trying to figure out the problem with pkg_create, it would be useful to figure out how the modules in question were installed, and if the answer is "directly from CPAN", why the "real" ports were not used for the task. Another interesting question is whether a previous version of lang/perl5.8 (5.8.8) was installed at some point, and whether perl-after-upgrade script was run after the upgrade to 5.8.9 (as per ports/UPDATING entry). \Anton. -- There is no beauty in entropy. -- Eliezer Yudkowsky From tobez at tobez.org Tue Jan 27 06:39:33 2009 From: tobez at tobez.org (Anton Berezin) Date: Tue Jan 27 06:39:46 2009 Subject: errors on pkg_create for p5-* ports In-Reply-To: <20090127141452.GA24178@rebelion.Sisis.de> References: <20090127131500.GA22386@rebelion.Sisis.de> <20090127135924.GA28672@heechee.tobez.org> <20090127141452.GA24178@rebelion.Sisis.de> Message-ID: <20090127143931.GB28672@heechee.tobez.org> On Tue, Jan 27, 2009 at 03:14:52PM +0100, Matthias Apitz wrote: > El d?a Tuesday, January 27, 2009 a las 02:59:24PM +0100, Anton Berezin escribi?: > > > Matthias, > > > > On Tue, Jan 27, 2009 at 02:15:00PM +0100, Matthias Apitz wrote: > > > > > After installing 7.1R ports (portupgraded) I'm trying to create packages > > > of all the ~1000 installed packages; 8 packages, all belonging to > > > bsdpan-* packages from ports/www/p5-* (exact list below) are giving > > > errors; what could I do? > > > > Something is very interesting here. If you used ports to install those > > modules, there will be no bsdpan packages, there will be p5 packages. > > > > If you installed modules directly from CPAN, there will be bsdpan packages. > > > > So before trying to figure out the problem with pkg_create, it would be > > useful to figure out how the modules in question were installed, and if the > > answer is "directly from CPAN", why the "real" ports were not used for the > > task. > > Your question remembers me what I've posted on January 18 to the > kde-freebsd list: > > > Hello, > > > > The building of the KDE 3.5.10 master port x11/kde3 fails in > > misc/shared-mime-info with: > > > > # cd /usr/ports/X11/kde3 > > # make install BATCH=yes > > > > .... > > checking for perl... /usr/bin/perl > > checking for XML::Parser... configure: error: XML::Parser perl module > > is > > required for intltool > > ===> Script "configure" failed unexpectedly. > > > > (this is with portsnap fetch+extract and portupgrade) > > > > I did by hand: > > > > # perl -MCPAN -e shell > > at cpan> prompt type in: > > install XML::Parser > > > > which made it happy; > > > > is this a known issue? (Cc: maintainer gnome@FreeBSD.org) > Well this explains why there is stuff directly from CPAN and why the > "real" has not been used; > any idea how to avoid this CPAN access? Well, there is a textproc/p5-XML-Parser port. It should be a dependency of the relevant port required by X11/kde3 (it is not entirely clear from your mail which particular port has failed its configuration change, the "...." above might have contained some useful information). At any rate, this must be fixed unless it was fixed already. I would not know without knowing what port has failed. As for the immediate problem at hand, could you send me (privately, there is no reason to involve that many lists) the output of ls -l /var/db/pkg As well as cat /var/db/pkg/bsdpan-URI*/+CONTENTS As well as ls -l /usr/local/lib/perl5/5.8.9/man/man3/ As well as cat /etc/make.conf As well as cat /etc/manpath.config That should get us started. In theory modules installed directly from CPAN should have their files registered correctly with the package system. It would be very interesting to find out what went wrong. If you don't care about finding out what went wrong and why, and you are sure that the only thing you installed directly from CPAN is XML-Parser (with its dependencies), then an easy way out is to rm -rf /var/db/pkg/bsdpan* and to go to /usr/ports/textproc/p5-XML-Parser and make install clean that. In this case you would not care about creating packages from bsdpan-* things, and you should be in the clear when you create packages from p5-* things. :-) > > Another interesting question is whether a previous version of lang/perl5.8 > > (5.8.8) was installed at some point, and whether perl-after-upgrade script > > was run after the upgrade to 5.8.9 (as per ports/UPDATING entry). > > I don't think so that there have been 5.8.8 installed; I installed the > base system, portupgraded and went directly to the KDE3 master port > which caused the above error; Ok. Cheers, \Anton. -- There is no beauty in entropy. -- Eliezer Yudkowsky From tobez at tobez.org Tue Jan 27 14:36:36 2009 From: tobez at tobez.org (Anton Berezin) Date: Tue Jan 27 14:37:09 2009 Subject: errors on pkg_create for p5-* ports In-Reply-To: <20090127141452.GA24178@rebelion.Sisis.de> References: <20090127131500.GA22386@rebelion.Sisis.de> <20090127135924.GA28672@heechee.tobez.org> <20090127141452.GA24178@rebelion.Sisis.de> Message-ID: <20090127143931.GB28672@heechee.tobez.org> On Tue, Jan 27, 2009 at 03:14:52PM +0100, Matthias Apitz wrote: > El d?a Tuesday, January 27, 2009 a las 02:59:24PM +0100, Anton Berezin escribi?: > > > Matthias, > > > > On Tue, Jan 27, 2009 at 02:15:00PM +0100, Matthias Apitz wrote: > > > > > After installing 7.1R ports (portupgraded) I'm trying to create packages > > > of all the ~1000 installed packages; 8 packages, all belonging to > > > bsdpan-* packages from ports/www/p5-* (exact list below) are giving > > > errors; what could I do? > > > > Something is very interesting here. If you used ports to install those > > modules, there will be no bsdpan packages, there will be p5 packages. > > > > If you installed modules directly from CPAN, there will be bsdpan packages. > > > > So before trying to figure out the problem with pkg_create, it would be > > useful to figure out how the modules in question were installed, and if the > > answer is "directly from CPAN", why the "real" ports were not used for the > > task. > > Your question remembers me what I've posted on January 18 to the > kde-freebsd list: > > > Hello, > > > > The building of the KDE 3.5.10 master port x11/kde3 fails in > > misc/shared-mime-info with: > > > > # cd /usr/ports/X11/kde3 > > # make install BATCH=yes > > > > .... > > checking for perl... /usr/bin/perl > > checking for XML::Parser... configure: error: XML::Parser perl module > > is > > required for intltool > > ===> Script "configure" failed unexpectedly. > > > > (this is with portsnap fetch+extract and portupgrade) > > > > I did by hand: > > > > # perl -MCPAN -e shell > > at cpan> prompt type in: > > install XML::Parser > > > > which made it happy; > > > > is this a known issue? (Cc: maintainer gnome@FreeBSD.org) > Well this explains why there is stuff directly from CPAN and why the > "real" has not been used; > any idea how to avoid this CPAN access? Well, there is a textproc/p5-XML-Parser port. It should be a dependency of the relevant port required by X11/kde3 (it is not entirely clear from your mail which particular port has failed its configuration change, the "...." above might have contained some useful information). At any rate, this must be fixed unless it was fixed already. I would not know without knowing what port has failed. As for the immediate problem at hand, could you send me (privately, there is no reason to involve that many lists) the output of ls -l /var/db/pkg As well as cat /var/db/pkg/bsdpan-URI*/+CONTENTS As well as ls -l /usr/local/lib/perl5/5.8.9/man/man3/ As well as cat /etc/make.conf As well as cat /etc/manpath.config That should get us started. In theory modules installed directly from CPAN should have their files registered correctly with the package system. It would be very interesting to find out what went wrong. If you don't care about finding out what went wrong and why, and you are sure that the only thing you installed directly from CPAN is XML-Parser (with its dependencies), then an easy way out is to rm -rf /var/db/pkg/bsdpan* and to go to /usr/ports/textproc/p5-XML-Parser and make install clean that. In this case you would not care about creating packages from bsdpan-* things, and you should be in the clear when you create packages from p5-* things. :-) > > Another interesting question is whether a previous version of lang/perl5.8 > > (5.8.8) was installed at some point, and whether perl-after-upgrade script > > was run after the upgrade to 5.8.9 (as per ports/UPDATING entry). > > I don't think so that there have been 5.8.8 installed; I installed the > base system, portupgraded and went directly to the KDE3 master port > which caused the above error; Ok. Cheers, \Anton. -- There is no beauty in entropy. -- Eliezer Yudkowsky _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From guru at unixarea.de Tue Jan 27 14:36:40 2009 From: guru at unixarea.de (Matthias Apitz) Date: Tue Jan 27 14:37:59 2009 Subject: errors on pkg_create for p5-* ports Message-ID: <20090127131500.GA22386@rebelion.Sisis.de> Hello, After installing 7.1R ports (portupgraded) I'm trying to create packages of all the ~1000 installed packages; 8 packages, all belonging to bsdpan-* packages from ports/www/p5-* (exact list below) are giving errors; what could I do? the command has been always 'pkg_create -Rnb xxxxx'; thx matthias bsdpan-URI-1.37: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/URI.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::Escape.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::Heuristic.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::QueryParam.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::Split.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::URL.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::WithBase.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::data.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::file.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/URI::ldap.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-Compress-Raw-Zlib-2.015: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/Compress::Raw::Zlib.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-IO-Compress-Base-2.015: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/File::GlobMapper.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Compress::Base.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::AnyUncompress.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::Base.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-IO-Compress-Zlib-2.015: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Compress::Deflate.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Compress::Gzip.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Compress::RawDeflate.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Compress::Zip.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::AnyInflate.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::Gunzip.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::Inflate.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::RawInflate.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/IO::Uncompress::Unzip.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-Compress-Zlib-2.015: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/Compress::Zlib.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-HTML-Tagset-3.20: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::Tagset.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-HTML-Parser-3.59: ... tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::Entities.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::Filter.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::HeadParser.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::LinkExtor.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::Parser.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::PullParser.3: Cannot stat: No such file or directory tar: /usr/local/lib/perl5/5.8.9/man/man3/HTML::TokeParser.3: Cannot stat: No such file or directory tar: Removing leading '/' from member names tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 bsdpan-libwww-perl-5.823: ... tar: Removing leading '/' from member names bsdpan-XML-Parser-2.36: ... tar: Removing leading '/' from member names -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ SPAMer of the year: Subject: Alle Software ist Deutsche Sprachen >From: -40 % die Neujahrsaktion _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From guru at unixarea.de Tue Jan 27 14:36:46 2009 From: guru at unixarea.de (Matthias Apitz) Date: Tue Jan 27 14:38:37 2009 Subject: errors on pkg_create for p5-* ports In-Reply-To: <20090127135924.GA28672@heechee.tobez.org> References: <20090127131500.GA22386@rebelion.Sisis.de> <20090127135924.GA28672@heechee.tobez.org> Message-ID: <20090127141452.GA24178@rebelion.Sisis.de> El d?a Tuesday, January 27, 2009 a las 02:59:24PM +0100, Anton Berezin escribi?: > Matthias, > > On Tue, Jan 27, 2009 at 02:15:00PM +0100, Matthias Apitz wrote: > > > After installing 7.1R ports (portupgraded) I'm trying to create packages > > of all the ~1000 installed packages; 8 packages, all belonging to > > bsdpan-* packages from ports/www/p5-* (exact list below) are giving > > errors; what could I do? > > Something is very interesting here. If you used ports to install those > modules, there will be no bsdpan packages, there will be p5 packages. > > If you installed modules directly from CPAN, there will be bsdpan packages. > > So before trying to figure out the problem with pkg_create, it would be > useful to figure out how the modules in question were installed, and if the > answer is "directly from CPAN", why the "real" ports were not used for the > task. Your question remembers me what I've posted on January 18 to the kde-freebsd list: > Hello, > > The building of the KDE 3.5.10 master port x11/kde3 fails in > misc/shared-mime-info with: > > # cd /usr/ports/X11/kde3 > # make install BATCH=yes > > .... > checking for perl... /usr/bin/perl > checking for XML::Parser... configure: error: XML::Parser perl module > is > required for intltool > ===> Script "configure" failed unexpectedly. > > (this is with portsnap fetch+extract and portupgrade) > > I did by hand: > > # perl -MCPAN -e shell > at cpan> prompt type in: > install XML::Parser > > which made it happy; > > is this a known issue? (Cc: maintainer gnome@FreeBSD.org) Well this explains why there is stuff directly from CPAN and why the "real" has not been used; any idea how to avoid this CPAN access? > > Another interesting question is whether a previous version of lang/perl5.8 > (5.8.8) was installed at some point, and whether perl-after-upgrade script > was run after the upgrade to 5.8.9 (as per ports/UPDATING entry). I don't think so that there have been 5.8.8 installed; I installed the base system, portupgraded and went directly to the KDE3 master port which caused the above error; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ SPAMer of the year: Subject: Alle Software ist Deutsche Sprachen >From: -40 % die Neujahrsaktion _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From tobez at tobez.org Tue Jan 27 14:36:50 2009 From: tobez at tobez.org (Anton Berezin) Date: Tue Jan 27 14:38:53 2009 Subject: errors on pkg_create for p5-* ports In-Reply-To: <20090127131500.GA22386@rebelion.Sisis.de> References: <20090127131500.GA22386@rebelion.Sisis.de> Message-ID: <20090127135924.GA28672@heechee.tobez.org> Matthias, On Tue, Jan 27, 2009 at 02:15:00PM +0100, Matthias Apitz wrote: > After installing 7.1R ports (portupgraded) I'm trying to create packages > of all the ~1000 installed packages; 8 packages, all belonging to > bsdpan-* packages from ports/www/p5-* (exact list below) are giving > errors; what could I do? Something is very interesting here. If you used ports to install those modules, there will be no bsdpan packages, there will be p5 packages. If you installed modules directly from CPAN, there will be bsdpan packages. So before trying to figure out the problem with pkg_create, it would be useful to figure out how the modules in question were installed, and if the answer is "directly from CPAN", why the "real" ports were not used for the task. Another interesting question is whether a previous version of lang/perl5.8 (5.8.8) was installed at some point, and whether perl-after-upgrade script was run after the upgrade to 5.8.9 (as per ports/UPDATING entry). \Anton. -- There is no beauty in entropy. -- Eliezer Yudkowsky _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From William at futurecis.com Thu Jan 29 08:57:26 2009 From: William at futurecis.com (William Bentley) Date: Thu Jan 29 08:57:33 2009 Subject: Perl5.8 Won't Build Message-ID: <4981D9B8.3000505@futurecis.com> Hey All, Trying to build Perl5.8 and keep getting error messages. This is a new installation under 7.1Release. Already did a make clean and portsnap. Any ideas appreciated. Here is the ouput. .....snip....... Extracting Policy.sh (with variable substitutions) Extracting utils/Makefile (with variable substitutions) Extracting writemain (with variable substitutions) Extracting x2p/cflags (with variable substitutions) Extracting x2p/Makefile (with variable substitutions) Configure done. If you compile perl5 on a different machine or from a different object directory, copy the Policy.sh file from this object directory to the new one before you run Configure -- this will help you with most of the policy defaults. ===> Building for perl-5.8.9 make: cannot open makefile. *** Error code 2 Stop in /usr/ports/lang/perl5.8. *** Error code 1 Stop in /usr/ports/lang/perl5.8. From tobez at tobez.org Thu Jan 29 09:23:56 2009 From: tobez at tobez.org (Anton Berezin) Date: Thu Jan 29 09:24:03 2009 Subject: Perl5.8 Won't Build In-Reply-To: <4981D9B8.3000505@futurecis.com> References: <4981D9B8.3000505@futurecis.com> Message-ID: <20090129172354.GA50142@heechee.tobez.org> On Thu, Jan 29, 2009 at 11:30:48AM -0500, William Bentley wrote: > Hey All, > > Trying to build Perl5.8 and keep getting error messages. This is a > new installation under 7.1Release. Already did a make clean and > portsnap. Any ideas appreciated. Here is the ouput. > > .....snip....... ^^^^ here is the interesting part. > Extracting Policy.sh (with variable substitutions) > Extracting utils/Makefile (with variable substitutions) > Extracting writemain (with variable substitutions) > Extracting x2p/cflags (with variable substitutions) > Extracting x2p/Makefile (with variable substitutions) > Configure done. > > If you compile perl5 on a different machine or from a different object > directory, copy the Policy.sh file from this object directory to the > new one before you run Configure -- this will help you with most of > the policy defaults. > > ===> Building for perl-5.8.9 > make: cannot open makefile. > *** Error code 2 > > Stop in /usr/ports/lang/perl5.8. > *** Error code 1 > > Stop in /usr/ports/lang/perl5.8. Could you attach a complete output of the configure stage? \Anton. -- There is no beauty in entropy. -- Eliezer Yudkowsky From erwin at FreeBSD.org Thu Jan 29 09:42:27 2009 From: erwin at FreeBSD.org (erwin@FreeBSD.org) Date: Thu Jan 29 09:42:33 2009 Subject: ports/128941: devel/p5-IO-Tty: IO::Pty no longer working after upgrading to FreeBSD 6.4-PRERELEASE Message-ID: <200901291742.n0THgQFJ001227@freefall.freebsd.org> Synopsis: devel/p5-IO-Tty: IO::Pty no longer working after upgrading to FreeBSD 6.4-PRERELEASE Responsible-Changed-From-To: erwin->perl Responsible-Changed-By: erwin Responsible-Changed-When: Thu Jan 29 17:42:12 UTC 2009 Responsible-Changed-Why: Reassign. http://www.freebsd.org/cgi/query-pr.cgi?pr=128941 From William at futurecis.com Thu Jan 29 09:47:22 2009 From: William at futurecis.com (William Bentley) Date: Thu Jan 29 09:47:30 2009 Subject: Perl5.8 Won't Build In-Reply-To: <20090129172354.GA50142@heechee.tobez.org> References: <4981D9B8.3000505@futurecis.com> <20090129172354.GA50142@heechee.tobez.org> Message-ID: <4981EBAD.3010405@futurecis.com> Here it is: #make ===> Vulnerability check disabled, database not found ===> Found saved configuration for perl-5.8.9 ===> Extracting for perl-5.8.9 => MD5 Checksum OK for perl/perl-5.8.9.tar.bz2. => SHA256 Checksum OK for perl/perl-5.8.9.tar.bz2. => MD5 Checksum OK for perl/BSDPAN-5.8.9.tar.bz2. => SHA256 Checksum OK for perl/BSDPAN-5.8.9.tar.bz2. => MD5 Checksum OK for perl/defined-or-5.8.9.bz2. => SHA256 Checksum OK for perl/defined-or-5.8.9.bz2. ===> Patching for perl-5.8.9 ===> Applying distribution patches for perl-5.8.9 ===> Applying FreeBSD patches for perl-5.8.9 /usr/bin/sed -e 's|%%PREFIX%%|/usr/local|g;' -e 's|%%PERL_VER%%|5.8.9|g;' -e 's|%%PERL_VERSION%%|5.8.9|g;' -e 's|%%PERL_ARCH%%|mach|g;' -e 's|%%MAKE_CONF%%|/etc/make.conf|g;' /usr/ports/lang/perl5.8/files/use.perl > /usr/ports/lang/perl5.8/work/use.perl /usr/bin/sed -e 's|%%PERL%%|/usr/local/bin/perl|g;' /usr/ports/lang/perl5.8/files/perl-after-upgrade > /usr/ports/lang/perl5.8/work/perl-after-upgrade /bin/cp /usr/ports/lang/perl5.8/work/use.perl /usr/ports/lang/perl5.8/work/pkg-install /bin/cp /usr/ports/lang/perl5.8/work/use.perl /usr/ports/lang/perl5.8/work/pkg-deinstall /usr/bin/sed -i.bak -e 's|%%PTHREAD_LIBS%%||g;' -e 's|%%PTHREAD_CFLAGS%%||g;' /usr/ports/lang/perl5.8/work/perl-5.8.9/hints/freebsd.sh ===> Configuring for perl-5.8.9 First let's make sure your kit is complete. Checking... Locating common programs... Checking compatibility between /bin/echo and builtin echo (if any)... Symbolic links are supported. Checking how to test for symbolic links... You can test for symbolic links with 'test -h'. Good, your tr supports [:lower:] and [:upper:] to convert case. Using [:upper:] and [:lower:] to convert case. 3b1 catamount dynixptx i386 machten next_3 qnx sunos_4_0 unisysdynix aix convexos epix interix machten_2 next_3_0 rhapsody sunos_4_1 utekv aix_3 cxux esix4 irix_4 midnightbsd next_4 riscos super-ux uts aix_4 cygwin fps irix_5 mint nonstopux sco svr4 uwin altos486 darwin freebsd irix_6 mips openbsd sco_2_3_0 svr5 vmesa amigaos dcosx genix irix_6_0 mirbsd opus sco_2_3_1 ti1500 vos apollo dec_osf gnu irix_6_1 mpc os2 sco_2_3_2 titanos atheos dgux gnukfreebsd isc mpeix os390 sco_2_3_3 ultrix_4 aux_3 dos_djgpp gnuknetbsd isc_2 ncr_tower os400 sco_2_3_4 umips beos dragonfly greenhills linux netbsd posix-bc solaris_2 unicos bsdos dynix hpux lynxos newsos4 powerux stellar unicosmk Which of these apply, if any? [freebsd] ./hints/freebsd.sh: /usr/bin/objformat: not found Some users have reported that Configure halts when testing for the O_NONBLOCK symbol with a syntax error. This is apparently a sh error. Rerunning Configure with ksh apparently fixes the problem. Try ksh Configure [your options] Operating system name? [freebsd] Operating system version? [7.1-release] Installation prefix to use? (~name ok) [/usr/local] AFS does not seem to be running... What installation prefix should I use for installing files? (~name ok) [/usr/local] Build Perl for SOCKS? [n] Use the PerlIO abstraction layer? [y] Getting the current patchlevel... Build a threading Perl? [n] Build Perl for multiplicity? [n] Use which C compiler? [cc] Checking for GNU cc in disguise and/or its version number... Now, how can we feed standard input to your C preprocessor... Directories to use for library searches? [/usr/lib /usr/local/lib] What is the file extension used for shared libraries? [so] Try to use long doubles if available? [n] Checking for optional libraries... What libraries to use? [-lm -lcrypt -lutil] What optimizer/debugger flag should be used? [-O2 -fno-strict-aliasing -pipe] Any additional cc flags? [-DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include] Let me guess what the preprocessor flags are... Any additional ld flags (NOT including libraries)? [ -Wl,-E -L/usr/local/lib] Checking your choice of C compiler and flags for coherency... Computing filename position in cpp output for #include directives... found. Checking to see how big your integers are... Checking to see if you have long long... Checking to see how big your long longs are... found. Checking to see if you have int64_t... Checking which 64-bit integer type we could use... We could use 'long' for 64-bit integers. Try to use maximal 64-bit support, if available? [y] Checking to see how big your double precision numbers are... Checking to see if you have long double... Checking to see how big your long doubles are... What is your architecture name [amd64-freebsd] This architecture is naturally 64-bit, not changing architecture name. Perlio selected. Pathname where the public executables will reside? (~name ok) [/usr/local/bin] Use relocatable @INC? [n] Pathname where the private library files will reside? (~name ok) [/usr/local/lib/perl5/5.8.9] Where do you want to put the public architecture-dependent libraries? (~name ok) [/usr/local/lib/perl5/5.8.9/mach] Other username to test security of setuid scripts with? [none] I'll assume setuid scripts are *not* secure. Does your kernel have *secure* setuid scripts? [n] Do you want to do setuid/setgid emulation? [n] Installation prefix to use for add-on modules and utilities? (~name ok) [/usr/local] Pathname for the site-specific library files? (~name ok) [/usr/local/lib/perl5/site_perl/5.8.9] List of earlier versions to include in @INC? [none] NOT found. Checking to see how well your C compiler groks the void type... Good. It appears to support void to the level perl5 wants. Checking to see how big your pointers are... Do you wish to wrap malloc calls to protect against potential overflows? [y] Do you wish to attempt to use the malloc that comes with perl5? [y] Your system wants malloc to return 'void *', it would seem. Your system uses void free(), it would seem. Pathname for the site-specific architecture-dependent library files? (~name ok) [/usr/local/lib/perl5/site_perl/5.8.9/mach] Do you want to configure vendor-specific add-on directories? [n] Colon-separated list of additional directories for perl to search? [none] Checking out function prototypes... Install any extra modules (y or n)? [n] Directory for the main Perl5 html pages? (~name ok) [none] Directory for the Perl5 module html pages? (~name ok) [none] Do you want to install perl as /usr/bin/perl? [n] Checking for GNU C Library... Shall I use /usr/bin/nm to extract C symbols from the libraries? [n] NOT found. Checking for C++... dlopen() found. found. Do you wish to use dynamic loading? [y] Source file to use for dynamic loading [ext/DynaLoader/dl_dlopen.xs] Any special flags to pass to cc -c to compile shared library modules? [-DPIC -fPIC] What command should be used to create dynamic libraries? [cc] Any special flags to pass to cc to create a dynamically loaded library? [-shared -L/usr/local/lib] Any special flags to pass to cc to use dynamic linking? [none] Build a shared libperl.so (y/n) [y] What name do you want to give to the shared libperl? [libperl.so] Adding -Wl,-R/usr/local/lib/perl5/5.8.9/mach/CORE to the flags passed to cc so that the perl executable will find the installed shared libperl.so. System manual is in /usr/share/man/man1. Where do the main Perl5 manual pages (source) go? (~name ok) [/usr/local/man/man1] What suffix should be used for the main Perl5 man pages? [1] You can have filenames longer than 14 characters. Where do the perl5 library man pages (source) go? (~name ok) [/usr/local/lib/perl5/5.8.9/perl/man/man3] What suffix should be used for the perl5 library man pages? [3] Figuring out host name... Your host name appears to be "p1.futurecis.com". Right? [y] What is your domain name? [.futurecis.com] What is your e-mail address? [wbentley@p1.futurecis.com] Perl administrator e-mail address [wbentley@p1.futurecis.com] Do you want to install only the version-specific parts of perl? [n] What shall I put after the #! to start up perl ("none" to not use #!)? [/usr/local/bin/perl] Where do you keep publicly executable scripts? (~name ok) [/usr/local/bin] Pathname where the add-on public executables should be installed? (~name ok) [/usr/local/bin] Pathname where the site-specific html pages should be installed? (~name ok) [none] Pathname where the site-specific library html pages should be installed? (~name ok) [none] Pathname where the site-specific manual pages should be installed? (~name ok) [/usr/local/man/man1] Pathname where the site-specific library manual pages should be installed? (~name ok) [/usr/local/lib/perl5/5.8.9/man/man3] Pathname where add-on public executable scripts should be installed? (~name ok) [/usr/local/bin] Use the "fast stdio" if available? [y] off_t found. Checking to see how big your file offsets are... fpos_t found. Checking the size of fpos_t... Using instead of . qgcvt() NOT found. Checking how to print long doubles... gconvert NOT found. gcvt NOT found. sprintf() found. I'll use sprintf to convert floats into a string. fwalk() NOT found. access() found. defines the *_OK access constants. accessx() NOT found. aintl() NOT found. alarm() found. found. found. found. Testing to see if we should include , or both. We'll include . Checking to see if your struct tm has tm_zone field... Checking to see if your struct tm has tm_gmtoff field... asctime_r() found. atolf() NOT found. atoll() found. Checking whether your compiler can handle __attribute__((format)) ... Checking whether your compiler can handle __attribute__((malloc)) ... Checking whether your compiler can handle __attribute__((nonnull(1))) ... Checking whether your compiler can handle __attribute__((noreturn)) ... Checking whether your compiler can handle __attribute__((pure)) ... Checking whether your compiler can handle __attribute__((unused)) ... Checking whether your compiler can handle __attribute__((warn_unused_result)) ... bcmp() found. bcopy() found. getpgrp() found. You have to use getpgrp() instead of getpgrp(pid). setpgrp() found. You have to use setpgrp(pid,pgrp) instead of setpgrp(). Checking whether your compiler can handle __builtin_choose_expr ... Checking whether your compiler can handle __builtin_expect ... bzero() found. found. found. We'll include to get va_dcl definition. You have and , so checking for C99 variadic macros. You have C99 variadic macros. You have void (*signal())(). Checking whether your C compiler can cast large floats to int32. Checking whether your C compiler can cast negative float to unsigned. vprintf() found. Your vsprintf() returns (int). chown() found. chroot() found. chsize() NOT found. class() NOT found. clearenv() NOT found. Hmm... Looks like you have Berkeley networking support. socketpair() found. Checking the availability of certain socket constants... found. Checking to see if your system supports struct cmsghdr... Checking to see if your C compiler knows about "const"... copysignl() found. crypt() found. NOT found. crypt_r() NOT found. ctermid() found. ctermid_r() found. ctime_r() found. cuserid() NOT found. found. found. DBL_DIG found. dbmclose() NOT found. difftime() found. found. Your directory entries are struct dirent. Good, your directory entry keeps length information in d_namlen. Checking to see if DIR has a dd_fd member variable found. NOT found. dirfd() found. dlerror() found. found. What is the extension of dynamically loaded modules [so] Checking whether your dlsym() needs a leading underscore ... dlsym doesn't need a leading underscore. drand48_r() NOT found. dup2() found. eaccess() found. endgrent() found. found. endgrent_r() NOT found. endhostent() found. found. endhostent_r() NOT found. endnetent() found. endnetent_r() NOT found. endprotoent() found. endprotoent_r() NOT found. endpwent() found. found. endpwent_r() NOT found. endservent() found. endservent_r() NOT found. defines the O_* constants... and you have the 3 argument form of open(). found. We'll be including . found. We don't need to include if we include . fork() found. pipe() found. Figuring out the flag used by open() for non-blocking I/O... Let's see what value errno gets from read() on a O_NONBLOCK file... Checking how std your stdio is... Checking to see what happens if we set the stdio ptr... Increasing ptr in your stdio leaves cnt unchanged. Good. You seem to have 'fast stdio' to directly manipulate the stdio buffers. fchdir() found. fchmod() found. fchown() found. fcntl() found. Well, your system knows about the normal fd_set typedef... and you have the normal fd_set macros (just as I'd expect). fgetpos() found. finite() found. finitel() NOT found. flock() found. fp_class() NOT found. pathconf() found. fpathconf() found. fpclass() NOT found. fpclassify() NOT found. fpclassl() NOT found. Checking to see if you have fpos64_t... frexpl() found. found. found. Checking to see if your system supports struct fs_data... fseeko() found. fsetpos() found. fstatfs() found. statvfs() found. fstatvfs() found. fsync() found. ftello() found. Checking if you have a working futimes() Yes, you have getcwd() found. getespwnam() NOT found. getfsstat() found. getgrent() found. getgrent_r() found. getgrgid_r() found. getgrnam_r() found. gethostbyaddr() found. gethostbyname() found. gethostent() found. gethostname() found. uname() found. Shall I ignore gethostname() from now on? [n] gethostbyaddr_r() found. gethostbyname_r() found. gethostent_r() found. getitimer() found. getlogin() found. getlogin_r() found. getmnt() NOT found. getmntent() NOT found. getnetbyaddr() found. getnetbyname() found. getnetent() found. getnetbyaddr_r() found. getnetbyname_r() found. getnetent_r() found. getpagesize() found. getprotobyname() found. getprotobynumber() found. getprotoent() found. getpgid() found. getpgrp2() NOT found. getppid() found. getpriority() found. getprotobyname_r() found. getprotobynumber_r() found. getprotoent_r() found. getprpwnam() NOT found. getpwent() found. getpwent_r() found. getpwnam_r() found. getpwuid_r() found. getservbyname() found. getservbyport() found. getservent() found. getservbyname_r() found. getservbyport_r() found. getservent_r() found. getspnam() NOT found. NOT found. getspnam_r() NOT found. gettimeofday() found. gmtime_r() found. hasmntopt() NOT found. found. found. htonl() found. ilogbl() found. strchr() found. inet_aton() found. isascii() found. isfinite() NOT found. isinf() found. isnan() found. isnanl() NOT found. killpg() found. lchown() found. LDBL_DIG found. found. Checking to see if your libm supports _LIB_VERSION... No, it does not (probably harmless) link() found. localtime_r() found. localeconv() found. lockf() found. lstat() found. madvise() found. malloc_size() NOT found. malloc_good_size() NOT found. mblen() found. mbstowcs() found. mbtowc() found. memchr() found. memcmp() found. memcpy() found. memmove() found. memset() found. mkdir() found. mkdtemp() found. mkfifo() found. mkstemp() found. mkstemps() found. mktime() found. found. mmap() found. and it returns (void *). sqrtl() NOT found. scalbnl() found. modfl() found. Your modfl() seems okay for large values. mprotect() found. msgctl() found. msgget() found. msgsnd() found. msgrcv() found. You have the full msg*(2) library. Checking to see if your system supports struct msghdr... msync() found. munmap() found. nice() found. found. nl_langinfo() found. Checking to see if your C compiler knows about "volatile"... Choosing the C types to be used for Perl's internal types... Checking how many bits of your UVs your NVs can preserve... Checking whether NV 0.0 is all bits zero in memory... 0.0 is represented as all bits zero in memory Checking to see if you have off64_t... pause() found. poll() found. readlink() found. vfork() found. Do you still want to use vfork()? [y] pthread_attr_setscope() found. random_r() NOT found. readdir() found. seekdir() found. telldir() found. rewinddir() found. readdir64_r() NOT found. readdir_r() found. readv() found. recvmsg() found. rename() found. rmdir() found. found. Checking if your memcmp() can compare relative magnitude... select() found. semctl() found. semget() found. semop() found. You have the full sem*(2) library. You have union semun in . You can use union semun for semctl IPC_STAT. You can also use struct semid_ds* for semctl IPC_STAT. sendmsg() found. setegid() found. seteuid() found. setgrent() found. setgrent_r() NOT found. sethostent() found. sethostent_r() NOT found. setitimer() found. setlinebuf() found. setlocale() found. found. setlocale_r() NOT found. setnetent() found. setnetent_r() NOT found. setprotoent() found. setpgid() found. setpgrp2() NOT found. setpriority() found. setproctitle() found. setprotoent_r() NOT found. setpwent() found. setpwent_r() NOT found. setregid() found. setresgid() found. setreuid() found. setresuid() found. setrgid() found. setruid() found. setservent() found. setservent_r() NOT found. setsid() found. setvbuf() found. NOT found. shmctl() found. shmget() found. shmat() found. and it returns (void *). shmdt() found. You have the full shm*(2) library. sigaction() found. NOT found. Checking to see if you have signbit() available to work on double... Yes. sigprocmask() found. POSIX sigsetjmp found. snprintf() found. vsnprintf() found. sockatmark() found. socks5_init() NOT found. Checking whether sprintf returns the length of the string... sprintf returns the length of the string (as ANSI says it should) srand48_r() NOT found. srandom_r() NOT found. found. Checking to see if your struct stat has st_blocks field... NOT found. NOT found. Checking to see if your system supports struct statfs... Checking to see if your struct statfs has f_flags field... Checking how to access stdio streams by file descriptor number... I can't figure out how to access stdio streams by file descriptor number. strcoll() found. Checking to see if your C compiler can copy structs... strerror() found. strerror_r() found. strftime() found. strlcat() found. strlcpy() found. strtod() found. strtol() found. strtold() found. strtoll() found. strtoq() found. strtoul() found. strtoull() found. strtouq() found. strxfrm() found. symlink() found. syscall() found. sysconf() found. system() found. tcgetpgrp() found. tcsetpgrp() found. time() found. time_t found. found. times() found. clock_t found. tmpnam_r() NOT found. truncate() found. ttyname_r() found. tzname[] found. (Testing for character data alignment may crash the test. That's okay.) It seems that you must access character data in an aligned manner. ualarm() found. umask() found. unordered() NOT found. unsetenv() found. usleep() found. ustat() NOT found. closedir() found. Checking whether closedir() returns a status... wait4() found. waitpid() found. wcstombs() found. wctomb() found. writev() found. Checking alignment constraints... Doubles must be aligned on a how-many-byte boundary? [8] Checking to see how your cpp does stuff like concatenate tokens... Oh! Smells like ANSI's been here. found. Checking Berkeley DB version ... Looks OK. Checking return type needed for hash for Berkeley DB ... Checking return type needed for prefix for Berkeley DB ... Looking for a random number function... Good, found drand48(). Use which function to generate random numbers? [drand48] Determining whether or not we are on an EBCDIC system... Nope, no EBCDIC, probably ASCII or some ISO Latin. Or UTF-8. Checking how to flush all pending stdio output... Your fflush(NULL) works okay for output streams. Let's see if it clobbers input pipes... fflush(NULL) seems to behave okay with input streams. Checking the size of gid_t... Checking the sign of gid_t... Checking how to print 64-bit integers... Checking the format strings to be used for Perl's internal types... Checking the format string to be used for gids... getgroups() found. setgroups() found. What type pointer is the second argument to getgroups() and setgroups()? [gid_t] Checking if your /usr/bin/make program sets $(MAKE)... mode_t found. Bus error (core dumped) It seems that va_copy() or similar will be needed. size_t found. What is the type for the 1st argument to gethostbyaddr? [char *] What is the type for the 2nd argument to gethostbyaddr? [size_t] What pager is used on your system? [/usr/bin/less] pid_t found. Checking how to generate random libraries on your machine... Your select() operates on 64 bits at a time. Generating a list of signal names and numbers... Checking the size of size_t... Checking to see if you have socklen_t... NOT found. I'll be using ssize_t for functions returning a byte count. Your stdio uses signed chars. Checking the size of uid_t... Checking the sign of uid_t... Checking the format string to be used for uids... Which compiler compiler (byacc or yacc) shall I use? [/usr/bin/byacc] NOT found. NOT found. NOT found. found. found. NOT found. found. dbm_open() found. NOT found. found. found. NOT found. Guessing which symbols your C compiler and preprocessor define... tcsetattr() found. You have POSIX termios.h... good! found. NOT found. found. found. You have socket ioctls defined in . found. NOT found. found. NOT found. found. found. found. found. NOT found. found. NOT found. NOT found. Looking for extensions... What extensions do you wish to load dynamically? [B ByteLoader Cwd DB_File Data/Dumper Devel/DProf Devel/PPPort Devel/Peek Digest/MD5 Encode Fcntl File/Glob Filter/Util/Call Hash/Util I18N/Langinfo IO IPC/SysV List/Util MIME/Base64 NDBM_File Opcode POSIX PerlIO/encoding PerlIO/scalar PerlIO/via SDBM_File Socket Storable Sys/Hostname Sys/Syslog Text/Soundex Time/HiRes Unicode/Normalize XS/APItest XS/Typemap attrs re threads threads/shared] What extensions do you wish to load statically? [none] Stripping down executable paths... Creating config.sh... Doing variable substitutions on .SH files... Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Not re-extracting config.h Extracting makeaperl (with variable substitutions) Extracting makedepend (with variable substitutions) Extracting makedir (with variable substitutions) Extracting Makefile (with variable substitutions) Extracting myconfig (with variable substitutions) Extracting pod/Makefile (with variable substitutions) Extracting Policy.sh (with variable substitutions) Extracting utils/Makefile (with variable substitutions) Extracting writemain (with variable substitutions) Extracting x2p/cflags (with variable substitutions) Extracting x2p/Makefile (with variable substitutions) Configure done. If you compile perl5 on a different machine or from a different object directory, copy the Policy.sh file from this object directory to the new one before you run Configure -- this will help you with most of the policy defaults. ===> Building for perl-5.8.9 make: cannot open makefile. *** Error code 2 Stop in /usr/ports/lang/perl5.8. *** Error code 1 Stop in /usr/ports/lang/perl5.8. Anton Berezin wrote: > On Thu, Jan 29, 2009 at 11:30:48AM -0500, William Bentley wrote: > >> Hey All, >> >> Trying to build Perl5.8 and keep getting error messages. This is a >> new installation under 7.1Release. Already did a make clean and >> portsnap. Any ideas appreciated. Here is the ouput. >> >> .....snip....... >> > > ^^^^ here is the interesting part. > > >> Extracting Policy.sh (with variable substitutions) >> Extracting utils/Makefile (with variable substitutions) >> Extracting writemain (with variable substitutions) >> Extracting x2p/cflags (with variable substitutions) >> Extracting x2p/Makefile (with variable substitutions) >> Configure done. >> >> If you compile perl5 on a different machine or from a different object >> directory, copy the Policy.sh file from this object directory to the >> new one before you run Configure -- this will help you with most of >> the policy defaults. >> >> ===> Building for perl-5.8.9 >> make: cannot open makefile. >> *** Error code 2 >> >> Stop in /usr/ports/lang/perl5.8. >> *** Error code 1 >> >> Stop in /usr/ports/lang/perl5.8. >> > > Could you attach a complete output of the configure stage? > > \Anton. > From lawrence.auster at att.net Thu Jan 29 14:28:56 2009 From: lawrence.auster at att.net (Lawrence Auster) Date: Thu Jan 29 14:29:30 2009 Subject: The =?iso-8859-1?q?=93Military=2C?= Industrial =?iso-8859-1?q?Complex=94?= is no more -- The Hidden Massive Racial Discrimination in America against Whites Message-ID: <20090129220505.LTWD11567.fed1rmmtao104.cox.net@fed1rmimpo03.cox.net> The “Military, Industrial Complex” is no more. Today it is the Political, Financial and Media — Zionist Complex! 1/28/2009 An short essay by Dr. David Duke The “Military-Industrial complex” really has no relevance to the real holders of global power today. America is the most powerful military and economic nation on earth. The powers that control the levers of political power in America possess the greatest power the world has ever seen. Who really has power over the government today? Is it the fabled “Military, Industrial Complex”? An effective gauge of direct political power in America is “to discover who provided the pivotal amounts of the billion-dollar recent campaigns for U.S. President. You can look directly at campaign contributions for every candidate from the Federal Election Commission in order to find out who holds the real power in politics. So, who holds the real power over the American political establishment? Let’s first look at who does not hold much power over the establishment. 1) It is not the military. There is not any organized military monetary influence or even significant political influence of the military over the politicians. In fact, no one in military positions of authority are allowed to openly get involved in politics. No active sergeant, lieutenant, or General can send out a directive to the men under him to support or oppose a particular candidate (the one exception I know to that was when the Louisiana commanding general of the National Guard, under Jewish influence, sent a letter to all national guardsmen telling them that it was their “patriotic duty” to vote against David Duke and for the Liberal corrupt former Governor, Edwin Edwards. Even that caused a scandal in military circles, as it should have. 2) It is NOT major manufacturing or even the huge oil companies. There was not one oil company and only a couple of legitimate manufacturing or industrial concerns on Obama and McCain’s top twenty contributor list. The list was completely dominated by Zionist international banking firms. If one combines every defense contractor’s contributions the money they give in politics is minuscule compared to Zionist international banks. They don’t even come close to the power in lobbying that AIPAC and a couple of dozen more Jewish extremist organizations have. Jewish lobbyists literally get almost unanimous support in Congress for outrageous giveaways to Israel, a nation that has committed terrorism against us and killed or maimed scores of Americans. I am not talking about contracts here, I am speaking about giving away billions of dollars to a foreign nation. So, so much for the media-popularized term, the military-industrial complex In direct political money and lobbying then, Zionists are the undisputed masters of the American political establishment. In addition to their control through the use of money as an inducement or a threat, they have tens of thousands of Jewish extremists scattered throughout the entire bureaucracy who are very conscious of supporting their brethren and supporting the organized Jewish agenda. They also are ready to act against any Gentile who dares to go against Israel or the Jewish agenda. How will a Jewish federal judge rule in a huge litigation issue between Jewish and non-Jewish parties? Why was the biggest robber in the history of the world, Bernie Madoff who stole over 50 billion dollars and who ruined tens of thousands of families, only charged with one criminal count, and allowed to stay in his luxury apartment to await trial? Is there an organized Jewish agenda? Absolutely. In fact, the leading and most powerful Jewish groups have a supra-organization called the Council of Presidents (composed of the most powerful 5 dozen Jewish organizations in America). They issue detailed positions not just on Mideast policy but on many other issues that have nothing to do with Israel, aspects of domestic policy including issues such as opening America’s borders. They even assume positions on issues that you wouldn’t even think would have unanimity among Jews, such as abortion rights. Their job is to make sure that Jewish power is absolutely united on what they decide are their common agendas. Next, we must talk about one of the most influential parts of the American political process, the mass media. The media, such as the NY Times and the Washington Post (the newspaper read by every member of America’s government and bureaucracy in Washington). The Washington Post can determine even what issues Congress will discuss and it greatly affects the publicity for or against those issues. Broadcast and cable television also have an enormous impact, and we can include movies, books, magazines and the newspaper chains that reach down into almost every American community. As my chapters in Jewish Supremacism on “Jewish Media Supremacy” document, the ownership, depth and breadth of Jewish influence in the media is simply breathtaking. In media, whether you speak of owners, administrators, managers, editors, producers, writers, correspondents, pundits and reporters, there is an army of Jews who are animated by the Holocaust and the issues of the organized Jewish community. If you haven’t yet read them, you simply must see the evidence on the Jewish supremacy in media I have compiled in my books Jewish Supremacism and My Awakening. The other great seat of establishment power is simply money, huge sums of money and the willingness to use those funds on behalf of an agenda. The biggest concentrations of wealth in the world today are in the Zionist international banks, and in financial groups that the Jews completely control such as the Federal Reserve Corporation, the same forces that have led us to the doorstep of a great depression. It is no accident that Alan Greenspan and Ben Shalom Bernanke are the last two of the Federal Reserve czars. Even in days of World War I, an immensely rich, Jewish international banker, Jacob Schiff, voiced pride in the fact that he was instrumental in weakening Czarist Russia (the government that Jews universally hated), and that he supported Russia’s enemies so as to make Russia ripe for communist overthrow (Jewish groups brag of his help to Japan in the Russo-Japanese War so as to hurt the Russian government). Schiff also gave millions of dollars to directly finance the Jews who led and organized the Russian revolution and the Bolshevik terror in Russia. There is no disputing of these facts. Plenty of Jewish history books detail all of it. So, frankly, financial power in the control of people who will use it for an agenda is also a key ingredient of real power. Again, the financial power in the hands of modern day Jacob Schiff’s, is an incredibly powerful weapon. So forget about the “Military-Industrial Complex.” That is passe. In today’s world it makes more sense to speak about the “Political, Financial and Media Zionist complex.” That is the real core of power that bends everything whether it be local laws, or giant corporations, to its will. Even if one of the world’s richest firms, such as Microsoft (which is now by the way run by a Jewish extremist), would buck the political, financial, and media Zionist complex, it would be broken by government fiat, the Jewish-influenced courts (such as anti-trust actions), and by vicious attacks by the Jewish-influenced media. Microsoft would either be dismembered or destroyed. Such are the realities of the modern world. There is no longer a “military industrial complex,” but there is a Political and media and financial Zionist complex that rules us and aims to control the whole world. No single part of this behemoth can be defeated, because it can use its other assets to defend the section under attack. It can only be brought down by concentrating all our political and ideological fire right on the core the problem, International Zionism and its driving impetus: Jewish Supremacism. —Dr. David Duke Source : http://www.davidduke.com/general/forget-the-military-industrial-complex-today-its-the-political-financial-and-media-zionist-complex_7394.html ---- The Hidden Massive Racial Discrimination in America against Whites 1/29/2009 The main argument for affirmative action is that institutions should reflect racial percentages of population, if not there must be de facto racial discrimination. Here is the breakdown of students by race at America’s premier university, Obama’s alma mater, Harvard. Even though non-Jewish White Americans are almost 70 percent of the population and on average score much higher on entrance exams, they are only about 22 percent of the Harvard student body. So what race is really the victim of racial discrimination? For those who are truly dedicated to stopping racial discrimination, what are you going to do about this massive discrimination, or does it not matter to you because White people happen to be the victims? The hidden, massive racial discrimination that goes on in America against White people! A U.S. Government study offers proof that European Americans face massive institutional racial discrimination that affects millions of the most talented and educated of our people Introduction by Dr. David Duke – As most of you know, the term “white supremacist” has become literally a prefix of my name when I am in the news. It is the media’s way to condition readers not to pay attention to what I say because I am a “white supremacist.” The truth is I am not a White supremacist, and I seek no supremacy or control over any people, but I do demand that the rights of people of European descent to be respected as much as any other people’s rights. The fact is that in the United States of America, Canada, the UK in many areas of Europe Whites face a powerful state-sanctioned, and often mandated, racial discrimination against White people who are better-qualified than their non-White counterparts. It may be surprising to some reading this, but millions of discriminated against Whites are often poorer and who face more difficult social situations than many of their non-White counterparts who are being given preference over them. It also affects the most talented of our people. Many Whites are under the mistaken impression that the White victims of racial discrimination are mostly from the low income and low IQ sectors of the population. Nothing could be further from the truth. In actuality, the percentages of Whites who are victims of racial discrimination are much higher in the sectors of the White population with the highest intelligence and greatest abilities. The facts are shocking, but true. Most people know that most universities have programs of admittance that give less-qualified minorities preference over better-qualified Whites. Almost all of the Fortune 500 largest corporations have affirmative action and diversity programs that discriminate against White people, both male and female, in hiring. They also have programs of discrimination that favor non-Whites in promotions and advancement. This is true in the academic area as well. You can look at almost any academic department of any American university and you will see in place a strong racial bias for “minorities” in preface over Whites in hiring and advancement. Whether you are talking about a university History, English or Math department in almost any university these policies are in place and powerful. These racial discriminatory policies are real, and they can be easily proven to exist. But, now we thanks to a government study, there is even a more powerful way to show their real impact on tens of mi llions of White Americans. The brilliant economist and author whose pen name is Yggdrasil has compiled the data from the National Longitudinal Survey of Youth (NLSY) 1979, which was a massive study conducted by the Department of Labor to track the lives of 155,000 Americans by race, IQ, income, education and other factors to see how remedial efforts for minorities were doing. It was done after the installation of so called “affirmative action” programs which gave preference to non-White groups over whites. The NLSY study is meant to follow this huge sampling for their entire lives to see how diversity is working out for America. The data is from this ongoing study is tangible proof of the horrendous level of racial discrimination going on against White people. I will link you to Yggdrasil’s fine paper in a moment, but let me first give you a couple of snippets from his work that proves the existence of massive racial discrimination going on against our people. Here is a chart showing the ethnic breakdown of the most prestigious university in the United States of America: Harvard. America’s premier university is extremely expensive (unless you receive special grants and scholarships) and a degree from it just about guarantees its graduates the best paid and prestigious jobs America has to offer. Affirmative action advocates have long said the companies or institutions that don’t reflect the actual racial population percentages are de facto racist and discriminatory. So what is the situation at Harvard, non-Jewish Whites who are about 70 pecent of the American population are only about 22 percent of the Harvard student body. One should first consider the fact that Whites are represented in the top two percentile level on college admission tests on an average that is a 5 times higher rate than non-White groups. If one then factors in the fact that Whites are also 70 percent of the population, there should be at least 25 times more Whites who would be better qualified than the non-White students currently at Harvard. But even though these Whites are the best and brightest America has to offer they are limited to only 20 percent of Harvard students! Such is nothing more than blatant, racial discrimination. Another interesting fact one can gleam from this chart and many in the NLSY studies that Jewish over-representation is not based simply on the fact that Jews have a high intelligence, they often do twice as well as their intelligence bracket would indicate. Such would suggest the intra-tribal support system for group cohesion and advancements aids their success rate. The NLSY data also shows how incomes today in the USA correlate with race and intelligence. Let’s take a look NLSY tracking studies of intelligent White women, these are White women in the 90 to 97 percent IQ bracket as compared to Black women in that same high 90 to 97 percent IQ bracket. The average Black females of that IQ level earned an average of approximately $54,000 per year through 1996, whereas White females on the same IQ level earned only half of that amount, about $28,000 per year through 1996. When White women in the same intelligent bracket of Black women earn half of the average amount that the Black women do, that’s real racial discrimination. I am not referring here to a few White women who are at least equally qualified but getting half the salary that Black women do, I am talking about the average White women in America! The NLSY is a big enough sample that reflects the whole nation. In fact it is meant to. The average White woman of high intelligence earns one-half of what Black women do of the same intelligence! I obviously don’t like this racial discrimination against our people. Neither does the economist Yggdrasil. We advocate that the best person regardless of race gets whatever college admission or job or promotion their abilities dictate. We have no fear of how well our people will do on a fair playing field. Because we stand for true civil rights, human rights in the matter, we are called racists, and the real capper: “white supremacists.” There are many people in America and around the world who are ignorant of the facts of anti-White racial discrimination. The media acts like it doesn’t exist. Even after the election of an affirmative action African-American President, America is still painted as an anti-Black racist country. The truth is that European Americans are facing racial discrimination in the very institutions and nation that our forefathers created. Our movement is truly a liberation movement like any other in the world that strives for a people to free and live in society of our own values rather than oppressive society imposed upon us. We are not racists or supremacists trying to deny the rights of others. We are human rights activists defending our people’s rights and heritage. –Dr. David Duke Source & Charts : http://www.davidduke.com/general/the-real-racial-discrimination-that-goes-on-in-america_7407.html ----- Obama’s Mideast Jewish Wet Dream Team George Mitchell is the new American envoy now in the Mideast. Who is Mitchell and who are the key players in Obama’s Mideast policy team? First, let’s examine the major players on the Obama foreign policy team. Roger Cohen writing in The New York Times on January 11, 2009 wrote some things that if he were a Gentile would have earned him some attacks as an “anti-Semite.” He pointed out the incredible top-heavy pro-Zionist content of the team which is supposed to broker a fair and just peace in the Mideast. In discussing the team he identified them with these words: They include Dennis Ross (the veteran Clinton administration Mideast peace envoy who may now extend his brief to Iran) [a long-time Jewish Zionist]; James Steinberg [Jewish Zionist] (as deputy secretary of state) ; Dan Kurtzer [Jewish Zionist] (the former U.S. ambassador to Israel); Dan Shapiro [Jewish Zionist] (a longtime aide to Obama); and Martin Indyk [Jewish Zionist] another former ambassador to Israel who is close to the incoming secretary of state, Hillary Clinton.) Now, I have nothing against smart, driven, liberal, Jewish (or half-Jewish) males; I’ve looked in the mirror. I know or have talked to all these guys, except Shapiro. They’re knowledgeable, broad-minded and determined. Still, on the diversity front they fall short. On the change-you-can-believe-in front, they also leave something to be desired. Cohen did not even mention that the two closest advisers to Obama, the guys that filter almost everything that Obama see and hears and makes the day to day decisions of running the oval office. They are David Axelrod and Rahm Emmanuel, two long time dedicated Jewish extremists. Emmanuel, son of an Irgun terrorist and named after another Irgun terrorist, even fought in the Israeli Army. Now we come to the new envoy to the Mideast, George Mitchell of Maine, the man who is supposed to be a broadminded and just arbitrator between Israel and the Palestinians. The Jewish-influenced has made a big point of Mitchell’s Lebanese ancestry. What the Zionist media doesn’t tell you is that he has been completely under the control of AIPAC and radical Zionists for years. As Senate Majority Leader he rammed through everything Israel wanted. He even supported the Senate resolution that gave Israel unconditional support during the Zionist massacre of thousands of Gaza civilians. In fact, originally an appointee to the Senate, Mitchell owes his entire Senate career on the massive support given him in 1982 and since by AIPAC and 27 other Jewish extremist controlled political action committees that AIPAC arranged. AIPAC’s Tom Dine summarized AIPAC’s success in Mitchell’s election by saying that “American Jews are thus able to form our own foreign policy agenda.” Of course, Dine spoke the complete and unvarnished truth. American and Israeli extremist Jews do indeed control the foreign policy of the United States. Such control has long gone on in concert with past U.S. Presidents and it goes on today with Obama. Only difference is that today there is a greater danger because many in America and around the world falsely believe that Obama represents change. With the incredible respect and adulation given to Obama, he is in a much better position to support the Zionist war agenda and ultimately do far more harm than a discredited George Bush. Hold on to your hats, America. I predict Obama will usher in war and conflagration that will make George Bush’s presidency seem mild in comparison. He has already announced a doubling of American troops in Afghanistan. Can a catastrophic war with Iran be far behind? Jewish extremists want this war and Obama is completely under their control! – Dr. David Duke Source : http://www.davidduke.com/general/who-is-on-obamas-dream-team-for-mideast-peace_7380.html ------------------------------------- You or someone using your email adress is currently subscribed to the Lawrence Auster Newletter. If you wish to unsubscribe from our mailing list, please let us know by calling "to 1 212 865 1284 Thanks, Lawrence Auster, 238 W 101 St Apt. 3B New York, NY 10025 Contact: lawrence.auster@att.net ------------------------------------- From pav at FreeBSD.org Fri Jan 30 14:47:52 2009 From: pav at FreeBSD.org (Pav Lucistnik) Date: Fri Jan 30 14:47:59 2009 Subject: [Fwd: p5-Net-EPP-Frame-0.11 failed on amd64 6-exp] Message-ID: <1233355665.50424.24.camel@hood.oook.cz> This port seems to have been now part of p5-Net-EPP. > => Net-EPP-Frame-0.11.tar.gz doesn't seem to exist in /tmp/distfiles/. > => Attempting to fetch from ftp://ftp.funet.fi/pub/languages/perl/CPAN/modules/by-module/Net/. > fetch: ftp://ftp.funet.fi/pub/languages/perl/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from ftp://ftp.cpan.org/pub/CPAN/modules/by-module/Net/. > fetch: ftp://ftp.cpan.org/pub/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from http://www.cpan.dk/modules/by-module/Net/. > fetch: http://www.cpan.dk/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: Not Found > => Attempting to fetch from http://ring.nict.go.jp/archives/lang/perl/CPAN/modules/by-module/Net/. > fetch: http://ring.nict.go.jp/archives/lang/perl/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: Not Found > => Attempting to fetch from http://ring.sakura.ad.jp/archives/lang/perl/CPAN/modules/by-module/Net/. > fetch: http://ring.sakura.ad.jp/archives/lang/perl/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: No address record > => Attempting to fetch from http://ring.riken.jp/archives/lang/perl/CPAN/modules/by-module/Net/. > fetch: http://ring.riken.jp/archives/lang/perl/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: Not Found > => Attempting to fetch from ftp://ftp.kddlabs.co.jp/lang/perl/CPAN/modules/by-module/Net/. > fetch: ftp://ftp.kddlabs.co.jp/lang/perl/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from ftp://ftp.dti.ad.jp/pub/lang/CPAN/modules/by-module/Net/. > fetch: ftp://ftp.dti.ad.jp/pub/lang/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from ftp://ftp.sunet.se/pub/lang/perl/CPAN/modules/by-module/Net/. > fetch: ftp://ftp.sunet.se/pub/lang/perl/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from ftp://mirror.hiwaay.net/CPAN/modules/by-module/Net/. > fetch: ftp://mirror.hiwaay.net/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from ftp://ftp.mirrorservice.org/sites/ftp.funet.fi/pub/languages/perl/CPAN/modules/by-module/Net/. > fetch: ftp://ftp.mirrorservice.org/sites/ftp.funet.fi/pub/languages/perl/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from ftp://csociety-ftp.ecn.purdue.edu/pub/CPAN/modules/by-module/Net/. > fetch: ftp://csociety-ftp.ecn.purdue.edu/pub/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from ftp://ftp.isu.net.sa/pub/CPAN/modules/by-module/Net/. > fetch: ftp://ftp.isu.net.sa/pub/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from ftp://ftp.cs.colorado.edu/pub/perl/CPAN/modules/by-module/Net/. > fetch: ftp://ftp.cs.colorado.edu/pub/perl/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from ftp://cpan.pop-mg.com.br/pub/CPAN/modules/by-module/Net/. > fetch: ftp://cpan.pop-mg.com.br/pub/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from http://at.cpan.org/modules/by-module/Net/. > fetch: http://at.cpan.org/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: Moved Temporarily > => Attempting to fetch from ftp://ftp.chg.ru/pub/lang/perl/CPAN/modules/by-module/Net/. > fetch: transfer timed out > => Attempting to fetch from ftp://ftp.auckland.ac.nz/pub/perl/CPAN/modules/by-module/Net/. > fetch: ftp://ftp.auckland.ac.nz/pub/perl/CPAN/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: File unavailable (e.g., file not found, no access) > => Attempting to fetch from http://backpan.cpan.org/modules/by-module/Net/. > fetch: http://backpan.cpan.org/modules/by-module/Net/Net-EPP-Frame-0.11.tar.gz: Not Found > => Attempting to fetch from http://nowhere/. > fetch: http://nowhere/Net-EPP-Frame-0.11.tar.gz: No address record > => Couldn't fetch it - please try to retrieve this > => port manually into /tmp/distfiles/ and try again. > *** Error code 1 > > Stop in /a/ports/net/p5-Net-EPP-Frame. > ================================================================ > build of /usr/ports/net/p5-Net-EPP-Frame ended at Fri Jan 30 21:52:33 UTC 2009 -- Pav Lucistnik And the sign said long haired, freaky people need not apply. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-perl/attachments/20090130/2810f5b4/attachment.pgp From lx at redundancy.redundancy.org Sat Jan 31 12:08:18 2009 From: lx at redundancy.redundancy.org (David E. Thiel) Date: Sat Jan 31 12:08:24 2009 Subject: update of libssh2 Message-ID: <20090131194201.GK51310@redundancy.redundancy.org> Libssh2 has been updated, so p5-Net-SSH2 will need to look for ssh2.0 instead of ssh2.1. Would you like me to fix? Thanks, David