Mon, 2005-07-25 at 22:03 +0100, Paul wrote:
./HtmlRender.cs(64) error CS1503: Argument 1: Cannot convert from
`Gecko.WebControl' to `Gtk.Widget'
./HtmlRender.cs(64) error CS1501: No overload for method `Add' takes `1'
arguments
make[1]: [browser.exe] Error 1
make: [all-recursive] Error 1

You are using gecko# from svn which uses the gtk#2 stuff. Casts can't be
done from v1 to v2.

You need *exactly* 0.6 from tarballs.
-- Ben

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

I stand corrected. you need version 0.6 of gecko-sharp.
- raf
Mon, 2005-07-25 at 14:06 -0700, Rafael Ferreira wrote:
You're are om the 2.0 version of gecko-sharp, you need version 1.0.

Actually I was working on a patch to make monodoc work with gecko 2.0,
does anyone think that it would be worth while?
- raf

Mon, 2005-07-25 at 22:03 +0100, Paul wrote:
Hi,

I have both the bog standard and developer versions of gtk-sharp
installed (as I've been told that they are happy side by side). However,
when I try to compile mono-tools, I'm getting the following error which
prevents the build.

Any ideas what's going on?

./elabel.cs(74) warning CS0108: `ELabel.Ellipsize(Pango.Layout, string,
int, int, int)' hides inherited member `Gtk.Label.Ellipsize'. Use the
new keyword if hiding was intended
/ `Gtk.Label.Ellipsize' (name of
symbol related to previous warning
./browser.cs(1155) warning CS0219: The variable `a' is assigned but its
value is never used
./browser.cs(760) warning CS0436: Ignoring imported type
`Monodoc.CopyXmlNodeWriter' since the current assembly already has a
declaration with the same name
./XmlNodeWriter.cs(14): `Monodoc.CopyXmlNodeWriter' (name of symbol
related to previous warning
/ `Monodoc.CopyXmlNodeWriter' (name of
symbol related to previous warning
./browser.cs(764) warning CS0219: The variable `dd' is assigned but its
value is never used
./browser.cs(1027) warning CS0219: The variable `md' is assigned but its
value is never used
./browser.cs(1057) warning CS0219: The variable `service' is assigned
but its value is never used
./browser.cs(1406) warning CS0219: The variable `path' is assigned but
its value is never used
./browser.cs(1691) warning CS0219: The variable `found' is assigned but
its value is never used
./HtmlRender.cs(64) error CS1502: The best overloaded method match for
`Gtk.Container.Add(Gtk.Widget)' has some invalid arguments
./HtmlRender.cs(64) error CS1503: Argument 1: Cannot convert from
`Gecko.WebControl' to `Gtk.Widget'
./HtmlRender.cs(64) error CS1501: No overload for method `Add' takes `1'
arguments
make[1]: [browser.exe] Error 1
make: [all-recursive] Error 1

than the bog-standard gtk-sharp, everything is from trunk.

TTFN

Paul

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

You're are om the 2.0 version of gecko-sharp, you need version 1.0.

Actually I was working on a patch to make monodoc work with gecko 2.0,
does anyone think that it would be worth while?
- raf

Mon, 2005-07-25 at 22:03 +0100, Paul wrote:
Hi,

I have both the bog standard and developer versions of gtk-sharp
installed (as I've been told that they are happy side by side). However,
when I try to compile mono-tools, I'm getting the following error which
prevents the build.

Any ideas what's going on?

./elabel.cs(74) warning CS0108: `ELabel.Ellipsize(Pango.Layout, string,
int, int, int)' hides inherited member `Gtk.Label.Ellipsize'. Use the
new keyword if hiding was intended
/ `Gtk.Label.Ellipsize' (name of
symbol related to previous warning
./browser.cs(1155) warning CS0219: The variable `a' is assigned but its
value is never used
./browser.cs(760) warning CS0436: Ignoring imported type
`Monodoc.CopyXmlNodeWriter' since the current assembly already has a
declaration with the same name
./XmlNodeWriter.cs(14): `Monodoc.CopyXmlNodeWriter' (name of symbol
related to previous warning
/ `Monodoc.CopyXmlNodeWriter' (name of
symbol related to previous warning
./browser.cs(764) warning CS0219: The variable `dd' is assigned but its
value is never used
./browser.cs(1027) warning CS0219: The variable `md' is assigned but its
value is never used
./browser.cs(1057) warning CS0219: The variable `service' is assigned
but its value is never used
./browser.cs(1406) warning CS0219: The variable `path' is assigned but
its value is never used
./browser.cs(1691) warning CS0219: The variable `found' is assigned but
its value is never used
./HtmlRender.cs(64) error CS1502: The best overloaded method match for
`Gtk.Container.Add(Gtk.Widget)' has some invalid arguments
./HtmlRender.cs(64) error CS1503: Argument 1: Cannot convert from
`Gecko.WebControl' to `Gtk.Widget'
./HtmlRender.cs(64) error CS1501: No overload for method `Add' takes `1'
arguments
make[1]: [browser.exe] Error 1
make: [all-recursive] Error 1

than the bog-standard gtk-sharp, everything is from trunk.

TTFN

Paul

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

Mon, 2005-07-25 at 14:06 -0700, Rafael Ferreira wrote:
You're are om the 2.0 version of gecko-sharp, you need version 1.0.

Am somewhat confused as to why people are even able to get past the
configure stage, seeing as we have:

PKG_CHECK_MDULES(GECKSHARP, gecko-sharp = 0.6)

Actually I was working on a patch to make monodoc work with gecko 2.0,
does anyone think that it would be worth while?

Monodoc uses gtk# 1.0 as of now. Moving to allow gecko# from head means
we have to move to gtk# 2.0

Before, we had a mode where mono-tools would build with whatever version
of gtk# was installed. However, this caused problems because:

* As most of us are developers, we have the 2.0 stuff installed.
That means that we compiled against 2.0. When it came time to
release, I had to figure out what dependencies were added
* It made the build system complicated (if gtk# 2.0 was installed
on the jail, rpms would depend on 2.0)

So, I reverted this mode and had mono-tools build with gtk# 1.0. You are
going to need gtk# 1.0 on your computer anyways; I can't see a reason to
bring back that patch.

Now, a patch to turn this obscure error into something sensible at
configure time would be great.
-- Ben

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

Hey,

7/26/05, Ben Maurer <bmaurer (AT) ximian (DOT) comwrote:
Mon, 2005-07-25 at 14:06 -0700, Rafael Ferreira wrote:
You're are om the 2.0 version of gecko-sharp, you need version 1.0.

Am somewhat confused as to why people are even able to get past the
configure stage, seeing as we have:

PKG_CHECK_MDULES(GECKSHARP, gecko-sharp = 0.6)

I'm also confused

Now, a patch to turn this obscure error into something sensible at
configure time would be great.

I've tried to reproduce the error but I was unable to do it. Just
wondering if Paul has done something tricky, like playing with the .pc
files or something like that. Any suggestions to track taht down?

Mario

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

yum install mono-complete
ends with: unsigned package
What should I do?
fedora core 4, installing mono 1.1.8.1
Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

Wed, 2005-07-27 at 00:12 +0300, Anton Andreev wrote:
yum install mono-complete

ends with: unsigned package

What should I do?

fedora core 4, installing mono 1.1.8.1

We don't sign our packages. You need to tell yum to disable its
signature check.
-- Ben

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

Hello,

7/27/05, Miguel de Icaza <miguel (AT) ximian (DOT) comwrote:
Hello Ben,

Am somewhat confused as to why people are even able to get past the
configure stage, seeing as we have:

PKG_CHECK_MDULES(GECKSHARP, gecko-sharp = 0.6)

thing that might be an issue is that I wasn't able to find a tarball
of gecko-sharp 0.6 anywhere on the Mono sites, and it's not even tagged
in SVN. I had to end up getting a 0.6 tarball from the Debian archives.
It would be good to store the tarball and link to it from somewhere so
long as it's being used by other packages.

Ben, where would this tarball be?

I'm not Ben but there is a tarball here:

The only problem I found there is that gecko-sharp.dll.config was
lacking a map to libgtkmozembed, something like:
<dllmap dll="gtkembedmoz" target="/"/>

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

If that's the case, then shouldn't the sample mono.repo on the website
() be modified to
have

gpgcheck=0

in each of the repository sections?
-fawad

Ben Maurer wrote:
Wed, 2005-07-27 at 00:12 +0300, Anton Andreev wrote:

>>yum install mono-complete
>>
>>ends with: unsigned package
>>
>>What should I do?
>>
>>fedora core 4, installing mono 1.1.8.1

We don't sign our packages. You need to tell yum to disable its
signature check.
-- Ben

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

Hi,

Wed, 2005-07-27 at 10:42 +0200, Mario Sopena wrote:
I'm not Ben but there is a tarball here:

Yeah, this is where we've been pointing people who build Beagle as well.

The only problem I found there is that gecko-sharp.dll.config was
lacking a map to libgtkmozembed, something like:
<dllmap dll="gtkembedmoz" target="/"/>

I think we're hacking LD_LIBRARY_PATH in our config file, so that people
can have one of mozilla, firefox, or thunderbird installed and have it
work, without needing gecko-sharp to depend on one explicitly. But I
definitely wouldn't object to this being moved into gecko-sharp proper.

Joe

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

Wed, 2005-07-27 at 11:21 -0400, Joe Shaw wrote:
Hi,

Wed, 2005-07-27 at 10:42 +0200, Mario Sopena wrote:
I'm not Ben but there is a tarball here:

Yeah, this is where we've been pointing people who build Beagle as well.

The only problem I found there is that gecko-sharp.dll.config was
lacking a map to libgtkmozembed, something like:
<dllmap dll="gtkembedmoz" target="/"/>

I think we're hacking LD_LIBRARY_PATH in our config file, so that people
can have one of mozilla, firefox, or thunderbird installed and have it
work, without needing gecko-sharp to depend on one explicitly. But I
definitely wouldn't object to this being moved into gecko-sharp proper.

Yeah, monodevelop does something similar. In fact, tseng says that he
has a patch in Ubuntu to make a change like this.

We distribute gecko# as a noarch/non-distro-specific library though, so
we can't really modify the target to something specific. Even if we did,
that wouldn't allow us to do "mozilla or thunderbird".

Maybe, since we want to encourage people to use Gecko# and make it easy
to run samples like the browser thingy, we could special case it in the
runtime. I really hate doing this (it's a nasty hack), but it's the only
way I see short of forcing everyone to figure out wha to do in a wrapper
script.
-- Ben

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

Hi,
You're absolutely right. Per the yum.conf man page
(),
the setting for gpgcheck in [main] defines the default. At least RHEL 4
and FC 4 ship with gpgcheck=1 in [main].

Regards
-fawad

Rafael Teixeira wrote:
Hi Fawad,

Maybe yum changed the default for this setting on recent versions, or
the global yum.conf has been changed by the user (Anton) to turn it on
by default.

This gpgcheck setting is omitted in my copy of mono.repo (as the one
you linked) and yum 2.2.1 (FC3) never presented me such message as
told by Anton: "unsigned package
".

Anyway, I do think mono.repo should be configured as you suggest to
make things 'explicitly' work as intended.

:)

7/27/05, Fawad Halim <fawad (AT) fawad (DOT) netwrote:

>>If that's the case, then shouldn't the sample mono.repo on the website
>>() be modified to
>>have
>>
>>gpgcheck=0
>>
>>in each of the repository sections?
>>
fawad
>>
>>Ben Maurer wrote:
>>
Wed, 2005-07-27 at 00:12 +0300, Anton Andreev wrote:

yum install mono-complete

ends with: unsigned package

What should I do?

fedora core 4, installing mono 1.1.8.1

We don't sign our packages. You need to tell yum to disable its
signature check.

Ben
>>
>>
>>Mono-devel-list mailing list
>>Mono-devel-list (AT) lists (DOT) ximian.com
>>
>>

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

yes, you were right. thanks.

Hi,
You're absolutely right. Per the yum.conf man page
(),
the setting for gpgcheck in [main] defines the default. At least RHEL 4
and FC 4 ship with gpgcheck=1 in [main].

Regards
-fawad

Rafael Teixeira wrote:
>Hi Fawad,
>>
>Maybe yum changed the default for this setting on recent versions, or
>the global yum.conf has been changed by the user (Anton) to turn it on
>by default.
>>
>This gpgcheck setting is omitted in my copy of mono.repo (as the one
>you linked) and yum 2.2.1 (FC3) never presented me such message as
>told by Anton: "unsigned package
>".
>>
>Anyway, I do think mono.repo should be configured as you suggest to
>make things 'explicitly' work as intended.
>>
>:)
>>
>7/27/05, Fawad Halim <fawad (AT) fawad (DOT) netwrote:
>>
If that's the case, then shouldn't the sample mono.repo on the website
() be modified to
have

gpgcheck=0

in each of the repository sections?

fawad

Ben Maurer wrote:

Wed, 2005-07-27 at 00:12 +0300, Anton Andreev wrote:

yum install mono-complete

ends with: unsigned package

What should I do?

fedora core 4, installing mono 1.1.8.1

We don't sign our packages. You need to tell yum to disable its
signature check.

Ben

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com


>>
>>
>>

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com

--

Mono-devel-list mailing list
Mono-devel-list (AT) lists (DOT) ximian.com