Bug 141032 - bbacpi fails to build with gcc-4.1 due to extra qualifiers in resource.hh
Bug#: 141032 Product:  Gentoo Linux Version: 2006.0 Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: smithj@gentoo.org Reported By: keaneyw@gmail.com
Component: GCC Porting
URL: 
Summary: bbacpi fails to build with gcc-4.1 due to extra qualifiers in resource.hh
Keywords:  
Status Whiteboard: 
Opened: 2006-07-19 06:37 0000
Description:   Opened: 2006-07-19 06:37 0000 
Attempting to emerge bbacpi-0.1.5 with gcc-4.1 will result in failure due to
extra qualifiers on lines 129 and 130 of resource.hh.  Removing these extra
qualifiers resolves the issue.

I have created a patch and corresponding ebuild and would like feedback as to
stability / sanity.  Ultimately, if it passes review, please add this ebuild to
portage.

------- Comment #1 From William Keaney 2006-07-19 06:38:37 0000 ------- 
Created an attachment (id=92205) [details]
Ebuild utilizing the patch that removes extra qualifiers in resource.hh

Description pretty  much says it all: ebuild utilizing a patch.

------- Comment #2 From William Keaney 2006-07-19 06:40:09 0000 ------- 
Created an attachment (id=92206) [details]
Patch to remove extra qualifiers from resource.hh

Again, the description should be sufficient.

------- Comment #3 From Christian Faulhammer 2006-07-26 05:11:22 0000 ------- 
ping

------- Comment #4 From Jan 2006-08-05 13:17:10 0000 ------- 
WIlliam, please forgive, in general my reactions are much quicker, and they
will be in the future. Thanks for filing this bug and providing the patch.
However, it does not completely work out for me: I get some steps further, but
emerge then dies with

resource.cc:40: error: definition of implicitly-declared 'virtual
Resource::~Resource()'

during compilation. The only thing I can see (with my limited C++ experience)
is that this error has nothing to do with qualifiers :-)

------- Comment #5 From Ryan Hill 2006-11-05 14:44:07 0000 ------- 
Jan: I can't reproduce your error.  If you still have this problem, please open
a new bug with emerge --info.

Patch applied.  Thanks.