From: Jim W. <jw...@dr...> - 2011-02-16 21:54:55
|
Jim Wise <jw...@dr...> writes: > Jim Wise <jw...@dr...> writes: > >> Juho Snellman <js...@ik...> writes: >> >>> Now that sourceforge is finally back, it's time for a long overdue release. I'll do it this weekend, so until then testing good, breaking more stuff bad. >> >> Cool! Solaris support for x86_64 will be broken in this release due to >> page size issues (1.0.45 works fine, and is on the download page) -- I'm >> working on this, but won't have a fix in for 1.0.46. Solaris x86 works >> fine, and I'll upload a build as soon as the release is tagged. > > Actually, I have a fix for the Solaris x86_64 thing which I'll put on > launchpad tomorrow morning (still testing the best way to integrate > this). > > So, if I can fix the sb-posix readdir thing in time for this weekend, > 1.0.46 can include builds for both Solaris x86 and Solaris x86_64. So, this boils down to revision 1.5 of src/compiler/x86_64/backend-parms.lisp, which changed the compiled-in value of *backend-page-bytes* from 4k to 32k, which Solaris x86-64 can't support in the default configuration. Changing this back to 4k makes Solaris work, but would have a performance impact on other platforms. This is easy enough to control with #!+sunos, but I want to make sure that I understand how this will affect cross-compilation -- I don't want to tie a build cross-compiled from Solaris for another x86-64 port to a 4k pagesize, and I don't want builds cross-compiled for Solaris from another port to create non-working binaries. How are #! read-time conditionals are set when cross-compiling? Thanks, -- Jim Wise jw...@dr... |