#1504: config/auto/arch.pm: Uninitialized value warning on Darwin due to change
in order of configuration steps
-----------------------+----------------------------------------------------
Reporter: jkeenan | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: configure | Version: 2.1.0
Severity: medium | Keywords: configure byteorder arch
Lang: | Patch:
Platform: darwin |
-----------------------+----------------------------------------------------
Comment(by jkeenan):
Replying to [comment:3 coke]:
...
> Sure - init::optimize now has a dependency on the config flag 'cpuarch',
so the steps that calculate this information need to come before
init:optimize; so we moved those 2, but didn't follow the full chain of
dependencies. (This is one of the reasons why I want to eventually move
all this stuff to a mini makefile, since then we can easily declare our
step dependencies and the let the tool figure out what order to run things
in.)
Yes, I was bedeviled by those difficult-to-follow dependencies when I was
writing tests for the config steps.
Will try to absorb AndyD's suggestion and continue to investigate.
kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1504#comment:5>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
