Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 405879 - dev-dotnet/gtk-sharp-2.12.10 - generated/Container.cs(11,38): error CS0234: The type or namespace name `Widget' does not exist in the namespace `Gtk'. Are you missing an assembly reference?
Summary: dev-dotnet/gtk-sharp-2.12.10 - generated/Container.cs(11,38): error CS0234: T...
Status: RESOLVED DUPLICATE of bug 404139
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: dotnet project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-26 11:16 UTC by Riccardo Brasca
Modified: 2012-03-04 13:06 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
emerge --info (info,4.42 KB, text/plain)
2012-02-26 11:16 UTC, Riccardo Brasca 		Details
build log (build.log,82.18 KB, text/plain)
2012-02-26 11:17 UTC, Riccardo Brasca 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Riccardo Brasca 2012-02-26 11:16:28 UTC 
emerge gtk-sharp fails with " error CS0234: The type or namespace name `Widget' does not exist in the namespace `Gtk'. Are you missing an assembly reference?".

Reproducible: Always

Steps to Reproduce:
1. emerge -av gtk-sharp




This could be related with bug #405877
Comment 1 Riccardo Brasca 2012-02-26 11:16:59 UTC 
Created attachment 303311 [details]
emerge --info
Comment 2 Riccardo Brasca 2012-02-26 11:17:12 UTC 
Created attachment 303313 [details]
build log
Comment 3 Pacho Ramos gentoo-dev 2012-02-27 19:34:47 UTC 
Probably related with bug 404139
Comment 4 Riccardo Brasca 2012-02-28 11:16:53 UTC 
(In reply to comment #3)
> Probably related with bug 404139

This is possibile, but I have no problem emerging gdk-sharp on my system.
Comment 5 Pacho Ramos gentoo-dev 2012-03-04 13:06:05 UTC 

*** This bug has been marked as a duplicate of bug 404139 ***