Looks good to me
/Erik
On 2013-09-11 14:00, Magnus Ihse Bursie wrote:
Autoconf creates by default a config.log in the current directory. Our
configure script moves this file to the directory created for the
configuration (e.g. build/linux...etc).
A previous fix launching the generated config
On 2013-09-11 23:08, Dalibor Topic wrote:
I haven't dug into the code much, but why not use AC_CONFIG_COMMANDS [0] ?
cheers,
dalibor topic
[06
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Configuration-Commands.html#Configuration-Commands
I haven't actua
On 9/11/13 2:00 PM, Magnus Ihse Bursie wrote:
> Autoconf creates by default a config.log in the current directory. Our
> configure script moves this file to the directory created for the
> configuration (e.g. build/linux...etc).
>
> A previous fix launching the generated configure file in a subs
Autoconf creates by default a config.log in the current directory. Our
configure script moves this file to the directory created for the
configuration (e.g. build/linux...etc).
A previous fix launching the generated configure file in a subshell made
the move to fail, since the directory name w
