I had to add a little hack to t/configure/132-auto_arch-02.t because it
was throwing an uninitialized value warning when being run on Darwin. 
This hack was needed because there's a hack inside auto::arch dealing
with Darwin and byteorder.  Since the tests, as currently constructed,
do not have all the information in the Parrot::Configure object as that
object does during regular configuration, there are points where the
value of an attribute in that object is sought but not found.  This
cleans up the test; actual configuration is not affected one way or the
other.

kid51

Reply via email to