Activity log for bug #65238
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2006-10-11 03:50:44 | Kevin Kubasik | bug | added bug | ||
| 2006-11-24 09:06:26 | Sebastian Dröge | mono: status | Unconfirmed | Confirmed | |
| 2006-11-24 09:06:26 | Sebastian Dröge | mono: importance | Undecided | Medium | |
| 2006-11-24 09:06:26 | Sebastian Dröge | mono: statusexplanation | Mono should ship two different pkgconfig files for Mono.Cairo 1.0 and Mono.Cairo 2.0, both specifying the complete path to the assembly. -r:something would only make gmcs look in /usr/lib/mono/2.0, mcs in 1.0 Please also see bug #64371 | ||
| 2006-11-24 09:20:20 | Sebastian Dröge | bug | assigned to mono (upstream) | ||
| 2006-11-24 14:34:14 | Bug Watch Updater | mono: status | Unknown | Confirmed | |
| 2006-11-26 11:31:24 | Gianvito Cavasoli | bug | added attachment 'mono.txt' (mono errors) | ||
| 2008-09-15 22:08:11 | Jo Shields | mono: status | Confirmed | Invalid | |
| 2008-09-15 22:08:11 | Jo Shields | mono: statusexplanation | Mono should ship two different pkgconfig files for Mono.Cairo 1.0 and Mono.Cairo 2.0, both specifying the complete path to the assembly. -r:something would only make gmcs look in /usr/lib/mono/2.0, mcs in 1.0 Please also see bug #64371 | Sorry, I'm unable to reproduce with modern Mono - it's normal not to supply a pkg-config file for 1.0 and 2.0 versions of a library, the error seems to be happening due to a failure to correctly remap 1.0 library references to 2.0 when gmcs is compiling (which is certainly not the case today), and the apps in question do not show this bug when building. Rejecting. | |
| 2010-02-21 16:10:12 | Mark Reitblatt | removed subscriber Mark Reitblatt |
