Bug 206318 - dev-db/mysql-gui-tools-5.0_p12-r2 compile problems with sigc
|
Bug#:
206318
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: swegener@gentoo.org
|
Reported By: shogun713@gmail.com
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: dev-db/mysql-gui-tools-5.0_p12-r2 compile problems with sigc
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2008-01-17 11:35 0000
|
Hi!
I notice that this ebuild emerge fails due to some error in code (the namespace
of sigc is pointed as SigC instead of sigc).
I attach a patch which fixes this problem.
Hope this helps.
Shogun
Reproducible: Always
Steps to Reproduce:
1.Try to emerge the package
2.
3.
Actual Results:
Does not compile
Expected Results:
Should compile
(In reply to comment #0)
> I attach a patch which fixes this problem.
Also post the actual emerge output with errors so that people can find the bug
when they have this problem.
Reopen the bug so that you can set it to resolved
<snip>
GConnectDialog.cc: In member function ‘void
MGConnectDialog::open_connection_editor()’:
MGConnectDialog.cc:662: error: ‘SigC’ has not been declared
MGConnectDialog.cc:662: error: expected `;' before ‘c1’
MGConnectDialog.cc:664: error: ‘SigC’ has not been declared
MGConnectDialog.cc:664: error: expected `;' before ‘c2’
MGConnectDialog.cc:670: error: ‘c1’ was not declared in this scope
MGConnectDialog.cc:671: error: ‘c2’ was not declared in this scope
MGConnectDialog.cc: In member function ‘void
MGConnectDialog::show_connection_failed()’:
MGConnectDialog.cc:679: error: ‘SigC’ has not been declared
MGConnectDialog.cc:679: error: expected `;' before ‘input_handler’
MGConnectDialog.cc:689: warning: deprecated conversion from string constant to
‘char*’
MGConnectDialog.cc:717: error: ‘input_handler’ was not declared in this
scope
MGConnectDialog.cc:752: error: ‘input_handler’ was not declared in this
scope
make[3]: *** [MGConnectDialog.o] Error 1
</snip>
Reopen this bugreport, this isn't fixed in CVS yet. I encountered the same
error, applying the patch fixed this bug for me. Please add and epatch this
patch in CVS.