[Mono-bugs] [Bug 698756] New: When building certain projects, XBuild throws an error about importing mscorlib multiple times

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Wed Jun 8 08:16:19 EDT 2011


https://bugzilla.novell.com/show_bug.cgi?id=698756

https://bugzilla.novell.com/show_bug.cgi?id=698756#c0


           Summary: When building certain projects, XBuild throws an error
                    about importing mscorlib multiple times
    Classification: Mono
           Product: Mono: Compilers
           Version: SVN
          Platform: x86-64
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: C#
        AssignedTo: msafar at novell.com
        ReportedBy: james at jaddie.co.uk
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Opera/9.80 (Windows NT 6.1; U; Edition Next; en)
Presto/2.8.158 Version/11.50

When attempting to build various different solutions, xbuild throws a wobbler
on some proj files complaining that mscorlib has already been imported.
The workaround NoStdLib=true fixes this however it requires 2 builds, and
breaks other projects too if they are not built first.
Apparently the msbuild behaviour changed recently and XBuild hasn't been
updated as such.

Reproducible: Always

Steps to Reproduce:
1. Grab the included solution
2. Build the sln without any params at all.
3. Observe the mscorlib failure
Actual Results:  
: error CS1703: An assembly with the same identity `mscorlib, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089' has already been imported.
Consider removing one of the references

Expected Results:  
Build Succeeded :D

The system its being built on, is 64bit gentoo, mono from the git built about 1
hour ago 08/06/2011 @ 12:00 GMT -- Master branch.
I also have other solutions if needed that fail.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list