On 09/20/07 Philippe Monnet wrote:
Actually someone else recommended
that I use monocharge as I have been unable to build from a stable source
monocharge and the get-monolite hack should never be used: they are
a problem, not a solution, so whoever reccomended them was simply wrong.
I am only
Paolo Molaro wrote:
On 09/20/07 Philippe Monnet wrote:
Actually someone else recommended
that I use monocharge as I have been unable to build from a stable source
monocharge and the get-monolite hack should never be used: they are
a problem, not a solution, so whoever reccomended them was
Hi,
Am 21.09.2007 um 15:08 schrieb Paolo Molaro:
On 09/20/07 Philippe Monnet wrote:
Actually someone else recommended
that I use monocharge as I have been unable to build from a stable
source
monocharge and the get-monolite hack should never be used: they are
a problem, not a solution,
On 09/21/07 Robert Jordan wrote:
It was me who recommended monocharge, but only because he cannot
build the class libs due to limited memory resources on his
machine.
I told him to configure with --disable-mcs-build and use the appropriate
monocharge libs.
I'm just saying: monocharge and
On 09/19/07 Philippe Monnet wrote:
Over the last couple days, I have been trying to figure out how to use
monocharge (now that I was able to build it).
monocharge should simply not be used, as the README says.
If you have problems in bootstrapping from svn you should
build and install first
Actually someone else recommended that I use monocharge as I have been unable to build from a stable source release, or a a daily build, or from SVN (trunk or tagged release). I realize my situation is challenging due to a shared hosting scenario and a lack of a local Linux box (don't have access
Over the last couple days, I have been trying to figure out how to use monocharge (now that I was able to build it).I had gone back to my "patched" mono svn trunk and done: ./configure --disable-mcs-build --prefix=/mysharedhost/mono make make installBut my mono/lib folders does not seem to have
