Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 228661 Details for
Bug 315989
dev-perl/Crypt-SSLeay-0.57: network tests fail
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
emerge log
Crypt-SSLeay-0.57.log (text/plain), 5.36 KB, created by
Kirikaza
on 2010-04-21 20:13:55 UTC
(
hide
)
Description:
emerge log
Filename:
MIME Type:
Creator:
Kirikaza
Created:
2010-04-21 20:13:55 UTC
Size:
5.36 KB
patch
obsolete
>You should enable -g (or higher) for debugging! > [32;01m*[0m CPV: dev-perl/Crypt-SSLeay-0.57 > [32;01m*[0m REPO: gentoo > [32;01m*[0m USE: elibc_glibc kernel_linux test userland_GNU x86 >>>> Unpacking source... >>>> Unpacking Crypt-SSLeay-0.57.tar.gz to /tmp/portage/dev-perl/Crypt-SSLeay-0.57/work >>>> Source unpacked in /tmp/portage/dev-perl/Crypt-SSLeay-0.57/work >>>> Compiling source in /tmp/portage/dev-perl/Crypt-SSLeay-0.57/work/Crypt-SSLeay-0.57 ... > [32;01m*[0m Using ExtUtils::MakeMaker > >BUILD INFORMATION >================================================ >ssl library: OpenSSL 0.9.8 in /usr >ssl header: openssl/ssl.h >libraries: -L/usr/lib -lssl -lcrypto -lgcc >include dir: -I/usr/include/openssl >================================================ >Checking if your kit is complete... >Looks good >Note (probably harmless): No library found for -lgcc >Writing Makefile for Crypt::SSLeay >The test suite can attempt to connect to public servers >to ensure that the code is working properly. If you are >behind a strict firewall or have no network connectivity, >these tests may fail (through no fault of the code). > >Do you want to run the live tests (y/N) ? [N] N >make -j3 OTHERLDFLAGS=-Wl,-O1 >/usr/bin/perl5.10.1 /usr/lib/perl5/vendor_perl/5.10.1/ExtUtils/xsubpp -typemap /usr/lib/perl5/5.10.1/ExtUtils/typemap -typemap typemap SSLeay.xs > SSLeay.xsc && mv SSLeay.xsc SSLeay.c >Running Mkbootstrap for Crypt::SSLeay () >chmod 644 SSLeay.bs >cp SSLeay.bs blib/arch/auto/Crypt/SSLeay/SSLeay.bs >chmod 644 blib/arch/auto/Crypt/SSLeay/SSLeay.bs >cp lib/Crypt/SSLeay/X509.pm blib/lib/Crypt/SSLeay/X509.pm >cp lib/Net/SSL.pm blib/lib/Net/SSL.pm >cp SSLeay.pm blib/lib/Crypt/SSLeay.pm >cp lib/Crypt/SSLeay/CTX.pm blib/lib/Crypt/SSLeay/CTX.pm >cp lib/Crypt/SSLeay/Conn.pm blib/lib/Crypt/SSLeay/Conn.pm >cp lib/Crypt/SSLeay/MainContext.pm blib/lib/Crypt/SSLeay/MainContext.pm >cp lib/Crypt/SSLeay/Err.pm blib/lib/Crypt/SSLeay/Err.pm >/usr/bin/gcc -c -I/usr/include/openssl -fno-strict-aliasing -pipe -fstack-protector -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -march=pentium4 -ftracer -mfpmath=sse -pipe -DVERSION=\"0.57\" -DXS_VERSION=\"0.57\" -fPIC "-I/usr/lib/perl5/5.10.1/i686-linux/CORE" SSLeay.c >rm -f blib/arch/auto/Crypt/SSLeay/SSLeay.so >LD_RUN_PATH="/usr/lib" /usr/bin/gcc -shared -O2 -march=pentium4 -ftracer -mfpmath=sse -pipe -L/usr/local/lib -fstack-protector SSLeay.o -Wl,-O1 -o blib/arch/auto/Crypt/SSLeay/SSLeay.so \ > -L/usr/lib -lssl -lcrypto \ > >chmod 755 blib/arch/auto/Crypt/SSLeay/SSLeay.so >>>> Source compiled. >make -j3 test TEST_VERBOSE=1 >PERL_DL_NONLAZY=1 /usr/bin/perl5.10.1 "-MExtUtils::Command::MM" "-e" "test_harness(1, 'blib/lib', 'blib/arch')" t/*.t >t/00-basic.t .... >1..12 >ok 1 - use Crypt::SSLeay; >ok 2 - use Crypt::SSLeay::CTX; >ok 3 - use Crypt::SSLeay::Conn; >ok 4 - use Crypt::SSLeay::Err; >ok 5 - use Crypt::SSLeay::MainContext; >ok 6 - use Crypt::SSLeay::X509; >ok 7 - use Net::SSL; >ok 8 - POD test for SSLeay.pm >ok 9 - POD test for lib/Net/SSL.pm >ok 10 - Crypt-SSLeay POD coverage is go! >ok 11 - Net::SSL POD coverage is go! >ok 12 - we have a context >ok >t/01-connect.t .. >1..8 >not ok 1 - Net::SSL->new > ># Failed test 'Net::SSL->new' ># at t/01-connect.t line 25. ># proxy connect failed: Bad arg length for Socket::pack_sockaddr_in, length is 9, should be 4 at /usr/lib/perl5/5.10.1/i686-linux/IO/Socket/INET.pm line 257. ># ; at t/01-connect.t line 11 >ok 2 # skip nothing listening on localhost:443 >ok 3 # skip nothing listening on localhost:443 >ok 4 # skip nothing listening on localhost:443 >ok 5 # skip nothing listening on localhost:443 >ok 6 # skip nothing listening on localhost:443 >ok 7 # skip nothing listening on localhost:443 >ok 8 # skip nothing listening on localhost:443 ># Looks like you failed 1 test of 8. >Dubious, test returned 1 (wstat 256, 0x100) >Failed 1/8 subtests > (less 7 skipped subtests: 0 okay) >t/02-live.t ..... >1..4 >ok 1 - use Net::SSL; ># config on linux ># ssl OpenSSL 0.9.8 in /usr ># lib -L/usr/lib -lssl -lcrypto -lgcc ># inc -I/usr/include/openssl ># cc /usr/bin/gcc >ok 2 - connect through proxy >ok 3 - can forward useragent string to proxy (network tests disabled) >ok 4 # skip Network tests disabled >ok > >Test Summary Report >------------------- >t/01-connect.t (Wstat: 256 Tests: 8 Failed: 1) > Failed test: 1 > Non-zero exit status: 1 >Files=3, Tests=24, 1 wallclock secs ( 0.07 usr 0.01 sys + 0.64 cusr 0.07 csys = 0.79 CPU) >Result: FAIL >Failed 1/3 test programs. 1/24 subtests failed. >make: *** [test_dynamic] Error 255 > [31;01m*[0m ERROR: dev-perl/Crypt-SSLeay-0.57 failed: > [31;01m*[0m test failed > [31;01m*[0m > [31;01m*[0m Call stack: > [31;01m*[0m ebuild.sh, line 54: Called src_test > [31;01m*[0m environment, line 2604: Called perl-module_src_test > [31;01m*[0m environment, line 2421: Called die > [31;01m*[0m The specific snippet of code: > [31;01m*[0m emake test TEST_VERBOSE=${TEST_VERBOSE:-0} || die "test failed"; > [31;01m*[0m > [31;01m*[0m If you need support, post the output of 'emerge --info =dev-perl/Crypt-SSLeay-0.57', > [31;01m*[0m the complete build log and the output of 'emerge -pqv =dev-perl/Crypt-SSLeay-0.57'. > [31;01m*[0m The complete build log is located at '/var/log/portage/dev-perl:Crypt-SSLeay-0.57:20100421-201039.log'. > [31;01m*[0m The ebuild environment file is located at '/tmp/portage/dev-perl/Crypt-SSLeay-0.57/temp/environment'. > [31;01m*[0m S: '/tmp/portage/dev-perl/Crypt-SSLeay-0.57/work/Crypt-SSLeay-0.57'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 315989
: 228661