Camm Maguire writes:
> Greetings! OK, the bsd issues are almost ironed out.
>
> GCL has made extensive use of unboxed complex arithmetic. Does BSD
> have this function somewhere?
>
> Error: ERROR "dlsym lookup failure on \"cexpf\": \"Undefined symbol
> \\\"cexpf\\\"\"" Fast links are on: do (si::
Greetings! OK, the bsd issues are almost ironed out.
GCL has made extensive use of unboxed complex arithmetic. Does BSD
have this function somewhere?
Error: ERROR "dlsym lookup failure on \"cexpf\": \"Undefined symbol
\\\"cexpf\\\"\""
Fast links are on: do (si::use-fast-links nil) for debuggin
"Weiss, Juergen" writes:
> I think in /boot/loader.conf you can set the maximum data segment
> size to a higher value (default is 512 MBytes), for
> example to 1 GByte by
>
> kern.maxdsiz=1073741824
>
> You have to reboot the system.
Will do this in about 8 hours.
M
--
Mark R V Murray - Cert AP
org; [EMAIL PROTECTED]
> Subject: [Axiom-developer] Re: [Gcl-devel] Re: gcl-2.7.0 on FreeBSD
>
> Camm Maguire writes:
> > Greetings!
> >
> > BSD appears to start the shared library loading relatively low:
> >
> > checking for shared library/C stack ceilin
Camm Maguire writes:
> Greetings!
>
> BSD appears to start the shared library loading relatively low:
>
> checking for shared library/C stack ceiling to heap... 0x280ad000
>
> (Linux starts at 0x4000)
>
> This will cut available memory in half on bsd.
>
> Is there a workaround?
I haven't
Greetings!
BSD appears to start the shared library loading relatively low:
checking for shared library/C stack ceiling to heap... 0x280ad000
(Linux starts at 0x4000)
This will cut available memory in half on bsd.
Is there a workaround?
Take care,
--
Camm Maguire
