Steve Langasek writes: > Side note -- sparc does have a "sparc32" util that can be used to change the > kernel personality that a process is running under (i.e., it changes the > output of uname among other things...), and I believe the official buildds > run all builds under sparc32 to avoid precisely these issues. Julien, can > you confirm whether mozart/mozart-gtk build for you under sparc32? > > It's still a bug in these packages if they're looking at the value of uname > instead of the architecture string from configure (in this case, one that's > been passed *explicitly* on the commandline!), but there's no reason it > should need to be RC if sparc32 works around it.
Mozart is a platform specific emulator and platform agnostic byte codes all living in the same place. Upstream supports many platforms sharing a common installation (in shared filespace) by dynamically finding the right emulator by calling uname .... For debian we do things different. I can modify our package to map sparc64 to sparc-linux and all will work (if sparc64 really is 32 bit), but I don't think this is a change I could feed to upstream. I don't think running the build under sparc32 is a solution because it means the users will have to also invoke mozart/oz under sparc32. cheers k -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
