On Sunday 01 January 2006 17:41, you wrote: > Hi, > > Ok, the situation is a bit more clear now... The problem is that erlang's > build system assumes that sparc automatically means ultrasparc and (if > hipe is enabled) automatically turns on all the ultrasparc-specific > optimizations. That's a problem, because we, at this point, still support > the 32-bit hardware, and so ultrasparc-optimized binaries will not work > out of the box on older machines. > > I see two ways out of this situation. The easy one is to disable hipe on > sparc. As I understand, that will turn off all the processor-specific > optimizations and should build fine on the buildds. The harder one is to > produce two sets of packages - one with hipe enabled and thus > ultrasparc-optimized, the other one with hipe disabled, and thus suitable > for sparc32 hardware. Whatever the decision is going to be, I'll be glad > test out the packages and advise on the proper way to build them. >
You might have seen that with 10.b.9-1, I already build an hipe-enabled runtime and a traditionnal runtime, erlang-base-hipe and erlang-base. It would be easy for me to make a special case for sparc architecture to make it build only the interpreted runtime. I will still be forwarding this to erlang-questions. The more clue they have the better. Good work on this issue. I would not have been able to tackle this on my own.
pgpuTM3Ui0YSh.pgp
Description: PGP signature
