On Tue, Jun 7, 2011 at 11:46 AM, Panu Matilainen
<pmatilai(a)laiskiainen.org> wrote:
Hard to say without the entire spec, but one typical cause of
"sometimes
works sometimes doesn't" issues with macros are %define's inside macro
{} blocks, which "work" until the first parametrized macro is called,
and after that it doesn't (due to an ancient flaw in the macro engine).
Replacing the %define inside {} with %global helps in this case.
Ouch! that sounds extra painful.
After a few more attempts I found that the macro was being initialized
per arch, and my arch wasn't setting it properly.
Didn't spot any 'undefined macro' warning in the output, but then
again I only tried with one '-v' param.
thanks!
m
--
martin.langhoff(a)gmail.com
martin(a)laptop.org -- Software Architect - OLPC
- ask interesting questions
- don't get distracted with shiny stuff - working code first
-
http://wiki.laptop.org/go/User:Martinlanghoff