> poudriere only installs BUILD_DEPENDS for current package but a regular
> build would also do so for any dependencies. Probably one of those pulls
> devel/pkgconf (aka USES=pkgconfig) which is what provides PKG_CHECK_MODULES.
Aha, yeah you're right!
I mistakenly had pkgconfig:run in my Makefile
mokhi writes:
>> The error often originates from undefined macros provided by other packages
>> e.g.,
> Yeah, as far as I understood, the `PKG_CHECK_MODULES` is not
> translated to its definition in first run.
> But the weird point for me is that why it will be corrected in second
> run (inside
> Can you pass -w flag to poudriere bulk command then inspect the specific
> line?
My guess was correct,
As I previously told, the generated `configure` script in first `make`
run and in second, differs.
> The error often originates from undefined macros provided by other packages
> e.g.,
Yeah
mokhi writes:
[...]
> [1] ./configure: 7063: Syntax error: newline unexpected (expecting ")")
> ===> Script "configure" failed unexpectedly.
Can you pass -w flag to poudriere bulk command then inspect the specific line?
The error often originates from undefined macros provided by other packages
Hi.
I'm trying to port an application that uses 'configure.ac' and
'makefile.am' for its building.
I used `USES= autoreconf` in my Makefile.
When I test it with poudriere, It fails for incorrect syntax in
configure script as it says[1]
But the weird point (for me :D) is when I go into poudriere ja
