Re: [Mono-dev] No works application

[Rolf Bjarne Kvinge]

>From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of LB Audio
Uchoa NET
>Sent: sábado, 21 de abril de 2007 3:29
>To: mono-devel-list@lists.ximian.com
>Subject: [Mono-dev] No works application
>
>Here simple code...
> 
>More... problem is configuring mono in my new computer.
>In another computer this worked normal.
> 
>http://www.vivaolinux.com.br/imagens/artigos/comunidade/OlaMundo.tar.gz
> 
>Which mono version to use?  
>What Linux Distro to use?
> 
>Thanks...

This Works for me with SVN, so you'll have to use the latest version of
mono-basic (you can download the latest mono-basic package here:
http://mono.ximian.com/monobuild/preview/download-preview/).
Any linux distro should do.

Rolf

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] Semaphores problem with latest mono 1.2.4 svn...

[Hubert FONGARNAND]

I've tried to upgrade my beta server with mono 1.2.4 from svn from
1.2.3.50

I launch my mod_mono_servers and i get semaphore errors problem...

When i launch webpage (or when i launch xsp)

I never had such problems before...
was passiert???

Sincerely

Hubert FONGARNAND



[EMAIL PROTECTED] CASServer]$ xsp

** ERROR **: shm_semaphores_init: semget error: Aucun espace disponible sur le 
périphérique.  Try deleting some semaphores with ipcs and ipcrm
or increase the maximum number of semaphore in the system.
aborting...
Stacktrace:


Native stacktrace:

/usr/bin/mono [0x8154055]
[0xe440]
/lib/tls/libc.so.6(abort+0xe9) [0x2c1199]
/usr/lib/libglib-2.0.so.0(g_log+0) [0x5ffebe]
/usr/lib/libglib-2.0.so.0(g_log+0x32) [0x5ffef0]
/usr/bin/mono [0x8106a2c]
/usr/bin/mono [0x80fffae]
/usr/bin/mono(mono_once+0xdc) [0x80f6068]
/usr/bin/mono [0x8100594]
/usr/bin/mono [0x80fb9c8]
/usr/bin/mono [0x80defbc]
/usr/bin/mono(mono_runtime_init+0x21) [0x80b262d]
/usr/bin/mono [0x8140eaa]
/usr/bin/mono(mono_main+0x2a3) [0x8058293]
/usr/bin/mono [0x8057ba7]
/lib/tls/libc.so.6(__libc_start_main+0xd3) [0x2ace23]
/usr/bin/mono [0x8057b09]

Debug info from gdb:



=
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=

Abandon



[EMAIL PROTECTED] CASServer]$ ipcs

-- Segment de mémoire partagé 
clé   shmid  propriétaire perms  octets nattch états
0x 65536  hubert600393216 2  dest
0x 98305  hubert600196608 2  dest
0x 131074 hubert600393216 2  dest
0x 163843 hubert600196608 2  dest
0x 196612 hubert600393216 2  dest
0x 229381 hubert600393216 2  dest
0x 262150 hubert600393216 2  dest
0x 294919 hubert600393216 2  dest
0x 327688 hubert600393216 2  dest
0x 360457 hubert600393216 2  dest
0x 393226 hubert600196608 2  dest
0x 425995 hubert600393216 2  dest
0x 458764 hubert600393216 2  dest
0x 491533 hubert600196608 2  dest
0x 557070 hubert600393216 2  dest

-- Tableaux de sémaphores 
clé   semid  propriétaire perms  nsems
0x4d00184c 0  hubert6008
0x4d00184d 65537  hubert6008
0x 819202 hubert6001
0x 851971 hubert6001
0x4d00185d 884740 hubert6008
0x4d00184e 196613 hubert6008
0x4d00184f 229382 hubert6008
0x4d001850 262151 hubert6008
0x4d001851 294920 hubert6008
0x4d001852 327689 hubert6008
0x4d001853 360458 hubert6008
0x4d001854 393227 hubert6008
0x4d001855 425996 hubert6008
0x4d001856 458765 hubert6008
0x4d001857 491534 hubert6008
0x4d001858 524303 hubert6008
0x4d001859 557072 hubert6008
0x4d00185a 589841 hubert6008
0x4d00185b 622610 hubert6008
0x4d00185c 655379 hubert6008
0x4d00185e 917524 hubert6008
0x4d00185f 950293 hubert6008
0x4d001860 983062 hubert6008
0x4d001861 1015831hubert6008
0x4d001862 1048600hubert6008
0x4d001863 1081369hubert6008
0x4d001864 1114138hubert6008
0x4d001865 1146907hubert6008
0x4d001866 1179676hubert6008
0x4d001867 1212445hubert6008
0x4d001868 1245214hubert6008
0x4d001869 1277983hubert6008
0x4d00186a 1310752hubert6008
0x4d00186b 1343521hubert6008
0x4d00186c 1376290hubert6008
0x4d00186d 1409059hubert6008
0x4d00186e 1441828hubert6008
0x4d00186f 1474597hubert6008
0x4d001870 1507366hubert6008
0x4d001871 1540135hubert6008
0x4d001872 1572904hubert6008
0x4d001873 1605673hubert6008
0x4d001874 1638442hubert6008
0x4d001875 1671211hubert6008
0x4d001876 1703980hubert6008
0x4d001877 1736749hubert6008
0x4d001878 1769518hubert600  

Re: [Mono-dev] Call for testing - HttpParamsCollection bug

[Joshua Tauberer]

Miguel de Icaza wrote:
>> I also encountered a bug in the new HttpParamsCollection, an 
>> IndexOutOfRange because of a failure to account for empty-string param 
>> values.  Patch attached.  Let me know if it's ok to commit.
> 
> It is OK to commit.
> 
> Could you also provide an nunit test case for this regression?

Actually, no.  My source tree is messed up or something, because I keep 
getting:

error CS8019: Can not find the core constructor for type 
`ParamArrayAttribute'

while making corlib.  So I can't compile and test anything at the 
moment.  I actually can't compile the patch I sent earlier, for that 
mattter.  Would someone else mind committing it so I don't commit 
something stupid that doesn't compile, even if it's a ridiculously tiny 
patch? :)

-- 
- Josh Tauberer

http://razor.occams.info

"Yields falsehood when preceded by its quotation!  Yields
falsehood when preceded by its quotation!" Achilles to
Tortoise (in "Gödel, Escher, Bach" by Douglas Hofstadter)
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono 1.2.4, preparation rituals.

[Jonathan Chambers]

Hello,
 Getting the fix for bug 80969 (Generic multidimensional arrays) into
1.2.4 would be very helpful if possible.

Thanks,
Jonathan

On 4/17/07, Miguel de Icaza <[EMAIL PROTECTED]> wrote:


Hello,

I would like to prepare a release, I think that we should branch the
tree on Thursday, hopefully that gives us time to do a first pass at
tarballs and packages.

As usual, please send me highlights that you believe should go into
the release notes for Mono 1.2.4.

We then do a week of testing on these packages, do fixes and
backports of fixes of anything that we regressed during this week and
issue a final 1.2.4 on April 27th or so.

Thomas is joining us this week, so things might start to look
different as he starts to take over our QA role.

Miguel.

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Jonathan Chambers]

At this point, the runtime should compile on win64 in VS2005. It won't link
as neither glib nor libgc are ported to win64. I have locally modified
versions of each that I am working on, but am not done yet. After all of
that is complete, I am sure the JIT will need at least some minor
adjustments; calling convention comes to mind and I am sure there are other
things of which I am not currently aware.

Does anyone know the status/intention of gcc on win64?

Thanks,
Jonathan

On 4/22/07, Kornél Pál <[EMAIL PROTECTED]> wrote:


Hi,

Earlier there were some patches and posts regarding Windows/x64 support on
the list. Could someone please let me know the current status of
Windows/x64?

Kornél

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Jonathan Chambers]

Actually, there is some effort already to get glib building under win64. See
thread here:
http://mail.gnome.org/archives/gtk-devel-list/2007-March/msg6.html

I am not sure how soon any patches will make it into glib, but there is some
effort. I initially thought eglib would be easier, but have since changed my
mind ;-). A glib port will be used/appreciated/maintained by a wider
community, and it has already been ported to build on Win32. eglib would
need ported to win32, and not just win32, but msvc. This was not trivial
when I tried, and I doubt mono wants all the #ifdef's and changes necessary
to get it working. Plus, glib is tested alot more than eglib.

A colleague of mine already has a win64 build of glib, and is working on
cleaning up his changes; again, I have no clue of when such changes
could/would be put into glib.

Thanks,
Jonathan

On 4/23/07, Michael Jerris <[EMAIL PROTECTED]> wrote:


 Seems like a good time to ask about the status of windows support (32 and
64) and/or msvc support for eglib.  It may be a more worthwhile use of time
to finish that work than to work on finishing porting glib.  I would be
happy to lend a hand in this process if there is some sort of direction on
the best way to go forward on this.



Mike




  --

*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Jonathan Chambers
*Sent:* Monday, April 23, 2007 10:14 AM
*To:* Kornél Pál
*Cc:* mono-devel-list@lists.ximian.com
*Subject:* Re: [Mono-dev] Mono on Windows/x64



At this point, the runtime should compile on win64 in VS2005. It won't
link as neither glib nor libgc are ported to win64. I have locally modified
versions of each that I am working on, but am not done yet. After all of
that is complete, I am sure the JIT will need at least some minor
adjustments; calling convention comes to mind and I am sure there are other
things of which I am not currently aware.

Does anyone know the status/intention of gcc on win64?

Thanks,
Jonathan

On 4/22/07, *Kornél Pál* < [EMAIL PROTECTED]> wrote:

Hi,

Earlier there were some patches and posts regarding Windows/x64 support on

the list. Could someone please let me know the current status of
Windows/x64?

Kornél

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list



___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Michael Jerris]

Seems like a good time to ask about the status of windows support (32 and 64) 
and/or msvc support for eglib.  It may be a more worthwhile use of time to 
finish that work than to work on finishing porting glib.  I would be happy to 
lend a hand in this process if there is some sort of direction on the best way 
to go forward on this.

 

Mike

 

 



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Chambers
Sent: Monday, April 23, 2007 10:14 AM
To: Kornél Pál
Cc: mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] Mono on Windows/x64

 

At this point, the runtime should compile on win64 in VS2005. It won't link as 
neither glib nor libgc are ported to win64. I have locally modified versions of 
each that I am working on, but am not done yet. After all of that is complete, 
I am sure the JIT will need at least some minor adjustments; calling convention 
comes to mind and I am sure there are other things of which I am not currently 
aware. 

Does anyone know the status/intention of gcc on win64?

Thanks,
Jonathan

On 4/22/07, Kornél Pál < [EMAIL PROTECTED]  > wrote:

Hi,

Earlier there were some patches and posts regarding Windows/x64 support on 
the list. Could someone please let me know the current status of
Windows/x64?

Kornél

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

 

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Semaphores problem with latest mono 1.2.4 svn...

[Miguel de Icaza]

Hello,

> I launch my mod_mono_servers and i get semaphore errors problem...

This is caused merely because you have had many abnormal program
terminations, so there are many semaphores lost.

Remove those semaphores with ipcrm -s  where NNN is the semaphore ID
you listed.

> When i launch webpage (or when i launch xsp)
> 
> I never had such problems before...
> was passiert???
> 
> Sincerely
> 
> Hubert FONGARNAND
> 
> 
> [EMAIL PROTECTED] CASServer]$ xsp
> 
> ** ERROR **: shm_semaphores_init: semget error: Aucun espace disponible sur 
> le périphérique.  Try deleting some semaphores with ipcs and ipcrm
> or increase the maximum number of semaphore in the system.
> aborting...
> Stacktrace:
> 
> 
> Native stacktrace:
> 
> /usr/bin/mono [0x8154055]
> [0xe440]
> /lib/tls/libc.so.6(abort+0xe9) [0x2c1199]
> /usr/lib/libglib-2.0.so.0(g_log+0) [0x5ffebe]
> /usr/lib/libglib-2.0.so.0(g_log+0x32) [0x5ffef0]
> /usr/bin/mono [0x8106a2c]
> /usr/bin/mono [0x80fffae]
> /usr/bin/mono(mono_once+0xdc) [0x80f6068]
> /usr/bin/mono [0x8100594]
> /usr/bin/mono [0x80fb9c8]
> /usr/bin/mono [0x80defbc]
> /usr/bin/mono(mono_runtime_init+0x21) [0x80b262d]
> /usr/bin/mono [0x8140eaa]
> /usr/bin/mono(mono_main+0x2a3) [0x8058293]
> /usr/bin/mono [0x8057ba7]
> /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x2ace23]
> /usr/bin/mono [0x8057b09]
> 
> Debug info from gdb:
> 
> 
> 
> =
> Got a SIGABRT while executing native code. This usually indicates
> a fatal error in the mono runtime or one of the native libraries
> used by your application.
> =
> 
> Abandon
> 
> 
> 
> [EMAIL PROTECTED] CASServer]$ ipcs
> 
> -- Segment de mémoire partagé 
> clé   shmid  propriétaire perms  octets nattch états
> 0x 65536  hubert600393216 2  dest
> 0x 98305  hubert600196608 2  dest
> 0x 131074 hubert600393216 2  dest
> 0x 163843 hubert600196608 2  dest
> 0x 196612 hubert600393216 2  dest
> 0x 229381 hubert600393216 2  dest
> 0x 262150 hubert600393216 2  dest
> 0x 294919 hubert600393216 2  dest
> 0x 327688 hubert600393216 2  dest
> 0x 360457 hubert600393216 2  dest
> 0x 393226 hubert600196608 2  dest
> 0x 425995 hubert600393216 2  dest
> 0x 458764 hubert600393216 2  dest
> 0x 491533 hubert600196608 2  dest
> 0x 557070 hubert600393216 2  dest
> 
> -- Tableaux de sémaphores 
> clé   semid  propriétaire perms  nsems
> 0x4d00184c 0  hubert6008
> 0x4d00184d 65537  hubert6008
> 0x 819202 hubert6001
> 0x 851971 hubert6001
> 0x4d00185d 884740 hubert6008
> 0x4d00184e 196613 hubert6008
> 0x4d00184f 229382 hubert6008
> 0x4d001850 262151 hubert6008
> 0x4d001851 294920 hubert6008
> 0x4d001852 327689 hubert6008
> 0x4d001853 360458 hubert6008
> 0x4d001854 393227 hubert6008
> 0x4d001855 425996 hubert6008
> 0x4d001856 458765 hubert6008
> 0x4d001857 491534 hubert6008
> 0x4d001858 524303 hubert6008
> 0x4d001859 557072 hubert6008
> 0x4d00185a 589841 hubert6008
> 0x4d00185b 622610 hubert6008
> 0x4d00185c 655379 hubert6008
> 0x4d00185e 917524 hubert6008
> 0x4d00185f 950293 hubert6008
> 0x4d001860 983062 hubert6008
> 0x4d001861 1015831hubert6008
> 0x4d001862 1048600hubert6008
> 0x4d001863 1081369hubert6008
> 0x4d001864 1114138hubert6008
> 0x4d001865 1146907hubert6008
> 0x4d001866 1179676hubert6008
> 0x4d001867 1212445hubert6008
> 0x4d001868 1245214hubert6008
> 0x4d001869 1277983hubert6008
> 0x4d00186a 1310752hubert6008
> 0x4d00186b 1343521hubert6008
> 0x4d00186c 1376290hubert6008
> 0x4d00186d 1409059hubert6008
> 0x4d00186e 1441828hubert6008
> 0x4d00186f 1474597hubert6008
> 0x4d001870 1507366hubert600 

Re: [Mono-dev] Call for testing - HttpParamsCollection bug

[Miguel de Icaza]

Hello,

> > It is OK to commit.
> > 
> > Could you also provide an nunit test case for this regression?
> 
> Actually, no.  My source tree is messed up or something, because I keep 
> getting:
> 
> error CS8019: Can not find the core constructor for type 
> `ParamArrayAttribute'

This has been fixed.

> while making corlib.  So I can't compile and test anything at the 
> moment.  I actually can't compile the patch I sent earlier, for that 
> mattter.  Would someone else mind committing it so I don't commit 
> something stupid that doesn't compile, even if it's a ridiculously tiny 
> patch? :)

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Miguel de Icaza]

Hello,

> I am not sure how soon any patches will make it into glib, but there
> is some effort. I initially thought eglib would be easier, but have
> since changed my mind ;-). A glib port will be
> used/appreciated/maintained by a wider community, and it has already
> been ported to build on Win32. eglib would need ported to win32, and
> not just win32, but msvc. This was not trivial when I tried, and I
> doubt mono wants all the #ifdef's and changes necessary to get it
> working. Plus, glib is tested alot more than eglib. 

We are going to drop glib and move to eglib in the future anyways.

In addition, eglib is such a small library that am curious as to what
you think would require all that work to port eglib to Win64, it does
not seem that difficult, and the code base is very small.

Miguel.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Miguel de Icaza]

Hello,

A small follow up, the tricky bits for porting to Win64 would be:

* gfile.c 

* gspawn.c

Possibly review the typedefs and move some typedefs from glib.h into
eglib-config.h.in as well as guessing a few values for eglib-config.

Miguel.

> I am not sure how soon any patches will make it into glib, but there
> is some effort. I initially thought eglib would be easier, but have
> since changed my mind ;-). A glib port will be
> used/appreciated/maintained by a wider community, and it has already
> been ported to build on Win32. eglib would need ported to win32, and
> not just win32, but msvc. This was not trivial when I tried, and I
> doubt mono wants all the #ifdef's and changes necessary to get it
> working. Plus, glib is tested alot more than eglib. 
> 
> A colleague of mine already has a win64 build of glib, and is working
> on cleaning up his changes; again, I have no clue of when such changes
> could/would be put into glib.
> 
> Thanks,
> Jonathan
> 
> On 4/23/07, Michael Jerris <[EMAIL PROTECTED]> wrote:
> Seems like a good time to ask about the status of windows
> support (32 and 64) and/or msvc support for eglib.  It may be
> a more worthwhile use of time to finish that work than to work
> on finishing porting glib.  I would be happy to lend a hand in
> this process if there is some sort of direction on the best
> way to go forward on this.
> 
>  
> 
> Mike
> 
>  
> 
>  
> 
>
> __
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Jonathan Chambers
> Sent: Monday, April 23, 2007 10:14 AM
> To: Kornél Pál
> Cc: mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] Mono on Windows/x64
> 
> 
>  
> 
> At this point, the runtime should compile on win64 in VS2005.
> It won't link as neither glib nor libgc are ported to win64. I
> have locally modified versions of each that I am working on,
> but am not done yet. After all of that is complete, I am sure
> the JIT will need at least some minor adjustments; calling
> convention comes to mind and I am sure there are other things
> of which I am not currently aware. 
> 
> Does anyone know the status/intention of gcc on win64?
> 
> Thanks,
> Jonathan
> 
> On 4/22/07, Kornél Pál <[EMAIL PROTECTED]> wrote:
> 
> Hi,
> 
> Earlier there were some patches and posts regarding
> Windows/x64 support on 
> the list. Could someone please let me know the current status
> of
> Windows/x64?
> 
> Kornél
> 
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 
> 
>  
> 
> 
> 
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Jonathan Chambers]

Hello,

On 4/23/07, Miguel de Icaza <[EMAIL PROTECTED]> wrote:


Hello,

> I am not sure how soon any patches will make it into glib, but there
> is some effort. I initially thought eglib would be easier, but have
> since changed my mind ;-). A glib port will be
> used/appreciated/maintained by a wider community, and it has already
> been ported to build on Win32. eglib would need ported to win32, and
> not just win32, but msvc. This was not trivial when I tried, and I
> doubt mono wants all the #ifdef's and changes necessary to get it
> working. Plus, glib is tested alot more than eglib.

We are going to drop glib and move to eglib in the future anyways.



Knowing this previously would have helped ;-). I have got conflicting advice
in the past about whether glib or eglib would be the best approach.

In addition, eglib is such a small library that am curious as to what

you think would require all that work to port eglib to Win64, it does
not seem that difficult, and the code base is very small.



I'll look at the progress I made previously locally. I think the biggest
issues were msvc issues like handling varargs differently than gcc (adding a
decent number of #ifdefs), and lots of string conversions between Windows
API (Unicode) and glib (utf-8). I'm willing to work on this again, with help
from anyone else, if this is the future direction of mono.

Miguel.



Thanks,
Jonathan
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Michael Jerris]

Msvc (at least 2005), gcc, and sun studio at least all support __VA_ARGS__ for 
var args macros.  It is part of c99.  This should work without any ifdefs.  The 
code below (from an unrelated project) compiles fine on all of those compilers. 
 Are there any non-c99 compliant compilers in the targets needed (other than 
msvc 2005 of course, where at least this works fine?)

 

Mike

 

#define say_file(...) {\

char tmp[80];\

switch_status_t status;\

snprintf(tmp, sizeof(tmp), __VA_ARGS__);\

if ((status = switch_ivr_play_file(session, NULL, tmp, args)) != 
SWITCH_STATUS_SUCCESS){ \

  return status;\

}\

if 
(!switch_channel_ready(switch_core_session_get_channel(session))) {\

  return SWITCH_STATUS_FALSE;\

}}\

 

 

 



From: Jonathan Chambers [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 23, 2007 11:29 AM
To: Miguel de Icaza
Cc: Michael Jerris; Kornél Pál; mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] Mono on Windows/x64

 

Hello,

On 4/23/07, Miguel de Icaza <[EMAIL PROTECTED] > wrote:

Hello,

> I am not sure how soon any patches will make it into glib, but there
> is some effort. I initially thought eglib would be easier, but have
> since changed my mind ;-). A glib port will be
> used/appreciated/maintained by a wider community, and it has already
> been ported to build on Win32. eglib would need ported to win32, and
> not just win32, but msvc. This was not trivial when I tried, and I 
> doubt mono wants all the #ifdef's and changes necessary to get it
> working. Plus, glib is tested alot more than eglib.

We are going to drop glib and move to eglib in the future anyways.


Knowing this previously would have helped ;-). I have got conflicting advice in 
the past about whether glib or eglib would be the best approach.

 

In addition, eglib is such a small library that am curious as to what
you think would require all that work to port eglib to Win64, it does
not seem that difficult, and the code base is very small.


I'll look at the progress I made previously locally. I think the biggest issues 
were msvc issues like handling varargs differently than gcc (adding a decent 
number of #ifdefs), and lots of string conversions between Windows API 
(Unicode) and glib (utf-8). I'm willing to work on this again, with help from 
anyone else, if this is the future direction of mono. 

 

Miguel.



Thanks,
Jonathan 

 

 

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Andreas Färber]

Am 23.04.2007 um 17:25 schrieb Miguel de Icaza:

> A small follow up, the tricky bits for porting to Win64 would be:
>
>   * gfile.c
>
>   * gspawn.c
>
> Possibly review the typedefs and move some typedefs from glib.h  
> into
> eglib-config.h.in as well as guessing a few values for eglib-config.

I fixed a build problem with ABS in eglib's mono-ehash.c and will  
post a patch this evening if noone else is quicker.

Andreas
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Miguel de Icaza]

Hey,

> Knowing this previously would have helped ;-). I have got conflicting
> advice in the past about whether glib or eglib would be the best
> approach.

Well, we were developing it ;-)

But our goal is to drop glib and get back some of the memory usage we
have been using.   As with every large change, this is not something we
want to do in the incremental 1.2.xx releases.

Miguel.
> 
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Andreas Färber]

> We are going to drop glib and move to eglib in the future anyways.
>
> I'm willing to work on this again, with help from anyone else, if  
> this is the future direction of mono.

I made some local additions to eglib for ppc64 (e.g. g_strndup), I'm  
just not sure how to correctly ifdef it. Probably a lot of additions  
to configure.in will be needed but I don't know how.

Andreas
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Michael Jerris]

Step 1.  Attached patch for review, should have no affect at all on non msvc 
build.  Resolves all build errors on msvc 2005.  Still needs implementations 
for quite a few things on msvc, and windows in general, this patch makes no 
effort to address those.  Note several things throughout marked FIXME that need 
to be looked at when the implementation is addressed.

Mike



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:mono-devel-list-
> [EMAIL PROTECTED] On Behalf Of Miguel de Icaza
> Sent: Monday, April 23, 2007 12:06 PM
> To: Jonathan Chambers
> Cc: Kornél Pál; mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] Mono on Windows/x64
> 
> Hey,
> 
> > Knowing this previously would have helped ;-). I have got conflicting
> > advice in the past about whether glib or eglib would be the best
> > approach.
> 
> Well, we were developing it ;-)
> 
> But our goal is to drop glib and get back some of the memory usage we
> have been using.   As with every large change, this is not something we
> want to do in the incremental 1.2.xx releases.
> 
> Miguel.
> >
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list


eglibmsvc2005compile.diff
Description: eglibmsvc2005compile.diff
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Jonathan Chambers]

Michael,
This looks good; you may want to put the vsproj in mono/msvc since I
stuck all other VS related files in there. There is some warnings that need
fixed (passing chars to Unicode routines), and the issues you mentioned, but
this should help alot in getting mono on Win64. If eglib is working, I can
build mono with no gc initially to get any other issues worked out. I think
my colleage has the beta version libgc 7 working. I can try with that as
well.

Thanks,
Jonathan

On 4/23/07, Michael Jerris <[EMAIL PROTECTED]> wrote:


Step 1.  Attached patch for review, should have no affect at all on non
msvc build.  Resolves all build errors on msvc 2005.  Still needs
implementations for quite a few things on msvc, and windows in general, this
patch makes no effort to address those.  Note several things throughout
marked FIXME that need to be looked at when the implementation is addressed.

Mike



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:mono-devel-list-
> [EMAIL PROTECTED] On Behalf Of Miguel de Icaza
> Sent: Monday, April 23, 2007 12:06 PM
> To: Jonathan Chambers
> Cc: Kornél Pál; mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] Mono on Windows/x64
>
> Hey,
>
> > Knowing this previously would have helped ;-). I have got conflicting
> > advice in the past about whether glib or eglib would be the best
> > approach.
>
> Well, we were developing it ;-)
>
> But our goal is to drop glib and get back some of the memory usage we
> have been using.   As with every large change, this is not something we
> want to do in the incremental 1.2.xx releases.
>
> Miguel.
> >
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Michael Jerris]

Agreed, still tons to do... the location of the vcproj makes no difference to 
me, can someone confirm where you want it and I'll roll another project file in 
the right location.  

 



From: Jonathan Chambers [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 23, 2007 1:22 PM
To: Michael Jerris
Cc: mono-devel-list@lists.ximian.com; Kornél Pál; Miguel de Icaza
Subject: Re: [Mono-dev] Mono on Windows/x64

 

Michael,
 This looks good; you may want to put the vsproj in mono/msvc since I stuck 
all other VS related files in there. There is some warnings that need fixed 
(passing chars to Unicode routines), and the issues you mentioned, but this 
should help alot in getting mono on Win64. If eglib is working, I can build 
mono with no gc initially to get any other issues worked out. I think my 
colleage has the beta version libgc 7 working. I can try with that as well. 

Thanks,
Jonathan

On 4/23/07, Michael Jerris <[EMAIL PROTECTED]> wrote:

Step 1.  Attached patch for review, should have no affect at all on non msvc 
build.  Resolves all build errors on msvc 2005.  Still needs implementations 
for quite a few things on msvc, and windows in general, this patch makes no 
effort to address those.  Note several things throughout marked FIXME that need 
to be looked at when the implementation is addressed. 

Mike



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:mono-devel-list- 
> [EMAIL PROTECTED] On Behalf Of Miguel de Icaza
> Sent: Monday, April 23, 2007 12:06 PM
> To: Jonathan Chambers
> Cc: Kornél Pál; mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] Mono on Windows/x64
>
> Hey,
>
> > Knowing this previously would have helped ;-). I have got conflicting
> > advice in the past about whether glib or eglib would be the best 
> > approach.
>
> Well, we were developing it ;-)
>
> But our goal is to drop glib and get back some of the memory usage we
> have been using.   As with every large change, this is not something we 
> want to do in the incremental 1.2.xx releases.
>
> Miguel.
> >
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

 

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Jonathan Chambers]

Michael,
I get the following compiler error building with gcc:

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I. -Wall -Werror -D_FORTIFY_SOURCE=2 -g
-O0 -D_GNU_SOURCE -MT libeglib_la-gstr.lo -MD -MP -MF .deps/libeglib_la-
gstr.Tpo -c gstr.c  -fPIC -DPIC -o .libs/libeglib_la-gstr.o
gstr.c: In function 'g_filename_to_uri':
gstr.c:429: error: syntax error before ')' token
cc1: warnings being treated as errors
gstr.c:457: warning: control reaches end of non-void function
gstr.c: In function 'g_filename_from_uri':
gstr.c:482: error: syntax error before ')' token
gstr.c:517: warning: control reaches end of non-void function
make[2]: *** [libeglib_la-gstr.lo] Error 1
make[2]: Leaving directory `/home/jschambe/monosvn/mono/eglib/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/jschambe/monosvn/mono/eglib'
make: *** [all] Error 2

- Jonathan

On 4/23/07, Michael Jerris <[EMAIL PROTECTED]> wrote:


 Agreed, still tons to do… the location of the vcproj makes no difference
to me, can someone confirm where you want it and I'll roll another project
file in the right location.


  --

*From:* Jonathan Chambers [mailto:[EMAIL PROTECTED]
*Sent:* Monday, April 23, 2007 1:22 PM
*To:* Michael Jerris
*Cc:* mono-devel-list@lists.ximian.com; Kornél Pál; Miguel de Icaza
*Subject:* Re: [Mono-dev] Mono on Windows/x64



Michael,
 This looks good; you may want to put the vsproj in mono/msvc since I
stuck all other VS related files in there. There is some warnings that need
fixed (passing chars to Unicode routines), and the issues you mentioned, but
this should help alot in getting mono on Win64. If eglib is working, I can
build mono with no gc initially to get any other issues worked out. I think
my colleage has the beta version libgc 7 working. I can try with that as
well.

Thanks,
Jonathan

On 4/23/07, *Michael Jerris* <[EMAIL PROTECTED]> wrote:

Step 1.  Attached patch for review, should have no affect at all on non
msvc build.  Resolves all build errors on msvc 2005.  Still needs
implementations for quite a few things on msvc, and windows in general, this
patch makes no effort to address those.  Note several things throughout
marked FIXME that need to be looked at when the implementation is addressed.


Mike



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:mono-devel-list-
> [EMAIL PROTECTED] On Behalf Of Miguel de Icaza
> Sent: Monday, April 23, 2007 12:06 PM
> To: Jonathan Chambers
> Cc: Kornél Pál; mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] Mono on Windows/x64
>
> Hey,
>
> > Knowing this previously would have helped ;-). I have got conflicting
> > advice in the past about whether glib or eglib would be the best
> > approach.
>
> Well, we were developing it ;-)
>
> But our goal is to drop glib and get back some of the memory usage we
> have been using.   As with every large change, this is not something we
> want to do in the incremental 1.2.xx releases.
>
> Miguel.
> >
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list



___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Michael Jerris]

Fixes gcc compile error below, and moves project file as requested.

 



From: Jonathan Chambers [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 23, 2007 1:45 PM
To: Michael Jerris
Cc: mono-devel-list@lists.ximian.com; Kornél Pál; Miguel de Icaza
Subject: Re: [Mono-dev] Mono on Windows/x64

 

Michael,
 I get the following compiler error building with gcc:

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I. -Wall -Werror -D_FORTIFY_SOURCE=2 -g -O0 
-D_GNU_SOURCE -MT libeglib_la-gstr.lo -MD -MP -MF .deps/libeglib_la- gstr.Tpo 
-c gstr.c  -fPIC -DPIC -o .libs/libeglib_la-gstr.o
gstr.c: In function 'g_filename_to_uri':
gstr.c:429: error: syntax error before ')' token
cc1: warnings being treated as errors
gstr.c :457: warning: control reaches end of non-void function
gstr.c: In function 'g_filename_from_uri':
gstr.c:482: error: syntax error before ')' token
gstr.c:517: warning: control reaches end of non-void function 
make[2]: *** [libeglib_la-gstr.lo] Error 1
make[2]: Leaving directory `/home/jschambe/monosvn/mono/eglib/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/jschambe/monosvn/mono/eglib' 
make: *** [all] Error 2

- Jonathan

On 4/23/07, Michael Jerris <[EMAIL PROTECTED]> wrote:

Agreed, still tons to do... the location of the vcproj makes no difference to 
me, can someone confirm where you want it and I'll roll another project file in 
the right location.  

 



From: Jonathan Chambers [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 23, 2007 1:22 PM
To: Michael Jerris
Cc: mono-devel-list@lists.ximian.com; Kornél Pál; Miguel de Icaza


Subject: Re: [Mono-dev] Mono on Windows/x64

 

Michael,
 This looks good; you may want to put the vsproj in mono/msvc since I stuck 
all other VS related files in there. There is some warnings that need fixed 
(passing chars to Unicode routines), and the issues you mentioned, but this 
should help alot in getting mono on Win64. If eglib is working, I can build 
mono with no gc initially to get any other issues worked out. I think my 
colleage has the beta version libgc 7 working. I can try with that as well. 

Thanks,
Jonathan

On 4/23/07, Michael Jerris <[EMAIL PROTECTED]> wrote:

Step 1.  Attached patch for review, should have no affect at all on non msvc 
build.  Resolves all build errors on msvc 2005.  Still needs implementations 
for quite a few things on msvc, and windows in general, this patch makes no 
effort to address those.  Note several things throughout marked FIXME that need 
to be looked at when the implementation is addressed. 

Mike



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:mono-devel-list- 
> [EMAIL PROTECTED] On Behalf Of Miguel de Icaza
> Sent: Monday, April 23, 2007 12:06 PM
> To: Jonathan Chambers
> Cc: Kornél Pál; mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] Mono on Windows/x64
>
> Hey,
>
> > Knowing this previously would have helped ;-). I have got conflicting
> > advice in the past about whether glib or eglib would be the best 
> > approach.
>
> Well, we were developing it ;-)
>
> But our goal is to drop glib and get back some of the memory usage we
> have been using.   As with every large change, this is not something we 
> want to do in the incremental 1.2.xx releases.
>
> Miguel.
> >
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

 

 



eglibmsvc2005compile.2.diff
Description: eglibmsvc2005compile.2.diff
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono 1.2.4, preparation rituals.

[Frederik Carlier]

>> Pressing ENTER in a single line textbox on a form that has a "default" 
>> button causes an extra character to be added to the textbox instead of 
>> the button being "pressed".
>> Also, pressing backspace to remove this non-printable character leaves a 
>> relic.
>> 
> Thanks for filing the bug.
>
> Although this bug report came too late, we have already branched the
> tree and it does not seem like there is a bug fix yet.
A bug fix has been commited (Bug 81408, SVN r76143). Is there a 
possibility this fix can find its way into 1.2.4?

Frederik.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Andreas Färber]

> I fixed a build problem with ABS in eglib's mono-ehash.c and will
> post a patch this evening if noone else is quicker.

http://bugzilla.ximian.com/show_bug.cgi?id=81433


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono 1.2.4, preparation rituals.

[Jonathan Pobst]

Jackson ported it to 1.2.4 in SVN r76147, so it will be in the final 
1.2.4 release.

Thanks!
Jon


Frederik Carlier wrote:
>>> Pressing ENTER in a single line textbox on a form that has a "default" 
>>> button causes an extra character to be added to the textbox instead of 
>>> the button being "pressed".
>>> Also, pressing backspace to remove this non-printable character leaves a 
>>> relic.
>>> 
>> Thanks for filing the bug.
>>
>> Although this bug report came too late, we have already branched the
>> tree and it does not seem like there is a bug fix yet.
> A bug fix has been commited (Bug 81408, SVN r76143). Is there a 
> possibility this fix can find its way into 1.2.4?
> 
> Frederik.
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 
> 

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Michael Jerris]

This patch is confirmed to compile clean on gcc now.  Feedback?

 

Mike

 



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Jerris
Sent: Monday, April 23, 2007 2:04 PM
To: Jonathan Chambers
Cc: Kornél Pál; Miguel de Icaza; mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] Mono on Windows/x64

 

Fixes gcc compile error below, and moves project file as requested.

 



From: Jonathan Chambers [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 23, 2007 1:45 PM
To: Michael Jerris
Cc: mono-devel-list@lists.ximian.com; Kornél Pál; Miguel de Icaza
Subject: Re: [Mono-dev] Mono on Windows/x64

 

Michael,
 I get the following compiler error building with gcc:

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I. -Wall -Werror -D_FORTIFY_SOURCE=2 -g -O0 
-D_GNU_SOURCE -MT libeglib_la-gstr.lo -MD -MP -MF .deps/libeglib_la- gstr.Tpo 
-c gstr.c  -fPIC -DPIC -o .libs/libeglib_la-gstr.o
gstr.c: In function 'g_filename_to_uri':
gstr.c:429: error: syntax error before ')' token
cc1: warnings being treated as errors
gstr.c :457: warning: control reaches end of non-void function
gstr.c: In function 'g_filename_from_uri':
gstr.c:482: error: syntax error before ')' token
gstr.c:517: warning: control reaches end of non-void function 
make[2]: *** [libeglib_la-gstr.lo] Error 1
make[2]: Leaving directory `/home/jschambe/monosvn/mono/eglib/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/jschambe/monosvn/mono/eglib' 
make: *** [all] Error 2

- Jonathan

On 4/23/07, Michael Jerris <[EMAIL PROTECTED]> wrote:

Agreed, still tons to do... the location of the vcproj makes no difference to 
me, can someone confirm where you want it and I'll roll another project file in 
the right location.  

 



From: Jonathan Chambers [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 23, 2007 1:22 PM
To: Michael Jerris
Cc: mono-devel-list@lists.ximian.com; Kornél Pál; Miguel de Icaza


Subject: Re: [Mono-dev] Mono on Windows/x64

 

Michael,
 This looks good; you may want to put the vsproj in mono/msvc since I stuck 
all other VS related files in there. There is some warnings that need fixed 
(passing chars to Unicode routines), and the issues you mentioned, but this 
should help alot in getting mono on Win64. If eglib is working, I can build 
mono with no gc initially to get any other issues worked out. I think my 
colleage has the beta version libgc 7 working. I can try with that as well. 

Thanks,
Jonathan

On 4/23/07, Michael Jerris <[EMAIL PROTECTED]> wrote:

Step 1.  Attached patch for review, should have no affect at all on non msvc 
build.  Resolves all build errors on msvc 2005.  Still needs implementations 
for quite a few things on msvc, and windows in general, this patch makes no 
effort to address those.  Note several things throughout marked FIXME that need 
to be looked at when the implementation is addressed. 

Mike



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:mono-devel-list- 
> [EMAIL PROTECTED] On Behalf Of Miguel de Icaza
> Sent: Monday, April 23, 2007 12:06 PM
> To: Jonathan Chambers
> Cc: Kornél Pál; mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] Mono on Windows/x64
>
> Hey,
>
> > Knowing this previously would have helped ;-). I have got conflicting
> > advice in the past about whether glib or eglib would be the best 
> > approach.
>
> Well, we were developing it ;-)
>
> But our goal is to drop glib and get back some of the memory usage we
> have been using.   As with every large change, this is not something we 
> want to do in the incremental 1.2.xx releases.
>
> Miguel.
> >
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

 

 



eglibmsvc2005compile.4.diff
Description: eglibmsvc2005compile.4.diff
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Mono on Windows/x64

[Miguel de Icaza]

Hey,

> This patch is confirmed to compile clean on gcc now.  Feedback?

It can go in;  Feel free to commit.

>  
> 
> Mike
> 
>  
> 
>
> __
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Michael
> Jerris
> Sent: Monday, April 23, 2007 2:04 PM
> To: Jonathan Chambers
> Cc: Kornél Pál; Miguel de Icaza; mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] Mono on Windows/x64
> 
> 
>  
> 
> Fixes gcc compile error below, and moves project file as requested.
> 
>  
> 
>
> __
> From: Jonathan Chambers [mailto:[EMAIL PROTECTED] 
> Sent: Monday, April 23, 2007 1:45 PM
> To: Michael Jerris
> Cc: mono-devel-list@lists.ximian.com; Kornél Pál; Miguel de Icaza
> Subject: Re: [Mono-dev] Mono on Windows/x64
> 
> 
>  
> 
> Michael,
>  I get the following compiler error building with gcc:
> 
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I. -Wall -Werror -D_FORTIFY_SOURCE=2
> -g -O0 -D_GNU_SOURCE -MT libeglib_la-gstr.lo -MD -MP
> -MF .deps/libeglib_la- gstr.Tpo -c gstr.c  -fPIC -DPIC
> -o .libs/libeglib_la-gstr.o
> gstr.c: In function 'g_filename_to_uri':
> gstr.c:429: error: syntax error before ')' token
> cc1: warnings being treated as errors
> gstr.c :457: warning: control reaches end of non-void function
> gstr.c: In function 'g_filename_from_uri':
> gstr.c:482: error: syntax error before ')' token
> gstr.c:517: warning: control reaches end of non-void function 
> make[2]: *** [libeglib_la-gstr.lo] Error 1
> make[2]: Leaving directory `/home/jschambe/monosvn/mono/eglib/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/jschambe/monosvn/mono/eglib' 
> make: *** [all] Error 2
> 
> - Jonathan
> 
> On 4/23/07, Michael Jerris <[EMAIL PROTECTED]> wrote:
> 
> Agreed, still tons to do… the location of the vcproj makes no
> difference to me, can someone confirm where you want it and I'll roll
> another project file in the right location.  
> 
>  
> 
>
> __
> From: Jonathan Chambers [mailto:[EMAIL PROTECTED] 
> Sent: Monday, April 23, 2007 1:22 PM
> To: Michael Jerris
> Cc: mono-devel-list@lists.ximian.com; Kornél Pál; Miguel de Icaza
> 
> 
> Subject: Re: [Mono-dev] Mono on Windows/x64
> 
> 
>  
> 
> Michael,
>  This looks good; you may want to put the vsproj in mono/msvc
> since I stuck all other VS related files in there. There is some
> warnings that need fixed (passing chars to Unicode routines), and the
> issues you mentioned, but this should help alot in getting mono on
> Win64. If eglib is working, I can build mono with no gc initially to
> get any other issues worked out. I think my colleage has the beta
> version libgc 7 working. I can try with that as well. 
> 
> Thanks,
> Jonathan
> 
> On 4/23/07, Michael Jerris <[EMAIL PROTECTED]> wrote:
> 
> Step 1.  Attached patch for review, should have no affect at all on
> non msvc build.  Resolves all build errors on msvc 2005.  Still needs
> implementations for quite a few things on msvc, and windows in
> general, this patch makes no effort to address those.  Note several
> things throughout marked FIXME that need to be looked at when the
> implementation is addressed. 
> 
> Mike
> 
> 
> 
> > -Original Message-
> > From: [EMAIL PROTECTED]
> [mailto:mono-devel-list- 
> > [EMAIL PROTECTED] On Behalf Of Miguel de Icaza
> > Sent: Monday, April 23, 2007 12:06 PM
> > To: Jonathan Chambers
> > Cc: Kornél Pál; mono-devel-list@lists.ximian.com
> > Subject: Re: [Mono-dev] Mono on Windows/x64
> >
> > Hey,
> >
> > > Knowing this previously would have helped ;-). I have got
> conflicting
> > > advice in the past about whether glib or eglib would be the best 
> > > approach.
> >
> > Well, we were developing it ;-)
> >
> > But our goal is to drop glib and get back some of the memory usage
> we
> > have been using.   As with every large change, this is not something
> we 
> > want to do in the incremental 1.2.xx releases.
> >
> > Miguel.
> > >
> > ___
> > Mono-devel-list mailing list
> > Mono-devel-list@lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 
> 
>  
> 
> 
>  
> 
> 
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] patch to start bonding navigator and masked textbox

[olivier . duff]

Hi,

I try again to send a patch to mailing list.
Hope this one this will work...
This patch is just a basic bindingnavigator with test and a stub of masked
textbox with some basic things taken from msdn but with no methode
implementation.

bye ( if yuou read me ;) )
duff ( olivier dufour)

stub MaskedTextbox and bindingNavigator.patch
Description: Binary data
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] Building nant-0.85 against Mono-1.2.4

[Paul]

Hi,

I'm trying to build NAnt-0.85 against Mono-1.2.4 and it's throwing the
following error. Does anyone know of a fix for it?

The Nant bug reporter has something about it here

http://sourceforge.net/tracker/index.php?func=detail&aid=1675297&group_id=31650&atid=402868

but there isn't a fix on the site for it - is there one?

TTFN

Paul
-- 
Sie können mich aufreizen und wirklich heiß machen!


signature.asc
Description: This is a digitally signed message part
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] patch to start bonding navigator and masked textbox

[Alan McGovern]

Hi Olivier,

I'm actually working on the BindingNavigator to implement the rest of it's
functionality (well, implement more of it anyway). I'm using your patch as
the base to work off, so it will hit the tree in a few days (or maybe a bit
more). I'll keep you posted on the status of it.

Alan.

On 4/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


Hi,

I try again to send a patch to mailing list.
Hope this one this will work...
This patch is just a basic bindingnavigator with test and a stub of masked
textbox with some basic things taken from msdn but with no methode
implementation.

bye ( if yuou read me ;) )
duff ( olivier dufour)
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list



___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] Building Tao against 1.2.4

[Paul]

Hi,

Anyone managed to build (using Nant) Tao-2.0RC using mono-1.2.4? It
hangs on building the XML ndoc stuff for Tao.PhysFS.

For now, is there a way to avoid generating the doc files?

TTFN

Paul
-- 
Sie können mich aufreizen und wirklich heiß machen!


signature.asc
Description: This is a digitally signed message part
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] Mono problem using Maemo

[Danilo Freire]

Hi,

I trying to use a simple helloworld Runtime.Remoting application (Client and
Server) at a N800 device, and the following problem appears at the server
when the client tries to connect with it:

Both applications run without problem in a desktop.

Server Stack:

Nokia-N800-10:~/MonoStuff# mono RemotingServer.exe

Press the enter key to exit...
mono[8035]: GLIB ERROR ** default - file inssel.c: line 3502
(mono_burg_emit): should not be reached
aborting...
Stacktrace:

  at
System.Runtime.Serialization.Formatters.Binary.MessageFormatter.ReadMethodCall(
System.IO.BinaryReader,bool,
System.Runtime.Remoting.Messaging.HeaderHandler,
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter)
<0x>
  at
System.Runtime.Serialization.Formatters.Binary.MessageFormatter.ReadMethodCall(
System.IO.BinaryReader,bool,
System.Runtime.Remoting.Messaging.HeaderHandler,
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter) <0x00218>

Native stacktrace:

mono [0x100688]
/usr/lib/libglib-2.0.so.0(g_logv+0x268) [0x4115b42d]

=
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=



and at the Client application:

Nokia-N800-10:~/MonoStuff# mono MaemoClient.exe


Unhandled Exception: System.Runtime.Remoting.RemotingException: Tcp
transport error.

Server stack trace:
  at
System.Runtime.Remoting.Channels.Tcp.TcpMessageIO.ReceiveMessageStatus (
System.IO.Stream networkStream, System.Byte[] buffer) [0x0]
  at
System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage
 msg, ITransportHeaders requestHeaders,
System.IO.Stream requestStream, ITransportHeaders& responseHeaders,
System.IO.Stream& responseStream) [0x0]
  at
System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage
 msg) [0x0]

Exception rethrown at [0]:
 ---> System.Runtime.Remoting.RemotingException: Connection closed
  at System.Runtime.Remoting.Channels.Tcp.TcpMessageIO.StreamRead (
System.IO.Stream networkStream, System.Byte[] buffer, Int32 count)
[0x0]
  at
System.Runtime.Remoting.Channels.Tcp.TcpMessageIO.ReceiveMessageStatus (
System.IO.Stream networkStream, System.Byte[] buffer) [0x0] --- End of
inner exception stack trace ---

  at
System.Runtime.Remoting.Channels.Tcp.TcpMessageIO.ReceiveMessageStatus (
System.IO.Stream networkStream, System.Byte[] buffer) [0x0]
  at
System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage
 msg, ITransportHeaders requestHeaders,
System.IO.Stream requestStream, ITransportHeaders& responseHeaders,
System.IO.Stream& responseStream) [0x0]
  at
System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage
 msg) [0x0]




Is that a known bug? It appears to be a problem at Mono runtime of maemo.
Any tip will be helpful.

thanks anticipate
[]s

--
Danilo Freire
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Building nant-0.85 against Mono-1.2.4

[marek safar]

Hello Paul,

> 
> I'm trying to build NAnt-0.85 against Mono-1.2.4 and it's throwing the
> following error. Does anyone know of a fix for it?
> 
> The Nant bug reporter has something about it here
> 
> http://sourceforge.net/tracker/index.php?func=detail&aid=1675297&group_id=31650&atid=402868
> 
> but there isn't a fix on the site for it - is there one?

The warning is correct and can be easily fixed. InitializeElement is virtual 
method
marked as obsolete but not in all its instances. To fix the warning you have to
either remove Obsolete attribute or add Obsolete attribute to all 
virtual/overrides
of the method.

Regards,
Marek
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Building nant-0.85 against Mono-1.2.4

[Leszek Ciesielski]

AFAIK this is fixed in nant repo, try building nant-nightly.

Or build nant with older mono, it'll work the same.

On 4/24/07, marek safar <[EMAIL PROTECTED]> wrote:
> Hello Paul,
>
> >
> > I'm trying to build NAnt-0.85 against Mono-1.2.4 and it's throwing the
> > following error. Does anyone know of a fix for it?
> >
> > The Nant bug reporter has something about it here
> >
> > http://sourceforge.net/tracker/index.php?func=detail&aid=1675297&group_id=31650&atid=402868
> >
> > but there isn't a fix on the site for it - is there one?
>
> The warning is correct and can be easily fixed. InitializeElement is virtual 
> method
> marked as obsolete but not in all its instances. To fix the warning you have 
> to
> either remove Obsolete attribute or add Obsolete attribute to all 
> virtual/overrides
> of the method.
>
> Regards,
> Marek
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>


-- 
MS-DOS user since 5.0
Windows user since 3.11
Linux user since kernel 2.4
Novell Netware user since 2.2
WARCRAFT user since 1.0
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list