Royce,

please remember were MAKE is coming from. "\" is an escape character in
UNIX so if you change your path delimiter to "/" it will work as
expected. BTW Windows can handle "/" instead of "\" except the the
command line IF does not accept "/".

It's not a bug it is M$😉.

Cheers,
Knut

Am 14.10.21 um 12:50 schrieb Royce Pereira:
Yes, I found the bug - a recently installed (I wanted to give it a
try) toolchain from here:
Fast Cross-Platform App Development Software - Embarcadero
<https://www.embarcadero.com/>
It had written its own path variables with the path to its own make.

I had uninstalled it later, but it did not delete the path entries.
after deleting them manually, problem solved1

Thank you !!

On Thu, 14 Oct 2021 at 11:50, <dva...@internode.on.net
<mailto:dva...@internode.on.net>> wrote:


    On 13.10.21 17:31, Royce Pereira wrote:
       > Today I started getting this error when i run make:
       >
       > make: *** No rule to make target
    `c\:\avr-gcc\avr\include\avr\io.h', needed
       > by `Timer-5D-DD-0715.o'.  Stop.

    While I'm rusty on make these days, ISTM that there is something wrong
    with the makefile, as io.h should not be a target. Headers are
    included
    in source files for targets (xx.o), not built separately. It is then
    unsurprising that there is no rule for no build.

    Listing io.h as a dependency, either on the target line, or as a
    separate dependency:

    Timer-5D-DD-0715.o: io.h

    will tell make to rebuild the target if io.h has changed, but only an
    erroneous placement of io.h as a target ought to create your current
    problem ... in theory.

    Even if you use suffix rules, .h should only appear on the right
    of the
    colon.

    If you would post the makefile, it may be possible to spot the
    problem.

    > The offending part is the slash after c (C\:\)

    That may be just a display artifact, escaping perhaps.

    > I checked for typos in my makefile, but it's happening with all
    my projects.

    Is there really only one makefile?

    > Note:
    >  I'm using windows 10 and make.exe is in :
    >
    > C:\MinGW\msys\1.0\bin\make.exe
    >
    > Which is defined in my path.

    An instance of make is being run - it announced itself in the error
    message. For completeness, is it gnu make or some lesser imitation?
    Has that been upgraded recently? (With a buggy version.)

    Erik

    P.S. CCing as last two posts to other lists didn't make it to list.

    --
    The difference between theory and practice is much smaller in theory
    than in practice.



--
Best Regards,

-- Royce Pereira

Reply via email to