There’s just one glitch, the name of the build directory is determined by
BUILD = $(shell ../../scripts/findhost.sh $(shell src/config.guess))
I can set it after the extract phase like so
post-extract {
set builddir [exec ${worksrcpath}/scripts/findhost.sh [exec
${worksrcpath}/config.guess]]
configure.dir ${worksrcdir}/${builddir}
}
but then configure.dir isn't global for the config/build phases, is it?
Mark Brethen
[email protected]
> On Oct 4, 2018, at 10:04 AM, Ryan Schmidt <[email protected]> wrote:
>
>
>
> On Oct 4, 2018, at 09:24, Mark Brethen wrote:
>
>> I’m not sure how to handle this build setup: in the top directory there is a
>> makefile but the configure files are in a subdirectory “src”. The makefile
>> handles it thusly,
>>
>> all:
>> cd src; \
>> autoconf; \
>> autoheader
>> mkdir -p $(BUILD); \
>> cd $(BUILD); \
>> ../src/configure --disable-universal; \
>> $(MAKE)
>>
>> and so I get the following error:
>>
>> ---> Configuring libreduce
>> Error: Failed to configure libreduce: configure failure: command execution
>> failed
>> Error: See
>> /opt/local/var/macports/logs/_Users_marbre_ports_math_reduce/libreduce/main.log
>> for details.
>> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
>> Error: Processing of port libreduce failed
>>
>> If I use 'use_configure no’ in my portfile then it won’t configure the way
>> macport’s intends.
>
> Sounds like you should do something like:
>
>
> use_autoreconf yes
> autoreconf.dir ${worksrcpath}/src
>
> configure.dir ${workpath}/build
> configure.cmd ${autoreconf.dir}/configure
>
> pre-configure {
> xinstall -d ${configure.dir}
> }
>
> build.dir ${configure.dir}
