The configure file is autogenerated and distributed only with releases (this is typically the case with projects using autotools). Thus the development version does not contain configure.
You can use autoreconf -i to generate the configure file.
On Thu, Jan 5, 2017 at 12:40 AM, Ask Hjorth Larsen <email address hidden>
wrote:
> The configure file is autogenerated and distributed only with releases
> (this is typically the case with projects using autotools). Thus the
> development version does not contain configure.
>
> You can use autoreconf -i to generate the configure file.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1652743
>
> Title:
> absent configure script
>
> Status in LibXC:
> New
>
> Bug description:
> Hello,
>
> I could not find configure script in trunk. How to compile ?
>
> Peter
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/libxc/+bug/1652743/+subscriptions
>
> Can this bug be considered closed?
>
> I believe the active bug site for libxc is here:
> http://www.tddft.org/trac/libxc/
>
> Will take the liberty of closing this one.
>
> ** Changed in: libxc
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1652743
>
> Title:
> absent configure script
>
> Status in LibXC:
> Invalid
>
> Bug description:
> Hello,
>
> I could not find configure script in trunk. How to compile ?
>
> Peter
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/libxc/+bug/1652743/+subscriptions
>
The configure file is autogenerated and distributed only with releases (this is typically the case with projects using autotools). Thus the development version does not contain configure.
You can use autoreconf -i to generate the configure file.