>>>>> "Jan" == Jan Rychter <[EMAIL PROTECTED]> writes:
>>>>> "Raymond" == Raymond Toy <[EMAIL PROTECTED]> writes:
>>>>> "Martin" == Martin Cracauer <[EMAIL PROTECTED]> writes:
Martin> These people are just insane. The shared libs used to hang out
Martin> at 0x4000xxx to 0x4200xxx. Then Redhat 7 comes along and they
Martin> take up space to 0x4400xxx. Fine, I can move up.
Raymond> FWIW, when 19a comes out (whenever that might be), CMUCL will
Raymond> have its dynamic space start at #x58000000 instead of
Raymond> #x48000000. Hope that helps.
Jan> Hmm... when is that expected?
Good question. That greatly depends on when the cvs machine is
revived. If it were revived today, I would expect that at least 2
more snapshots would be done, and, if we're lucky, the second snapshot
would be equivalent to the release. That puts us in April at the very
earliest. More likely May or even June. Sorry.
Jan> I tried to compile and cross-compile the 2003-11 snapshot changing the
Jan> DYNAMIC_0_SPACE_START offset to 0x58000000, but all I got is segfaults
Jan> in the load-world stage. Apparently there is more to it than just
Jan> changing this value.
If you cannot build a version using Ole Rohne's description, I'll see
if I can get some current binaries uploaded somewhere.
Jan> And SBCL doesn't like SERIES, which I'm using.
Please report the issue as a bug on the series bug list on
sourceforge.net if the current CVS sources of series still don't
work. Thanks.
Ray
--
Ericsson may automatically add a disclaimer. Sorry, it's beyond my
control.
This communication is confidential and intended solely for the addressee(s). Any
unauthorized review, use, disclosure or distribution is prohibited. If you believe
this message has been sent to you in error, please notify the sender by replying to
this transmission and delete the message without disclosing it. Thank you.
E-mail including attachments is susceptible to data corruption, interruption,
unauthorized amendment, tampering and viruses, and we only send and receive e-mails on
the basis that we are not liable for any such corruption, interception, amendment,
tampering or viruses or any consequences thereof.
