Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 382409

Summary: net-p2p/mldonkey-3.0.7 fails to build with gcc 4.6
Product: Gentoo Linux Reporter: Sergey Zubkov <cubbi>
Component: New packagesAssignee: Gentoo net-p2p team <net-p2p>
Status: RESOLVED OBSOLETE    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 346809    
Attachments: patch to fix the compilation error by providing the required ctor
patch to fix the compilation error but using correct declaration syntax

Description Sergey Zubkov 2011-09-09 15:58:37 UTC
net-p2p/mldonkey-3.0.7 fails to build with gcc-4.6.1-r1 with the following error message:

src/utils/lib/CryptoPP.cc:165:26: error: uninitialized const ‘CryptoPP::g_nullNa
meValuePairs’ [-fpermissive]
src/utils/lib/CryptoPP.h:694:20: note: ‘const class CryptoPP::NullNameValuePairs
’ has no user-provided default constructor


Reproducible: Always

Steps to Reproduce:
1. emerge =sys-devel/gcc-4.6.1-r1 (unmask/keyword as necessary)
2. gcc-config 2 (or whatever slot it gets to)
3. emerge =net-p2p/mldonkey-3.0.7
Comment 1 Sergey Zubkov 2011-09-09 16:01:04 UTC
Created attachment 285981 [details, diff]
patch to fix the compilation error by providing the required ctor
Comment 2 Sergey Zubkov 2011-09-12 14:16:23 UTC
Created attachment 286225 [details, diff]
patch to fix the compilation error but using correct declaration syntax

My first patch modified the class, but all this problem really needs is to fix the syntax error in the declaration of the const object.
Comment 3 Raúl Porcel (RETIRED) gentoo-dev 2011-09-17 18:03:50 UTC
Try with 3.1.0 but please, these bugs should go upstream, they should know how to fix it.
Comment 4 Sergey Zubkov 2011-09-20 03:45:00 UTC
Fixed in net-p2p/mldonkey-3.1.0
What's the appropriate status change in this case
Comment 5 Tony Vroon (RETIRED) gentoo-dev 2011-09-24 13:14:01 UTC
This is no longer an issue in 3.1.0 which is available in the tree. Closing report.