On 06/07/2011 05:23 PM, Martin Langhoff wrote:
I am hacking on a slighly modified kernel spec file for an OLPC arm
test kernel. While chasing strange build errors, I find that
%{image_install_path} isn't always being expanded.
The resulting build script looks like
http://fpaste.org/LQwR/#82
where %{image_install_path}, defined earlier as 'boot' hasn't been expanded.
Any debugging hints?
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.
Another possibility that comes to mind is funny side-effects from
BuildArch which can cause similar effects, but this time use of %global
being the problem:
https://bugzilla.redhat.com/show_bug.cgi?id=593363
- Panu -