Hm, that's true. Well, possibly the right fix would be to implement
do-configure target, as piggy-backing on GNU_CONFIGURE doesn't work well
anyhow... Lemme think about it.
With regards,
Timur Bakeyev.
On Mon, Nov 25, 2013 at 4:15 PM, Marcus von Appen <m...@freebsd.org> wrote:
> On, Mon Nov 25, 2013, Timur I. Bakeyev wrote:
>
> > Hi, Marcus!
> >
> > I see this patch as useless, as WAF isn't called via shebang.
> >
> > Please, take a closer look onto port's Makefile.
>
> It is called via shebang in the configure stage. do-configure (from
> bsd.port.mk) expands to:
>
> ${CONFIGURE_ENV} ./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS} ...
>
> which effectively will become:
>
> ${CONFIGURE_ENV} ./buildtools/bin/waf configure ${CONFIGURE_ARGS} ...
>
> And this is where it breaks:
>
> /usr/ports/databases/ldb # make configure
> [...]
> ===> Configuring for ldb-1.1.16
> env: python: No such file or directory
> ===> Script "buildtools/bin/waf configure" failed unexpectedly.
>
> Cheers
> Marcus
>
_______________________________________________
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
