Install fails (was Re: ANNOUNCE: Beagle 0.3.0 and Beagle-Xesam 0.1)

2007-12-03 Thread Henry S. Thompson
I have what I'm sure is a minority problem, but would welcome any suggestions. I run on a Fedore 6 box which is managed centrally, i.e. I do not have root privileges. I have been able in the past to install beagle (up through 0.2.18) by a modest amount of hacking about and installing other

Re: Install fails (was Re: ANNOUNCE: Beagle 0.3.0 and Beagle-Xesam 0.1)

2007-12-03 Thread D Bera
I run on a Fedore 6 box which is managed centrally, i.e. I do not have root privileges. I have been able in the past to install beagle (up through 0.2.18) by a modest amount of hacking about and installing other things as well, including my own mono-1.2.2.1, in my own local tree. But I'm

Re: Install fails (was Re: ANNOUNCE: Beagle 0.3.0 and Beagle-Xesam 0.1)

2007-12-03 Thread Joe Shaw
Hi, Just to add to what dBera said: On 12/3/07, Henry S. Thompson [EMAIL PROTECTED] wrote: produces a segfault with the following trace: at (wrapper managed-to-native) System.String.InternalAllocateStr (int) 0x4 at (wrapper managed-to-native) System.String.InternalAllocateStr (int)

Re: Install fails

2007-12-03 Thread Henry S. Thompson
D Bera writes: I run on a Fedore 6 box which is managed centrally, i.e. I do not have root privileges. I have been able in the past to install beagle (up through 0.2.18) by a modest amount of hacking about and installing other things as well, including my own mono-1.2.2.1, in my own local

Re: Install fails

2007-12-03 Thread Henry S. Thompson
Joe Shaw writes: Could you post the entire output of this crash? Thanks for looking -- here it is: MONO_GAC_PREFIX=/group/ltg/projects/lcontrib ./beagle-config BeagleSearch *** Running uninstalled Config.exe *** Debug: Loading old config Beagle.Util.NetworkingConfig from networking.xml

Re: Install fails

2007-12-03 Thread D Bera
at (wrapper managed-to-native) System.String.InternalAllocateStr (int) 0x4 at (wrapper managed-to-native) System.String.InternalAllocateStr (int) 0x at System.Text.StringBuilder.InternalEnsureCapacity (int) [0x000b1] in

Re: Install fails

2007-12-03 Thread Joe Shaw
Hi, On 12/3/07, D Bera [EMAIL PROTECTED] wrote: at (wrapper managed-to-native) System.String.InternalAllocateStr (int) 0x4 at (wrapper managed-to-native) System.String.InternalAllocateStr (int) 0x at System.Text.StringBuilder.InternalEnsureCapacity (int) [0x000b1] in

Re: Install fails

2007-12-03 Thread Joe Shaw
Hi again, get_machinename() crasher ... where have I seen this before ? Maybe this ? https://bugzilla.novell.com/show_bug.cgi?id=MONO82460 Looks like it, yeah. Unfortunately it's a Mono bug, and it seems to be deep enough in Mono XmlSerializer magic that we can't work around it. Oh

Re: Install fails

2007-12-03 Thread D Bera
Hi, at Mono.Unix.UnixEnvironment.get_MachineName () [0xb] in /amd/nfs/hippocampus/disk/ptn057/projects/lcontrib/src/mono-1.2.5.2/mcs/class/Mono.Posix/Mono.Unix/UnixEnvironment.cs:55 at Beagle.Util.NetworkingConfig..ctor () 0x0001d at (wrapper runtime-invoke)

Re: Install fails

2007-12-03 Thread Joe Shaw
Hi, On 12/3/07, D Bera [EMAIL PROTECTED] wrote: How about I use System.Environment.MachineName instead of Mono.Unix.UnixEnvironment.MachineName ? Seems to work with long names too... (I tried with a 24-char name). Yeah, let's do that. S.E.MachineName just calls gethostname() in an internal

Re: Install fails

2007-12-03 Thread Debajyoti Bera
How about I use System.Environment.MachineName instead of Mono.Unix.UnixEnvironment.MachineName ? Seems to work with long names too... (I tried with a 24-char name). Yeah, let's do that. S.E.MachineName just calls gethostname() in an internal call in the runtime. M.U.UE.MachineName