On Wed, 2004-03-24 at 14:57, Robert Shade wrote:
> No
>
> rob
Ok, have you tried changing the definition of RUNTIME in
build/config-default.make? Strange that the config.make change doesn't
cut it; maybe that needs RUNTIME := mint to get it to stick.
Peter
--
Peter Williams
No
rob
Peter Williams wrote:
On Wed, 2004-03-24 at 11:29, Robert Shade wrote:
I have not been able to figure out how to change $(RUNTIME) to resolve
to mint, thus the change.
Putting
RUNTIME = mint
in build/config.make doesn't work?
Peter
___
On Wed, 2004-03-24 at 11:29, Robert Shade wrote:
> I have not been able to figure out how to change $(RUNTIME) to resolve
> to mint, thus the change.
Putting
RUNTIME = mint
in build/config.make doesn't work?
Peter
--
Peter Williams [EMAIL PROTECTED]
"[Ninjas] are c
Did you ever get this fixed?
If you didn't, the problem is that at this phase of the buld the
makefiles are using the internal mcs (the one it just built). In order
to do this, it calls it directly instead of using the mcs script:
---(snip!)---
Creating ../../../build/deps/I18N.dll.makefrag ..
Urs C Muff wrote:
did you install mono from fink?
if so, you have to add /sw/lib to DYLD_LIBRARY_PATH instead of
/usr/local/lib
On Mar 23, 2004, at 10:00 PM, Attila Balogh wrote:
Yes, and i added /sw/lib in the first place.
Could i check the patch you created?
Regards
Attila
__
did you install mono from fink?
if so, you have to add /sw/lib to DYLD_LIBRARY_PATH instead of
/usr/local/lib
On Mar 23, 2004, at 10:00 PM, Attila Balogh wrote:
Erik Dasque wrote:
Hmmm,
Yes, I think I had this problem at some point. Set LD_LIBRARY_PATH
since you're talking about .so librarie
This is due the the config file issue, I sent a patch to the dev list,
but nobody replied to review it yet!
- Urs
On Mar 23, 2004, at 10:00 PM, Attila Balogh wrote:
Erik Dasque wrote:
Hmmm,
Yes, I think I had this problem at some point. Set LD_LIBRARY_PATH
since you're talking about .so libr
Erik Dasque wrote:
Hmmm,
Yes, I think I had this problem at some point. Set LD_LIBRARY_PATH
since you're talking about .so libraries here. Renaming them to dylib
won't help, they're not dylibs. So set LD_LIBRARY_PATH the same way
you set DYLD_LIBRARY_PATH. Let me know if that fixes it.
Erik
Attila Balogh wrote:
hello, still on running monodevelop on osx.
I get a gtksharpglue dll not found exception. Those are in
/usr/local/lib/libgtksharpglue.so, ... (I even renamed them to .dylib,
and I tried a entry in the config, no change).
at me the first problem is with libgnomeui.so
this
hello, still on running monodevelop on osx.
I get a gtksharpglue dll not found exception. Those are in
/usr/local/lib/libgtksharpglue.so, ... (I even renamed them to .dylib,
and I tried a entry in the config, no change).
at me the first problem is with libgnomeui.so
this is the exact message:
i made the change, now it goes further, after checking all the .xml
files it throws this:
Unhandled Exception: System.IO.IOException: Win32 IO returned
ERROR_NO_MORE_FILES. Path: ../../mcs/errors/cs3005-14.cs
A Win32 IO error?!? Try getting a fresh clean copy from cvs. I've been
compiling mcs
build is not really an issue, just replace mono with mint in all build
processes and make sure you have the 'fink' dependencies using the
unstable tree, but running is still a big no for me...
- Urs
On Mar 22, 2004, at 5:24 PM, Attila Balogh wrote:
Urs C Muff wrote:
change mono into mint in t
Urs C Muff wrote:
change mono into mint in the make files and that should do it.
-urs
On Mar 22, 2004, at 1:39 PM, Attila Balogh wrote:
it's a little bit offtopic it this thread, but Rob: is it possible
that the '(except for some GTK# stuff)' is the reason why i can't
build monodoc on macosx?
Yes. Changed .so to .dylib
after installing? with mv?
After installing. Unfortunately it gets clobbered every time you update.
/usr/local/lib/monodoc> cat /usr/local/etc/mono/config
--snip--
That looks about right to me. Although, I can't see what I have right
now. I'm actually in the middle
were you able to run any GTK# apps? in gtk-sharp/sample?
did you change /usr/local/etc/mono/config at all? .so --> .dylib?
Yes. Changed .so to .dylib
I get a gtksharpglue dll not found exception. Those are in
/usr/local/lib/libgtksharpglue.so, ... (I even renamed them to .dylib,
and I tried
were you able to run any GTK# apps? in gtk-sharp/sample?
did you change /usr/local/etc/mono/config at all? .so --> .dylib?
I get a gtksharpglue dll not found exception. Those are in
/usr/local/lib/libgtksharpglue.so, ... (I even renamed them to .dylib,
and I tried a entry in the config, no cha
change mono into mint in the make files and that should do it.
-urs
On Mar 22, 2004, at 1:39 PM, Attila Balogh wrote:
it's a little bit offtopic it this thread, but Rob: is it possible
that the '(except for some GTK# stuff)' is the reason why i can't
build monodoc on macosx? gtk#, gtksourcevie
I was referring to running GTK# apps. I've never had any problems
building anything.
I would suggest that you update to the latest CVS and try again, as some
PPC changes have occured in the JIT recently. If it still doesn't help,
file a bug report.
rob
Attila Balogh wrote:
it's a little bi
it's a little bit offtopic it this thread, but Rob: is it possible that
the '(except for some GTK# stuff)' is the reason why i can't build
monodoc on macosx? gtk#, gtksourceview-sharp and all the dependencies
compile allright, but the monodoc compilation fails because of '** ERROR
**: file mini
It should go all the way. :)
As stated a couple times on these lists, the JIT is still incomplete for
PPC. Paolo has started on exceptions for the PPC JIT (the last
incomplete part AFAIK), but it's not quite done yet.
Everything (mcs and otherwise) should work fine using the interpreter
(exce
Robert Shade wrote:
make sure that /usr/local/mcs refers to the interpreter (mint) and not
the JIT (mono).
So is it generally a bad idea to use the JIT for building MCS? Or is
that just recommended on OSX? It gets farther now that mint is being
used... Still going.
--
Benjamin Reed, a.k.a.
make sure that /usr/local/mcs refers to the interpreter (mint) and not
the JIT (mono).
rob
Benjamin Reed wrote:
I've been checking whether MCS is yet buildable on OSX, and it gets
farther than before, it now dies with:
---(snip!)---
Creating ../../../build/deps/I18N.dll.makefrag ...
touch ../
Benjamin Reed wrote:
I'm using the default profile, and the mono 0.31 packages I just put up
in Fink unstable.
Oh, and I do have libicn enabled with mono building against it. I seem
to recall getting a similar error to this from the 0.30.99 bits though,
with a non-icu mono, so that may be unre
I've been checking whether MCS is yet buildable on OSX, and it gets
farther than before, it now dies with:
---(snip!)---
Creating ../../../build/deps/I18N.dll.makefrag ...
touch ../../../build/deps/I18N.dll.stamp
MONO_PATH="../../../class/lib:$MONO_PATH" mono ../../../mcs/mcs.exe
/r:mscorlib.dl
24 matches
Mail list logo
