Skip to contentSkip to conversation

gpm: run autogen.sh as PRE_CONFIGURE step

PATCH New Ryan Barnett 2 participants 2 messages Feb 4, 2014

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 gpm: run autogen.sh as PRE_CONFIGURE step

Move the GPM_RUN_AUTOGEN to be a PRE_CONFIGURE step because this step depends on the dependancies being built. If it is a POST_PATCH step the dependancies won't be built and the GPM_RUN_AUTOGEN step will fail.

---
 package/gpm/gpm.mk | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
package/gpm/gpm.mk +1 -1
index 296966a..58fab00 100644
@@ -28,7 +28,7 @@ GPM_CONF_OPT = --without-curses
 define GPM_RUN_AUTOGEN
 	cd $(@D) && PATH=$(HOST_PATH) ./autogen.sh
 endef
-GPM_POST_PATCH_HOOKS += GPM_RUN_AUTOGEN
+GPM_PRE_CONFIGURE_HOOKS += GPM_RUN_AUTOGEN
 
 GPM_DEPENDENCIES += host-automake host-autoconf host-libtool
 
Signature · 1 line
1.8.3.2
#1 lore raw

PATCH 1/1 gpm: run autogen.sh as PRE_CONFIGURE step

Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Ryan" == Ryan Barnett <[email protected]> writes:

Move the GPM_RUN_AUTOGEN to be a PRE_CONFIGURE step because this step depends on the dependancies being built. If it is a POST_PATCH step the dependancies won't be built and the GPM_RUN_AUTOGEN step will fail.

Committed, thanks.

Signature · 1 line
Bye, Peter Korsgaard