Summary: | dev-perl/DBI fails tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jerome Potts <jpotts> |
Component: | Current packages | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | minor | CC: | james |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
paludis --info dev-perl/DBI
paludis --info sys-libs/glibc paludis --info sys-devel/gcc |
Description
Jerome Potts
2009-08-01 17:56:30 UTC
Paludis is not officially supported, is there anyway you can test this behavior on a machine using portage and post your 'emerge --info' after doing so? There ought to be an equivalent way to show key system info, e.g. toolchain and architecture, using paludis (sorry I don't know it). Then others can try to reproduce this. BTW using an old toolchain (gcc 4.1.2/glibc 2.6.1) on amd64, DBI-1.601 passed those tests Created attachment 200613 [details]
paludis --info dev-perl/DBI
sys-libs/glibc-2.9_p20081201-r2
sys-devel/gcc-4.3.2-r3:4.3
Created attachment 200615 [details]
paludis --info sys-libs/glibc
Created attachment 200617 [details]
paludis --info sys-devel/gcc
$ gcc-config -l
[1] i686-pc-linux-gnu-4.1.2
[2] i686-pc-linux-gnu-4.3.2 *
Please reopen if you still have problems with DBI-1.609 (the only version in the tree) |