[Mono-dev] Status for PR-1489 - AppSettings File attribute symlink

[David Curylo]

I have a pull request that’s been complete for a few weeks for adding symlink 
support to the path reference in the AppSettings File attribute.  There was a 
little discussion and seems to be in good shape to merge, but it’s still 
waiting.  Any status on this one?

https://github.com/mono/mono/pull/1489

Is something more required?

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

Re: [Mono-dev] Building Profiler Example

[Greg Young]

And I got it working (with malloc) and pkg-config

[mono] \w @ gcc -shared -o mono-profiler-sample.so profiler.c
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-lglib-2.0 `pkg-config --cflags --libs mono-2` -fPIC

its mono-2 or mono0-sgen2 not mono.

On Wed, Jan 21, 2015 at 3:04 AM, Greg Young  wrote:
> Have it building now but after dumping gnew for malloc
>
> have tried things like
> gcc -shared -o mono-profiler-sample.so profiler.c
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -lglib-2.0 -fPIC
>
> with malloc it can compile with
> gcc -shared -o mono-profiler-sample.so profiler.c  -fPIC
>
> On Tue, Jan 20, 2015 at 11:48 PM, Greg Young  wrote:
>> So after some work I am back to where I was.
>>
>> [mono] \w @ pkg-config --cflags --libs mono
>>
>>   1 ↵
>>
>> [mono] \w @ pkg-config --cflags --libs dotnet
>>  -r:Accessibility.dll -r:cscompmgd.dll -r:Microsoft.VisualC.dll
>> -r:System.Configuration.Install.dll -r:System.Data.dll
>> -r:System.Data.OracleClient.dll -r:System.Design.dll
>> -r:System.DirectoryServices.dll -r:System.dll
>> -r:System.Drawing.Design.dll -r:System.Drawing.dll
>> -r:System.EnterpriseServices.dll -r:System.Management.dll
>> -r:System.Messaging.dll -r:System.Runtime.Remoting.dll
>> -r:System.Runtime.Serialization.Formatters.Soap.dll
>> -r:System.Security.dll -r:System.ServiceProcess.dll -r:System.Web.dll
>> -r:System.Web.Services.dll -r:System.Windows.Forms.dll
>> -r:System.Xml.dll
>>
>> I am guessing I need to go through the task of installing gnome to
>> /opt/gnome but keep thinking there must be an easier way (the bit
>> missing is from gnome though I am a bit surprised that I get nothing
>> at all on --libs mono
>>
>> I am curious can you actually build the sample with your parallel
>> build? I have been able to most everything else so far
>>
>> On Tue, Jan 20, 2015 at 9:44 PM, Greg Young  wrote:
>>>
>>>
>>> On Tuesday, January 20, 2015, Andres G. Aragoneses  wrote:

 On 20/01/15 20:19, Greg Young wrote:
>
> This is roughly what our scripts do.
>
> https://github.com/EventStore/EventStore/blob/dev/src/Scripts/get-mono


 So, are you running your pkg-config test inside the `[mono]` shell?
>>>
>>>
>>> Have pkg config paths set to include /opt/mono/lib/pkgconfig
>>>
>>> Pkg-config for dotnet gives back things but not mono.
>>>
>>> I have most of the paths there setup except for the gnome ones. I am
>>> guessing I have to build gnome to /opt/gnome is this part of what you are
>>> doing? The gnew function is gnome iirc
>>>


> We don't rebuild all the dependencies from source as specified but


 Rebuild dependencies of mono from sources? I don't do that either, I don't
 think the URL I gave you recommends this.
>>>
>>>
>>>  Hmm they have like 5 things to build from source



> mono is definitely done this way also it being that documentation is
> from Mono 1.1.9.1 I can only imagine the shear amount of yak shaving
> in trying to get it to work with current sources.


 I've been using a mono parallel environment for years in order to run two
 mono installations in the same computer at the same time (especially to 
 test
 master branch). I don't think the wiki page I pointed you is obsolete at
 all.


> On Tue, Jan 20, 2015 at 9:06 PM, Andres G. Aragoneses 
> wrote:
>>
>> Are you using a parallel mono environment[1] for your /opt/mono
>> installation?
>>
>> If not, then I'm not surprised that you're having pkg-config problems
>> and
>> the like.
>>
>> [1]
>>
>> http://www.mono-project.com/docs/compiling-mono/parallel-mono-environments/
>>
>>
>> On 20/01/15 19:54, Greg Young wrote:
>>>
>>>
>>> from looking:
>>>
>>> greg@orc ~/src/shit » pkg-config --cflags --libs mono
>>>
>>> greg@orc ~/src/shit »
>>>
>>> I'd guess this should be returning something? I am running with mono
>>> in /opt/mono built from source.
>>>
>>> Is there some step I am missing here in getting setup?
>>>
>>> On Tue, Jan 20, 2015 at 4:18 PM, Greg Young 
>>> wrote:


 Was trying to build the profiler example in the source tree it
 mentions to build with

 gcc -shared -o mono-profiler-sample.so profile.c `pkg-config --cflags
 --libs mono`

 I am guessing I also need a -I /mymono/includes/mono-2.0

 I am still getting build errors though.

~/Code/profiletest  gcc -shared -o mono-profiler-sample.so
 profile.c
 `pkg-config --cflags --libs mono` -I /opt/mono/include/mono-2.0
 profile.c:19:9: warning: implicit declaration of function 'g_print' is
 invalid in C99 [-Wimplicit-function-declaration]
   g_print ("total number of calls: %d\n", prof->ncalls);
>>

Re: [Mono-dev] Building Profiler Example

[Greg Young]

Have it building now but after dumping gnew for malloc

have tried things like
gcc -shared -o mono-profiler-sample.so profiler.c
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-lglib-2.0 -fPIC

with malloc it can compile with
gcc -shared -o mono-profiler-sample.so profiler.c  -fPIC

On Tue, Jan 20, 2015 at 11:48 PM, Greg Young  wrote:
> So after some work I am back to where I was.
>
> [mono] \w @ pkg-config --cflags --libs mono
>
>   1 ↵
>
> [mono] \w @ pkg-config --cflags --libs dotnet
>  -r:Accessibility.dll -r:cscompmgd.dll -r:Microsoft.VisualC.dll
> -r:System.Configuration.Install.dll -r:System.Data.dll
> -r:System.Data.OracleClient.dll -r:System.Design.dll
> -r:System.DirectoryServices.dll -r:System.dll
> -r:System.Drawing.Design.dll -r:System.Drawing.dll
> -r:System.EnterpriseServices.dll -r:System.Management.dll
> -r:System.Messaging.dll -r:System.Runtime.Remoting.dll
> -r:System.Runtime.Serialization.Formatters.Soap.dll
> -r:System.Security.dll -r:System.ServiceProcess.dll -r:System.Web.dll
> -r:System.Web.Services.dll -r:System.Windows.Forms.dll
> -r:System.Xml.dll
>
> I am guessing I need to go through the task of installing gnome to
> /opt/gnome but keep thinking there must be an easier way (the bit
> missing is from gnome though I am a bit surprised that I get nothing
> at all on --libs mono
>
> I am curious can you actually build the sample with your parallel
> build? I have been able to most everything else so far
>
> On Tue, Jan 20, 2015 at 9:44 PM, Greg Young  wrote:
>>
>>
>> On Tuesday, January 20, 2015, Andres G. Aragoneses  wrote:
>>>
>>> On 20/01/15 20:19, Greg Young wrote:

 This is roughly what our scripts do.

 https://github.com/EventStore/EventStore/blob/dev/src/Scripts/get-mono
>>>
>>>
>>> So, are you running your pkg-config test inside the `[mono]` shell?
>>
>>
>> Have pkg config paths set to include /opt/mono/lib/pkgconfig
>>
>> Pkg-config for dotnet gives back things but not mono.
>>
>> I have most of the paths there setup except for the gnome ones. I am
>> guessing I have to build gnome to /opt/gnome is this part of what you are
>> doing? The gnew function is gnome iirc
>>
>>>
>>>
 We don't rebuild all the dependencies from source as specified but
>>>
>>>
>>> Rebuild dependencies of mono from sources? I don't do that either, I don't
>>> think the URL I gave you recommends this.
>>
>>
>>  Hmm they have like 5 things to build from source
>>>
>>>
>>>
 mono is definitely done this way also it being that documentation is
 from Mono 1.1.9.1 I can only imagine the shear amount of yak shaving
 in trying to get it to work with current sources.
>>>
>>>
>>> I've been using a mono parallel environment for years in order to run two
>>> mono installations in the same computer at the same time (especially to test
>>> master branch). I don't think the wiki page I pointed you is obsolete at
>>> all.
>>>
>>>
 On Tue, Jan 20, 2015 at 9:06 PM, Andres G. Aragoneses 
 wrote:
>
> Are you using a parallel mono environment[1] for your /opt/mono
> installation?
>
> If not, then I'm not surprised that you're having pkg-config problems
> and
> the like.
>
> [1]
>
> http://www.mono-project.com/docs/compiling-mono/parallel-mono-environments/
>
>
> On 20/01/15 19:54, Greg Young wrote:
>>
>>
>> from looking:
>>
>> greg@orc ~/src/shit » pkg-config --cflags --libs mono
>>
>> greg@orc ~/src/shit »
>>
>> I'd guess this should be returning something? I am running with mono
>> in /opt/mono built from source.
>>
>> Is there some step I am missing here in getting setup?
>>
>> On Tue, Jan 20, 2015 at 4:18 PM, Greg Young 
>> wrote:
>>>
>>>
>>> Was trying to build the profiler example in the source tree it
>>> mentions to build with
>>>
>>> gcc -shared -o mono-profiler-sample.so profile.c `pkg-config --cflags
>>> --libs mono`
>>>
>>> I am guessing I also need a -I /mymono/includes/mono-2.0
>>>
>>> I am still getting build errors though.
>>>
>>>~/Code/profiletest  gcc -shared -o mono-profiler-sample.so
>>> profile.c
>>> `pkg-config --cflags --libs mono` -I /opt/mono/include/mono-2.0
>>> profile.c:19:9: warning: implicit declaration of function 'g_print' is
>>> invalid in C99 [-Wimplicit-function-declaration]
>>>   g_print ("total number of calls: %d\n", prof->ncalls);
>>>   ^
>>> profile.c:39:16: warning: implicit declaration of function 'g_new0' is
>>> invalid in C99 [-Wimplicit-function-declaration]
>>>   prof = g_new0 (MonoProfiler, 1);
>>>  ^
>>> profile.c:39:24: error: unexpected type name 'MonoProfiler': expected
>>> expression
>>>   prof = g_new0 (MonoProfiler, 1);
>>>  ^
>>> 2 warnings and 1 error generated.
>>>
>>> 

Re: [Mono-dev] Fork of certmgr - any ideas?

[Miguel de Icaza]

Seems like we have a case of these:

http://tirania.org/blog/archive/2010/Dec-31.html

On Tue, Jan 20, 2015 at 4:36 PM, Arthur Peka  wrote:

> Hey Andres,
>
> you don't seem to get my point.
> Firstly, IMO certmgr is *far* better off as a standalone app (not part of
> Mono bundle). That would allow to have much faster development.
>
> Secondly, from what I know Mono has a lengthy code review process, and
> lack of people who have the right to approve changes. Given that cergmgr is
> not a priority I can imagine how long will it be until request is
> accepted/rejected. I will try to merge my fixes back to certmgr, however,
> and I'm more than sure it will be *months *before any action is taken.
> Hope I'm wrong.
>
> And lastly, I'm using Visual Studio style as opposed to Mono style.
>
> Artur.
>
> On Tue, Jan 20, 2015 at 4:27 PM, Andres G. Aragoneses 
> wrote:
>
>> On 17/01/15 21:22, Arthur Peka wrote:
>>
>>> Hello mono devs,
>>>
>>> as you know, currently certmgr is bundled with Mono which IMO slows its
>>> development progress. There are some known bugs
>>> , and I think overall
>>> user experience as well as tool's code could be better.
>>>
>>> So I decided to make a standalone fork, maybe you have some ideas that
>>> could be implemented?
>>>
>>> You can find the fork here >> >.
>>>
>>
>> Hey Arthur, do you have any experience in opensource?
>>
>> Forking is only recommended as a last resort, when maintainers are not
>> willing to merge your contributions or your longer-term aspirations for the
>> project differ from theirs, drastically.
>>
>> Have you tried to contribute fixes for the bugs you mention?
>>
>>
>> ___
>> 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] Building Profiler Example

[Greg Young]

So after some work I am back to where I was.

[mono] \w @ pkg-config --cflags --libs mono

  1 ↵

[mono] \w @ pkg-config --cflags --libs dotnet
 -r:Accessibility.dll -r:cscompmgd.dll -r:Microsoft.VisualC.dll
-r:System.Configuration.Install.dll -r:System.Data.dll
-r:System.Data.OracleClient.dll -r:System.Design.dll
-r:System.DirectoryServices.dll -r:System.dll
-r:System.Drawing.Design.dll -r:System.Drawing.dll
-r:System.EnterpriseServices.dll -r:System.Management.dll
-r:System.Messaging.dll -r:System.Runtime.Remoting.dll
-r:System.Runtime.Serialization.Formatters.Soap.dll
-r:System.Security.dll -r:System.ServiceProcess.dll -r:System.Web.dll
-r:System.Web.Services.dll -r:System.Windows.Forms.dll
-r:System.Xml.dll

I am guessing I need to go through the task of installing gnome to
/opt/gnome but keep thinking there must be an easier way (the bit
missing is from gnome though I am a bit surprised that I get nothing
at all on --libs mono

I am curious can you actually build the sample with your parallel
build? I have been able to most everything else so far

On Tue, Jan 20, 2015 at 9:44 PM, Greg Young  wrote:
>
>
> On Tuesday, January 20, 2015, Andres G. Aragoneses  wrote:
>>
>> On 20/01/15 20:19, Greg Young wrote:
>>>
>>> This is roughly what our scripts do.
>>>
>>> https://github.com/EventStore/EventStore/blob/dev/src/Scripts/get-mono
>>
>>
>> So, are you running your pkg-config test inside the `[mono]` shell?
>
>
> Have pkg config paths set to include /opt/mono/lib/pkgconfig
>
> Pkg-config for dotnet gives back things but not mono.
>
> I have most of the paths there setup except for the gnome ones. I am
> guessing I have to build gnome to /opt/gnome is this part of what you are
> doing? The gnew function is gnome iirc
>
>>
>>
>>> We don't rebuild all the dependencies from source as specified but
>>
>>
>> Rebuild dependencies of mono from sources? I don't do that either, I don't
>> think the URL I gave you recommends this.
>
>
>  Hmm they have like 5 things to build from source
>>
>>
>>
>>> mono is definitely done this way also it being that documentation is
>>> from Mono 1.1.9.1 I can only imagine the shear amount of yak shaving
>>> in trying to get it to work with current sources.
>>
>>
>> I've been using a mono parallel environment for years in order to run two
>> mono installations in the same computer at the same time (especially to test
>> master branch). I don't think the wiki page I pointed you is obsolete at
>> all.
>>
>>
>>> On Tue, Jan 20, 2015 at 9:06 PM, Andres G. Aragoneses 
>>> wrote:

 Are you using a parallel mono environment[1] for your /opt/mono
 installation?

 If not, then I'm not surprised that you're having pkg-config problems
 and
 the like.

 [1]

 http://www.mono-project.com/docs/compiling-mono/parallel-mono-environments/


 On 20/01/15 19:54, Greg Young wrote:
>
>
> from looking:
>
> greg@orc ~/src/shit » pkg-config --cflags --libs mono
>
> greg@orc ~/src/shit »
>
> I'd guess this should be returning something? I am running with mono
> in /opt/mono built from source.
>
> Is there some step I am missing here in getting setup?
>
> On Tue, Jan 20, 2015 at 4:18 PM, Greg Young 
> wrote:
>>
>>
>> Was trying to build the profiler example in the source tree it
>> mentions to build with
>>
>> gcc -shared -o mono-profiler-sample.so profile.c `pkg-config --cflags
>> --libs mono`
>>
>> I am guessing I also need a -I /mymono/includes/mono-2.0
>>
>> I am still getting build errors though.
>>
>>~/Code/profiletest  gcc -shared -o mono-profiler-sample.so
>> profile.c
>> `pkg-config --cflags --libs mono` -I /opt/mono/include/mono-2.0
>> profile.c:19:9: warning: implicit declaration of function 'g_print' is
>> invalid in C99 [-Wimplicit-function-declaration]
>>   g_print ("total number of calls: %d\n", prof->ncalls);
>>   ^
>> profile.c:39:16: warning: implicit declaration of function 'g_new0' is
>> invalid in C99 [-Wimplicit-function-declaration]
>>   prof = g_new0 (MonoProfiler, 1);
>>  ^
>> profile.c:39:24: error: unexpected type name 'MonoProfiler': expected
>> expression
>>   prof = g_new0 (MonoProfiler, 1);
>>  ^
>> 2 warnings and 1 error generated.
>>
>> What am I missing to get this to build?
>>
>> --
>> Studying for the Turing test
>
>
>
>
>


 ___
 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-

Re: [Mono-dev] cert-sync

[Alexander Köplinger]

I always thought OSX used the system cert store anyway and this was just a 
Linux "issue"?
 
-- Alex 
 
From: edward.harvey.m...@clevertrove.com
To: mono-devel-list@lists.ximian.com
Date: Tue, 20 Jan 2015 12:01:31 +
Subject: [Mono-dev] cert-sync









> From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
> boun...@lists.ximian.com] On Behalf Of Jo Shields
> 
> Mono 3.12 will ship with a new tool, cert-sync,
> which populates the root CA store from a static concatenated file.
> This will be executed on package install on Linux
 
Thanks Jo,
 
It looks like it does the same job as mozroots, but pulls from the concatenated 
file instead of downloading from mozilla.  That file should be available on 
most (if not all) linuxes, but ... Any plans to support OSX?  And/or mobile 
devices?
 
If the presence of root certs is not automated on *all* platforms running mono, 
then the application developer is still required to programatically run 
mozroots anyway.
 
Automating the process into the installation package is a really nice 
improvement.  Even if cert-sync won't work on OSX due to having no concatenated 
file available, can mozroots be automated into the OSX mono installer?
 




___
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] Fork of certmgr - any ideas?

[Arthur Peka]

Hey Andres,

you don't seem to get my point.
Firstly, IMO certmgr is *far* better off as a standalone app (not part of
Mono bundle). That would allow to have much faster development.

Secondly, from what I know Mono has a lengthy code review process, and lack
of people who have the right to approve changes. Given that cergmgr is not
a priority I can imagine how long will it be until request is
accepted/rejected. I will try to merge my fixes back to certmgr, however,
and I'm more than sure it will be *months *before any action is taken. Hope
I'm wrong.

And lastly, I'm using Visual Studio style as opposed to Mono style.

Artur.

On Tue, Jan 20, 2015 at 4:27 PM, Andres G. Aragoneses 
wrote:

> On 17/01/15 21:22, Arthur Peka wrote:
>
>> Hello mono devs,
>>
>> as you know, currently certmgr is bundled with Mono which IMO slows its
>> development progress. There are some known bugs
>> , and I think overall
>> user experience as well as tool's code could be better.
>>
>> So I decided to make a standalone fork, maybe you have some ideas that
>> could be implemented?
>>
>> You can find the fork here .
>>
>
> Hey Arthur, do you have any experience in opensource?
>
> Forking is only recommended as a last resort, when maintainers are not
> willing to merge your contributions or your longer-term aspirations for the
> project differ from theirs, drastically.
>
> Have you tried to contribute fixes for the bugs you mention?
>
>
> ___
> 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] Building Profiler Example

[Greg Young]

On Tuesday, January 20, 2015, Andres G. Aragoneses  wrote:

> On 20/01/15 20:19, Greg Young wrote:
>
>> This is roughly what our scripts do.
>>
>> https://github.com/EventStore/EventStore/blob/dev/src/Scripts/get-mono
>>
>
> So, are you running your pkg-config test inside the `[mono]` shell?


Have pkg config paths set to include /opt/mono/lib/pkgconfig

Pkg-config for dotnet gives back things but not mono.

I have most of the paths there setup except for the gnome ones. I am
guessing I have to build gnome to /opt/gnome is this part of what you are
doing? The gnew function is gnome iirc


>
>  We don't rebuild all the dependencies from source as specified but
>>
>
> Rebuild dependencies of mono from sources? I don't do that either, I don't
> think the URL I gave you recommends this.


 Hmm they have like 5 things to build from source

>
>
>  mono is definitely done this way also it being that documentation is
>> from Mono 1.1.9.1 I can only imagine the shear amount of yak shaving
>> in trying to get it to work with current sources.
>>
>
> I've been using a mono parallel environment for years in order to run two
> mono installations in the same computer at the same time (especially to
> test master branch). I don't think the wiki page I pointed you is obsolete
> at all.
>
>
>  On Tue, Jan 20, 2015 at 9:06 PM, Andres G. Aragoneses 
>> wrote:
>>
>>> Are you using a parallel mono environment[1] for your /opt/mono
>>> installation?
>>>
>>> If not, then I'm not surprised that you're having pkg-config problems and
>>> the like.
>>>
>>> [1]
>>> http://www.mono-project.com/docs/compiling-mono/parallel-
>>> mono-environments/
>>>
>>>
>>> On 20/01/15 19:54, Greg Young wrote:
>>>

 from looking:

 greg@orc ~/src/shit » pkg-config --cflags --libs mono

 greg@orc ~/src/shit »

 I'd guess this should be returning something? I am running with mono
 in /opt/mono built from source.

 Is there some step I am missing here in getting setup?

 On Tue, Jan 20, 2015 at 4:18 PM, Greg Young 
 wrote:

>
> Was trying to build the profiler example in the source tree it
> mentions to build with
>
> gcc -shared -o mono-profiler-sample.so profile.c `pkg-config --cflags
> --libs mono`
>
> I am guessing I also need a -I /mymono/includes/mono-2.0
>
> I am still getting build errors though.
>
>~/Code/profiletest  gcc -shared -o mono-profiler-sample.so
> profile.c
> `pkg-config --cflags --libs mono` -I /opt/mono/include/mono-2.0
> profile.c:19:9: warning: implicit declaration of function 'g_print' is
> invalid in C99 [-Wimplicit-function-declaration]
>   g_print ("total number of calls: %d\n", prof->ncalls);
>   ^
> profile.c:39:16: warning: implicit declaration of function 'g_new0' is
> invalid in C99 [-Wimplicit-function-declaration]
>   prof = g_new0 (MonoProfiler, 1);
>  ^
> profile.c:39:24: error: unexpected type name 'MonoProfiler': expected
> expression
>   prof = g_new0 (MonoProfiler, 1);
>  ^
> 2 warnings and 1 error generated.
>
> What am I missing to get this to build?
>
> --
> Studying for the Turing test
>





>>>
>>> ___
>>> 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
>


-- 
Studying for the Turing test
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Building Profiler Example

[Andres G. Aragoneses]

On 20/01/15 20:19, Greg Young wrote:

This is roughly what our scripts do.

https://github.com/EventStore/EventStore/blob/dev/src/Scripts/get-mono


So, are you running your pkg-config test inside the `[mono]` shell?



We don't rebuild all the dependencies from source as specified but


Rebuild dependencies of mono from sources? I don't do that either, I 
don't think the URL I gave you recommends this.




mono is definitely done this way also it being that documentation is
from Mono 1.1.9.1 I can only imagine the shear amount of yak shaving
in trying to get it to work with current sources.


I've been using a mono parallel environment for years in order to run 
two mono installations in the same computer at the same time (especially 
to test master branch). I don't think the wiki page I pointed you is 
obsolete at all.




On Tue, Jan 20, 2015 at 9:06 PM, Andres G. Aragoneses  wrote:

Are you using a parallel mono environment[1] for your /opt/mono
installation?

If not, then I'm not surprised that you're having pkg-config problems and
the like.

[1]
http://www.mono-project.com/docs/compiling-mono/parallel-mono-environments/


On 20/01/15 19:54, Greg Young wrote:


from looking:

greg@orc ~/src/shit » pkg-config --cflags --libs mono

greg@orc ~/src/shit »

I'd guess this should be returning something? I am running with mono
in /opt/mono built from source.

Is there some step I am missing here in getting setup?

On Tue, Jan 20, 2015 at 4:18 PM, Greg Young 
wrote:


Was trying to build the profiler example in the source tree it
mentions to build with

gcc -shared -o mono-profiler-sample.so profile.c `pkg-config --cflags
--libs mono`

I am guessing I also need a -I /mymono/includes/mono-2.0

I am still getting build errors though.

   ~/Code/profiletest  gcc -shared -o mono-profiler-sample.so profile.c
`pkg-config --cflags --libs mono` -I /opt/mono/include/mono-2.0
profile.c:19:9: warning: implicit declaration of function 'g_print' is
invalid in C99 [-Wimplicit-function-declaration]
  g_print ("total number of calls: %d\n", prof->ncalls);
  ^
profile.c:39:16: warning: implicit declaration of function 'g_new0' is
invalid in C99 [-Wimplicit-function-declaration]
  prof = g_new0 (MonoProfiler, 1);
 ^
profile.c:39:24: error: unexpected type name 'MonoProfiler': expected
expression
  prof = g_new0 (MonoProfiler, 1);
 ^
2 warnings and 1 error generated.

What am I missing to get this to build?

--
Studying for the Turing test








___
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] Building Profiler Example

[Greg Young]

This is roughly what our scripts do.

https://github.com/EventStore/EventStore/blob/dev/src/Scripts/get-mono
We don't rebuild all the dependencies from source as specified but
mono is definitely done this way also it being that documentation is
from Mono 1.1.9.1 I can only imagine the shear amount of yak shaving
in trying to get it to work with current sources.



On Tue, Jan 20, 2015 at 9:06 PM, Andres G. Aragoneses  wrote:
> Are you using a parallel mono environment[1] for your /opt/mono
> installation?
>
> If not, then I'm not surprised that you're having pkg-config problems and
> the like.
>
> [1]
> http://www.mono-project.com/docs/compiling-mono/parallel-mono-environments/
>
>
> On 20/01/15 19:54, Greg Young wrote:
>>
>> from looking:
>>
>> greg@orc ~/src/shit » pkg-config --cflags --libs mono
>>
>> greg@orc ~/src/shit »
>>
>> I'd guess this should be returning something? I am running with mono
>> in /opt/mono built from source.
>>
>> Is there some step I am missing here in getting setup?
>>
>> On Tue, Jan 20, 2015 at 4:18 PM, Greg Young 
>> wrote:
>>>
>>> Was trying to build the profiler example in the source tree it
>>> mentions to build with
>>>
>>> gcc -shared -o mono-profiler-sample.so profile.c `pkg-config --cflags
>>> --libs mono`
>>>
>>> I am guessing I also need a -I /mymono/includes/mono-2.0
>>>
>>> I am still getting build errors though.
>>>
>>>   ~/Code/profiletest  gcc -shared -o mono-profiler-sample.so profile.c
>>> `pkg-config --cflags --libs mono` -I /opt/mono/include/mono-2.0
>>> profile.c:19:9: warning: implicit declaration of function 'g_print' is
>>> invalid in C99 [-Wimplicit-function-declaration]
>>>  g_print ("total number of calls: %d\n", prof->ncalls);
>>>  ^
>>> profile.c:39:16: warning: implicit declaration of function 'g_new0' is
>>> invalid in C99 [-Wimplicit-function-declaration]
>>>  prof = g_new0 (MonoProfiler, 1);
>>> ^
>>> profile.c:39:24: error: unexpected type name 'MonoProfiler': expected
>>> expression
>>>  prof = g_new0 (MonoProfiler, 1);
>>> ^
>>> 2 warnings and 1 error generated.
>>>
>>> What am I missing to get this to build?
>>>
>>> --
>>> Studying for the Turing test
>>
>>
>>
>>
>
>
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list



-- 
Studying for the Turing test
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Building Profiler Example

[Andres G. Aragoneses]

Are you using a parallel mono environment[1] for your /opt/mono 
installation?


If not, then I'm not surprised that you're having pkg-config problems 
and the like.


[1] 
http://www.mono-project.com/docs/compiling-mono/parallel-mono-environments/


On 20/01/15 19:54, Greg Young wrote:

from looking:

greg@orc ~/src/shit » pkg-config --cflags --libs mono

greg@orc ~/src/shit »

I'd guess this should be returning something? I am running with mono
in /opt/mono built from source.

Is there some step I am missing here in getting setup?

On Tue, Jan 20, 2015 at 4:18 PM, Greg Young  wrote:

Was trying to build the profiler example in the source tree it
mentions to build with

gcc -shared -o mono-profiler-sample.so profile.c `pkg-config --cflags
--libs mono`

I am guessing I also need a -I /mymono/includes/mono-2.0

I am still getting build errors though.

  ~/Code/profiletest  gcc -shared -o mono-profiler-sample.so profile.c
`pkg-config --cflags --libs mono` -I /opt/mono/include/mono-2.0
profile.c:19:9: warning: implicit declaration of function 'g_print' is
invalid in C99 [-Wimplicit-function-declaration]
 g_print ("total number of calls: %d\n", prof->ncalls);
 ^
profile.c:39:16: warning: implicit declaration of function 'g_new0' is
invalid in C99 [-Wimplicit-function-declaration]
 prof = g_new0 (MonoProfiler, 1);
^
profile.c:39:24: error: unexpected type name 'MonoProfiler': expected expression
 prof = g_new0 (MonoProfiler, 1);
^
2 warnings and 1 error generated.

What am I missing to get this to build?

--
Studying for the Turing test







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

Re: [Mono-dev] Building Profiler Example

[Greg Young]

greg@orc ~/src/shit » export PKG_CONFIG_PATH=/usr/lib/pkgconfig

  1 ↵
greg@orc ~/src/shit » pkg-config --cflags --libs mono

greg@orc ~/src/shit »

I have a mono.pc in /usr/lib/pkgconfig

On Tue, Jan 20, 2015 at 8:54 PM, Greg Young  wrote:
> from looking:
>
> greg@orc ~/src/shit » pkg-config --cflags --libs mono
>
> greg@orc ~/src/shit »
>
> I'd guess this should be returning something? I am running with mono
> in /opt/mono built from source.
>
> Is there some step I am missing here in getting setup?
>
> On Tue, Jan 20, 2015 at 4:18 PM, Greg Young  wrote:
>> Was trying to build the profiler example in the source tree it
>> mentions to build with
>>
>> gcc -shared -o mono-profiler-sample.so profile.c `pkg-config --cflags
>> --libs mono`
>>
>> I am guessing I also need a -I /mymono/includes/mono-2.0
>>
>> I am still getting build errors though.
>>
>>  ~/Code/profiletest  gcc -shared -o mono-profiler-sample.so profile.c
>> `pkg-config --cflags --libs mono` -I /opt/mono/include/mono-2.0
>> profile.c:19:9: warning: implicit declaration of function 'g_print' is
>> invalid in C99 [-Wimplicit-function-declaration]
>> g_print ("total number of calls: %d\n", prof->ncalls);
>> ^
>> profile.c:39:16: warning: implicit declaration of function 'g_new0' is
>> invalid in C99 [-Wimplicit-function-declaration]
>> prof = g_new0 (MonoProfiler, 1);
>>^
>> profile.c:39:24: error: unexpected type name 'MonoProfiler': expected 
>> expression
>> prof = g_new0 (MonoProfiler, 1);
>>^
>> 2 warnings and 1 error generated.
>>
>> What am I missing to get this to build?
>>
>> --
>> Studying for the Turing test
>
>
>
> --
> Studying for the Turing test



-- 
Studying for the Turing test
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Building Profiler Example

[Greg Young]

from looking:

greg@orc ~/src/shit » pkg-config --cflags --libs mono

greg@orc ~/src/shit »

I'd guess this should be returning something? I am running with mono
in /opt/mono built from source.

Is there some step I am missing here in getting setup?

On Tue, Jan 20, 2015 at 4:18 PM, Greg Young  wrote:
> Was trying to build the profiler example in the source tree it
> mentions to build with
>
> gcc -shared -o mono-profiler-sample.so profile.c `pkg-config --cflags
> --libs mono`
>
> I am guessing I also need a -I /mymono/includes/mono-2.0
>
> I am still getting build errors though.
>
>  ~/Code/profiletest  gcc -shared -o mono-profiler-sample.so profile.c
> `pkg-config --cflags --libs mono` -I /opt/mono/include/mono-2.0
> profile.c:19:9: warning: implicit declaration of function 'g_print' is
> invalid in C99 [-Wimplicit-function-declaration]
> g_print ("total number of calls: %d\n", prof->ncalls);
> ^
> profile.c:39:16: warning: implicit declaration of function 'g_new0' is
> invalid in C99 [-Wimplicit-function-declaration]
> prof = g_new0 (MonoProfiler, 1);
>^
> profile.c:39:24: error: unexpected type name 'MonoProfiler': expected 
> expression
> prof = g_new0 (MonoProfiler, 1);
>^
> 2 warnings and 1 error generated.
>
> What am I missing to get this to build?
>
> --
> Studying for the Turing test



-- 
Studying for the Turing test
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Fork of certmgr - any ideas?

[Andres G. Aragoneses]

On 17/01/15 21:22, Arthur Peka wrote:

Hello mono devs,

as you know, currently certmgr is bundled with Mono which IMO slows its
development progress. There are some known bugs
, and I think overall
user experience as well as tool's code could be better.

So I decided to make a standalone fork, maybe you have some ideas that
could be implemented?

You can find the fork here .


Hey Arthur, do you have any experience in opensource?

Forking is only recommended as a last resort, when maintainers are not 
willing to merge your contributions or your longer-term aspirations for 
the project differ from theirs, drastically.


Have you tried to contribute fixes for the bugs you mention?


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

[Mono-dev] Building Profiler Example

[Greg Young]

Was trying to build the profiler example in the source tree it
mentions to build with

gcc -shared -o mono-profiler-sample.so profile.c `pkg-config --cflags
--libs mono`

I am guessing I also need a -I /mymono/includes/mono-2.0

I am still getting build errors though.

 ~/Code/profiletest  gcc -shared -o mono-profiler-sample.so profile.c
`pkg-config --cflags --libs mono` -I /opt/mono/include/mono-2.0
profile.c:19:9: warning: implicit declaration of function 'g_print' is
invalid in C99 [-Wimplicit-function-declaration]
g_print ("total number of calls: %d\n", prof->ncalls);
^
profile.c:39:16: warning: implicit declaration of function 'g_new0' is
invalid in C99 [-Wimplicit-function-declaration]
prof = g_new0 (MonoProfiler, 1);
   ^
profile.c:39:24: error: unexpected type name 'MonoProfiler': expected expression
prof = g_new0 (MonoProfiler, 1);
   ^
2 warnings and 1 error generated.

What am I missing to get this to build?

-- 
Studying for the Turing test
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] cert-sync

[Edward Ned Harvey (mono)]

> From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-

> boun...@lists.ximian.com] On Behalf Of Jo Shields

>

> Mono 3.12 will ship with a new tool, cert-sync,

> which populates the root CA store from a static concatenated file.

> This will be executed on package install on Linux



Thanks Jo,



It looks like it does the same job as mozroots, but pulls from the concatenated 
file instead of downloading from mozilla.  That file should be available on 
most (if not all) linuxes, but ... Any plans to support OSX?  And/or mobile 
devices?



If the presence of root certs is not automated on *all* platforms running mono, 
then the application developer is still required to programatically run 
mozroots anyway.



Automating the process into the installation package is a really nice 
improvement.  Even if cert-sync won't work on OSX due to having no concatenated 
file available, can mozroots be automated into the OSX mono installer?


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