[m-users.] No rule to make target

[Julien Fischer]

Hi Carlos,

On Thu, 27 May 2021, Carlos de la Villa wrote:

> Thanks for the assist Julien. I downloaded mercury-srcdist-20.06.1 and
> unpacked inside my cygwin terminal, version 3.2.0(0.340/5/3) as seen
> after running `uname -r`. I'm running Windows 10 Pro version 20H2, OS
> Build 19042.985. I have both gcc and clang installed in this
> environment and gave no flags to the configuration script so I'm
> unsure which C compiler it's invoking by default. I once tried the
> flag --with-llds-base-grade=none after some research but saw no
> difference in result.

Since you didn't provide any flags to the configure script, make install
will try to install Mercury in /usr/local/mercury-20.06.  I suspect the
problem may simply be not having permission to write to /usr/local in
Cygwin.

You can use configure's --prefix option to set an alternative
installation directory that you do have permission to write to.

Julien.

> On Wed, May 26, 2021, 22:34 Julien Fischer <jfischer at opturion.com> wrote:
>
>       Hi,
>
>       On Wed, 26 May 2021, Carlos de la Villa wrote:
>
>       > Hello all, I hope this is going to the right place.
>
>       It is.
>
>       > Has anyone ever had the installation issue that `make install` doesn't
>       > have a rule for `/tmp/mmake.xxxxxx` (the "extension" seems to change
>       > every time I `sh configure`)?
>
>       The extension changing each time is expected.
>
>       > When I `sh configure` most things come
>       > back as yes. It doesn't error out at any point. However, when I `make
>       > install` I get that error. What am I missing?
>
>       You haven't provided sufficient information to say.
>
>       - What version of Mercury is this?
>       - What OS (and what version of it) is is this occurring?
>       - What C compiler (and what version of it) are you using?
>       - Did you pass any other flags to the configure script when
>       you invoked it?
>
>       Julien.
> 
> 
>