From: Christian G. <cg...@hq...> - 2003-04-10 23:03:05
|
>> If this poster is still on the list, could you provide >> some additional details about your environment? I am >> on Solaris 2.6, perl 5.004_04. There was no Policy.sh >> in this release and the Configure script autodetects >> the byte order to be 4321. I have tried it with 4321 >> and 1234 and still the spawned process hangs. > I am not said poster, but my understanding is that byte order changes > from 4321 to 2143, swapping bytes in the word. I was the inital poster, and I was using perl 5.6.1. I do not know if this option is implemented on perl 5.004_04. I also think that Policy.sh is something that gets generated by running ./Configure, for you to use later. In my build process, this allows to pre-define configration variables and then run ./Configure -der to merge your values with the autodetected values. I can confirm that the byte order autodetected by ./Configure is "4321", and that the configuration variable to use is "byteorder", at least for 5.6.1. My problem was that this auto-detection is turned off when I had some other option turned on... -- cg |