Closed yegle closed 13 years ago
sorry, should be "../buidtools/bin/waf" :-)
I have no WAF installed either and I set the PATH variable to include ../buildtools/bin. See https://github.com/webkiller71/samba4/blob/master/net-fs/samba/samba-4.0.0_alpha13.ebuild#L44
It's strange, I still got "command not found" error...
Which portage version are you using? Perhaps setting PATH the way I did is not allowed.
System uname: Linux-2.6.37-rc2-git1-x86_64-Intel-R-_Core-TM-_i5_CPU_M450@_2.40GHz-with-gentoo-2.0.1 Timestamp of tree: Fri, 26 Nov 2010 01:00:01 +0000 app-shells/bash: 4.1_p9 dev-java/java-config: 2.1.11-r2 dev-lang/python: 2.6.6-r1, 3.1.2-r4 dev-util/cmake: 2.8.1-r2 sys-apps/baselayout: 2.0.1-r1 sys-apps/openrc: 0.6.5-r1::sabayon sys-apps/sandbox: 2.4 sys-devel/autoconf: 2.13, 2.68 sys-devel/automake: 1.9.6-r3, 1.10.3, 1.11.1 sys-devel/binutils: 2.20.1-r1 sys-devel/gcc: 4.4.5, 4.5.1-r1 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.4 sys-devel/make: 3.82 virtual/os-headers: 2.6.36.1 (sys-kernel/linux-headers)
I'm using portage 2.1.8.3 which might explain a difference. Does 15f7705ac799d34288420f152b63e4bf1c7c1035 solve it for you?
Yes it works, thank you :-)
For most people, the waf is not installed in PATH. So it should be "../buildtools/waf" when referring waf in your ebuild :-)