This change breaks my arm build:
384fed00 (Dave Jones 2012-03-19 17:30:04 -0400 1485)
-for i in *.config +for i in kernel-*-$(uname -p)*.config
"uname -p" returns armv7l but the configs we use are more varied than that:
$(CFG)-arm.config $(CFG)-armv5tel.config $(CFG)-armv7hl.config \ $(CFG)-armv5tel-kirkwood.config \ $(CFG)-armv7l-imx.config $(CFG)-armv7l-omap.config \ $(CFG)-armv7l-tegra.config $(CFG)-armv7l-highbank.config \ $(CFG)-armv7hl-imx.config $(CFG)-armv7hl-omap.config \ $(CFG)-armv7hl-tegra.config $(CFG)-armv7hl-highbank.config \
Typically, we use "rpmbuild --target=armv7hl" to specify the platform to build for, do we need to change the way we're doing things? Is --target no longer supported?
On Thu, Mar 29, 2012 at 6:37 AM, DJ Delorie dj@delorie.com wrote:
This change breaks my arm build:
384fed00 (Dave Jones 2012-03-19 17:30:04 -0400 1485)
-for i in *.config +for i in kernel-*-$(uname -p)*.config
"uname -p" returns armv7l but the configs we use are more varied than that:
$(CFG)-arm.config $(CFG)-armv5tel.config $(CFG)-armv7hl.config \ $(CFG)-armv5tel-kirkwood.config \ $(CFG)-armv7l-imx.config $(CFG)-armv7l-omap.config \ $(CFG)-armv7l-tegra.config $(CFG)-armv7l-highbank.config \ $(CFG)-armv7hl-imx.config $(CFG)-armv7hl-omap.config \ $(CFG)-armv7hl-tegra.config $(CFG)-armv7hl-highbank.config \
Typically, we use "rpmbuild --target=armv7hl" to specify the platform to build for, do we need to change the way we're doing things? Is --target no longer supported?
This change seems to be in the kernel.spec and not in any of the scripts. I wonder if %_target_cpu should not be used instead?
Cheers, Niels
On Thu, Mar 29, 2012 at 02:34:38PM +0200, Niels de Vos wrote:
Typically, we use "rpmbuild --target=armv7hl" to specify the platform to build for, do we need to change the way we're doing things? Is --target no longer supported?
This change seems to be in the kernel.spec and not in any of the scripts. I wonder if %_target_cpu should not be used instead?
changed. thanks.
Dave
kernel@lists.fedoraproject.org