Re: Strange new error in make

2021-10-15 Thread Knut Schwichtenberg

Royce,

there is another good way to create a problem: If you use -MD to create
dependencies make can also crash with a strange message. This happens
mostly at the second run. Also here the "\" is the problem. The way to
get around this is use -MMD, remove the dependency files (mostly with .d
extension) and restart.  And whenever you are using paths within your
#include statement use "/".
That's all I've learned concerning dual usage of makefiles for M$ and
any UNIX / Linux

Cheers,
Knut.

On 14.10.21 22:17, Knut Schwichtenberg wrote:


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






Re: Strange new error in make

2021-10-14 Thread Knut Schwichtenberg

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

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, 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


Re: Strange new error in make

2021-10-14 Thread 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

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,  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


Re: Strange new error in make

2021-10-14 Thread dvalin

 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-gccavrincludeavrio.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:MinGWmsys1.0binmake.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.



Strange new error in make

2021-10-13 Thread Royce Pereira
Hi,

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.

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

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

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.

Please advise. Thank you!
-- 
Best Regards,

-- Royce Pereira


Re: error in make

2020-09-26 Thread Royce Pereira
Anyways the latest version of 'make' (4.2.1) does not seem to have this
error (so far).

I found i was using an older version (3.8.1). Once I upgraded, the error
did not appear.

This coincided with my upgrading avr-gcc to 10.1.
So maybe that had something to do with it, especially since I've been using
the same make.exe from avr-gcc 8.2 without this error, till I upgraded to
avr-gcc 10.1


On Sat, 26 Sep 2020, 20:04 Dave Hylands,  wrote:

> I’m going to guess that the problem is coming from the generated
> dependency files. You may need to massage them after generating them.
>
> On Sat, Sep 26, 2020 at 1:52 AM Nigel Winterbottom <
> winterbottom.ni...@gmail.com> wrote:
>
>> I've seen something similar when building from a "DOS" command prompt.
>> When building from a bash shell, however, as one can after installing Git
>> For Windows" those strange errors disappear..
>>
>> Another thing you can try is:
>> make --dry-run
>> You can examine the commands that make would generate for any errors.
>>
>>
>> -- Nigel
>>
>> On Fri, 25 Sep 2020 at 11:48, Georg-Johann Lay  wrote:
>>
>>> Royce Pereira schrieb:
>>>
>>>
>>> > Hi,
>>>
>>>
>>> >
>>>
>>>
>>> > The problem continues.
>>>
>>>
>>> >
>>>
>>>
>>> > it compiles without error once I delete all the generated files, but
>>> the
>>>
>>>
>>> > next time (even with 'make clean all' I get the same error from make:
>>>
>>>
>>> >
>>>
>>>
>>> > "make": *** No rule to make target `c\:\avr-gcc\avr\include\avr\io.h',
>>>
>>>
>>> > needed by `MIXER-72x75-0920.o'.  Stop.
>>>
>>>
>>>
>>>
>>>
>>> This does not look like a reasonable file name.  c\:\avr-gcc\...
>>>
>>>
>>>
>>>
>>>
>>> Where do you get it from?
>>>
>>>
>>>
>>>
>>>
>>> Johann
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> --
> Dave Hylands
> Peachland, BC, Canada
> http://www.davehylands.com
>


Re: error in make

2020-09-26 Thread Dave Hylands
I’m going to guess that the problem is coming from the generated dependency
files. You may need to massage them after generating them.

On Sat, Sep 26, 2020 at 1:52 AM Nigel Winterbottom <
winterbottom.ni...@gmail.com> wrote:

> I've seen something similar when building from a "DOS" command prompt.
> When building from a bash shell, however, as one can after installing Git
> For Windows" those strange errors disappear..
>
> Another thing you can try is:
> make --dry-run
> You can examine the commands that make would generate for any errors.
>
>
> -- Nigel
>
> On Fri, 25 Sep 2020 at 11:48, Georg-Johann Lay  wrote:
>
>> Royce Pereira schrieb:
>>
>>
>> > Hi,
>>
>>
>> >
>>
>>
>> > The problem continues.
>>
>>
>> >
>>
>>
>> > it compiles without error once I delete all the generated files, but the
>>
>>
>> > next time (even with 'make clean all' I get the same error from make:
>>
>>
>> >
>>
>>
>> > "make": *** No rule to make target `c\:\avr-gcc\avr\include\avr\io.h',
>>
>>
>> > needed by `MIXER-72x75-0920.o'.  Stop.
>>
>>
>>
>>
>>
>> This does not look like a reasonable file name.  c\:\avr-gcc\...
>>
>>
>>
>>
>>
>> Where do you get it from?
>>
>>
>>
>>
>>
>> Johann
>>
>>
>>
>>
>>
>>
>
> --
Dave Hylands
Peachland, BC, Canada
http://www.davehylands.com


Re: error in make

2020-09-26 Thread Nigel Winterbottom
I've seen something similar when building from a "DOS" command prompt. When
building from a bash shell, however, as one can after installing Git For
Windows" those strange errors disappear..

Another thing you can try is:
make --dry-run
You can examine the commands that make would generate for any errors.

-- Nigel

On Fri, 25 Sep 2020 at 11:48, Georg-Johann Lay  wrote:

> Royce Pereira schrieb:
> > Hi,
> >
> > The problem continues.
> >
> > it compiles without error once I delete all the generated files, but the
> > next time (even with 'make clean all' I get the same error from make:
> >
> > "make": *** No rule to make target `c\:\avr-gcc\avr\include\avr\io.h',
> > needed by `MIXER-72x75-0920.o'.  Stop.
>
> This does not look like a reasonable file name.  c\:\avr-gcc\...
>
> Where do you get it from?
>
> Johann
>
>


Re: error in make

2020-09-25 Thread Georg-Johann Lay

Royce Pereira schrieb:

Hi,

The problem continues.

it compiles without error once I delete all the generated files, but the
next time (even with 'make clean all' I get the same error from make:

"make": *** No rule to make target `c\:\avr-gcc\avr\include\avr\io.h',
needed by `MIXER-72x75-0920.o'.  Stop.


This does not look like a reasonable file name.  c\:\avr-gcc\...

Where do you get it from?

Johann



Re: error in make

2020-09-25 Thread Peter C++
Royce

While neither an expert in the given makefile nor windows I suggest you look 
into the dependencies file that are included and generated by your makefile. 
They seem to lie in the directory .dep/

There seem some problem with the mechanism it generates paths on your windows 
system. 

Regards
Peter

sent from a mobile device so please excuse strange words due to autocorrection. 
Peter Sommerlad
peter@sommerlad.ch
+41-79-432 23 32

> On 25 Sep 2020, at 10:50, Royce Pereira  wrote:
> 
> 
> Hi,
> 
> The problem continues.
> 
> it compiles without error once I delete all the generated files, but the next 
> time (even with 'make clean all' I get the same error from make:
> 
> "make": *** No rule to make target `c\:\avr-gcc\avr\include\avr\io.h', needed 
> by `MIXER-72x75-0920.o'.  Stop.
> 
> Again, this is probably because of the invalid path above (c\;\...) but i 
> cant figure out the source of this invalid path.
> 
> Could someone kindly shed some light on this? Thanks!
> 
>> On Tue, 22 Sep 2020 at 15:13, Royce Pereira  wrote:
>> Hi,
>> 
>> Ok, I deleted all generated files save my c file.
>> 
>> Now the error is not displayed, and the project compiles.
>> 
>> However, it would be interesting to know what causes it !
>> 
>> Thank you,
>> 
>>> On Tue, 22 Sep 2020 at 15:08, Royce Pereira  wrote:
>>> Hi,
>>> 
>>> Recently I am getting a strange error while  trying to 'make' my project.
>>> 
>>> "make": *** No rule to make target `c\:\avr-gcc\avr\include\avr\io.h', 
>>> needed by `MIXER-72x75-0920.o'.  Stop.
>>> 
>>> it was working fine until recently. I may have unknowingly modified 
>>> something, but i can't figure out the problem. i can tell c\:\ ... is an 
>>> invalid path, but i can't find the offending line.
>>> My knowledge of makfile is limited.
>>> 
>>> Here is my makefile;
>>> 
>>> # Hey Emacs, this is a -*- makefile -*-
>>> #
>>> # WinAVR Makefile Template written by Eric B. Weddington, Jörg Wunsch, et 
>>> al.
>>> #
>>> # Released to the Public Domain
>>> #
>>> # Additional material for this makefile was written by:
>>> # Peter Fleury
>>> # Tim Henigan
>>> # Colin O'Flynn
>>> # Reiner Patommel
>>> # Markus Pfaff
>>> # Sander Pool
>>> # Frederik Rouleau
>>> #
>>> #
>>> # On command line:
>>> #
>>> # make all = Make software.
>>> #
>>> # make clean = Clean out built project files.
>>> #
>>> # make coff = Convert ELF to AVR COFF.
>>> #
>>> # make extcoff = Convert ELF to AVR Extended COFF.
>>> #
>>> # make program = Download the hex file to the device, using avrdude.
>>> #Please customize the avrdude settings below first!
>>> #
>>> # make debug = Start either simulavr or avarice as specified for debugging, 
>>> #  with avr-gdb or avr-insight as the front end for debugging.
>>> #
>>> # make filename.s = Just compile filename.c into the assembler code only.
>>> #
>>> # make filename.i = Create a preprocessed source file for use in submitting
>>> #   bug reports to the GCC project.
>>> #
>>> # To rebuild project do "make clean" then "make all".
>>> #
>>> 
>>> 
>>> # MCU name
>>> MCU = atmega8
>>> 
>>> 
>>> # Processor frequency.
>>> # This will define a symbol, F_CPU, in all source code files equal to 
>>> the 
>>> # processor frequency. You can then use this symbol in your source code 
>>> to 
>>> # calculate timings. Do NOT tack on a 'UL' at the end, this will be done
>>> # automatically to create a 32-bit value in your source code.
>>> F_CPU = 100
>>> 
>>> 
>>> # Output format. (can be srec, ihex, binary)
>>> FORMAT = ihex
>>> 
>>> 
>>> # Target file name (without extension).
>>> TARGET = MIXER-72x75-0920
>>> 
>>> 
>>> # List C source files here. (C dependencies are automatically generated.)
>>> SRC = $(TARGET).c
>>> 
>>> 
>>> # List Assembler source files here.
>>> # Make them always end 

Re: error in make

2020-09-25 Thread Royce Pereira
Hi,

The problem continues.

it compiles without error once I delete all the generated files, but the
next time (even with 'make clean all' I get the same error from make:

"make": *** No rule to make target `c\:\avr-gcc\avr\include\avr\io.h',
needed by `MIXER-72x75-0920.o'.  Stop.

Again, this is probably because of the invalid path above (c\;\...) but i
cant figure out the source of this invalid path.

Could someone kindly shed some light on this? Thanks!

On Tue, 22 Sep 2020 at 15:13, Royce Pereira  wrote:

> Hi,
>
> Ok, I deleted all generated files save my c file.
>
> Now the error is not displayed, and the project compiles.
>
> However, it would be interesting to know what causes it !
>
> Thank you,
>
> On Tue, 22 Sep 2020 at 15:08, Royce Pereira  wrote:
>
>> Hi,
>>
>> Recently I am getting a strange error while  trying to 'make' my project.
>>
>> "make": *** No rule to make target `c\:\avr-gcc\avr\include\avr\io.h',
>> needed by `MIXER-72x75-0920.o'.  Stop.
>>
>> it was working fine until recently. I may have unknowingly
>> modified something, but i can't figure out the problem. i can tell c\:\ ...
>> is an invalid path, but i can't find the offending line.
>> My knowledge of makfile is limited.
>>
>> Here is my makefile;
>>
>> # Hey Emacs, this is a -*- makefile -*-
>>
>> #
>> # WinAVR Makefile Template written by Eric B. Weddington, Jörg Wunsch, et
>> al.
>> #
>> # Released to the Public Domain
>> #
>> # Additional material for this makefile was written by:
>> # Peter Fleury
>> # Tim Henigan
>> # Colin O'Flynn
>> # Reiner Patommel
>> # Markus Pfaff
>> # Sander Pool
>> # Frederik Rouleau
>> #
>>
>> #
>> # On command line:
>> #
>> # make all = Make software.
>> #
>> # make clean = Clean out built project files.
>> #
>> # make coff = Convert ELF to AVR COFF.
>> #
>> # make extcoff = Convert ELF to AVR Extended COFF.
>> #
>> # make program = Download the hex file to the device, using avrdude.
>> #Please customize the avrdude settings below first!
>> #
>> # make debug = Start either simulavr or avarice as specified for
>> debugging,
>> #  with avr-gdb or avr-insight as the front end for debugging.
>> #
>> # make filename.s = Just compile filename.c into the assembler code only.
>> #
>> # make filename.i = Create a preprocessed source file for use in
>> submitting
>> #   bug reports to the GCC project.
>> #
>> # To rebuild project do "make clean" then "make all".
>>
>> #
>>
>>
>> # MCU name
>> MCU = atmega8
>>
>>
>> # Processor frequency.
>> # This will define a symbol, F_CPU, in all source code files equal to
>> the
>> # processor frequency. You can then use this symbol in your source
>> code to
>> # calculate timings. Do NOT tack on a 'UL' at the end, this will be
>> done
>> # automatically to create a 32-bit value in your source code.
>> F_CPU = 100
>>
>>
>> # Output format. (can be srec, ihex, binary)
>> FORMAT = ihex
>>
>>
>> # Target file name (without extension).
>> TARGET = MIXER-72x75-0920
>>
>>
>> # List C source files here. (C dependencies are automatically generated.)
>> SRC = $(TARGET).c
>>
>>
>> # List Assembler source files here.
>> # Make them always end in a capital .S.  Files ending in a lowercase
>> .s
>> # will not be considered source files but generated files (assembler
>> # output from the compiler), and will be deleted upon "make clean"!
>> # Even though the DOS/Win* filesystem matches both .s and .S the same,
>> # it will preserve the spelling of the filenames, and gcc itself does
>> # care about how the name is spelled on its command-line.
>> ASRC =
>>
>>
>> # Optimization level, can be [0, 1, 2, 3, s].
>> # 0 = turn off optimization. s = optimize for size.
>> # (Note: 3 is not always the best optimization level. See avr-libc
>> FAQ.)
>> OPT = s
>>
>>
>> # Debugging format.
>> # Native formats for AVR-GCC's -g are dwarf-2 [default] or stabs.
>> # AVR Studio 4.10 requires dwarf-2.
>> # 

Re: error in make

2020-09-22 Thread Royce Pereira
Hi,

Ok, I deleted all generated files save my c file.

Now the error is not displayed, and the project compiles.

However, it would be interesting to know what causes it !

Thank you,

On Tue, 22 Sep 2020 at 15:08, Royce Pereira  wrote:

> Hi,
>
> Recently I am getting a strange error while  trying to 'make' my project.
>
> "make": *** No rule to make target `c\:\avr-gcc\avr\include\avr\io.h',
> needed by `MIXER-72x75-0920.o'.  Stop.
>
> it was working fine until recently. I may have unknowingly
> modified something, but i can't figure out the problem. i can tell c\:\ ...
> is an invalid path, but i can't find the offending line.
> My knowledge of makfile is limited.
>
> Here is my makefile;
>
> # Hey Emacs, this is a -*- makefile -*-
>
> #
> # WinAVR Makefile Template written by Eric B. Weddington, Jörg Wunsch, et
> al.
> #
> # Released to the Public Domain
> #
> # Additional material for this makefile was written by:
> # Peter Fleury
> # Tim Henigan
> # Colin O'Flynn
> # Reiner Patommel
> # Markus Pfaff
> # Sander Pool
> # Frederik Rouleau
> #
>
> #
> # On command line:
> #
> # make all = Make software.
> #
> # make clean = Clean out built project files.
> #
> # make coff = Convert ELF to AVR COFF.
> #
> # make extcoff = Convert ELF to AVR Extended COFF.
> #
> # make program = Download the hex file to the device, using avrdude.
> #Please customize the avrdude settings below first!
> #
> # make debug = Start either simulavr or avarice as specified for
> debugging,
> #  with avr-gdb or avr-insight as the front end for debugging.
> #
> # make filename.s = Just compile filename.c into the assembler code only.
> #
> # make filename.i = Create a preprocessed source file for use in submitting
> #   bug reports to the GCC project.
> #
> # To rebuild project do "make clean" then "make all".
>
> #
>
>
> # MCU name
> MCU = atmega8
>
>
> # Processor frequency.
> # This will define a symbol, F_CPU, in all source code files equal to
> the
> # processor frequency. You can then use this symbol in your source
> code to
> # calculate timings. Do NOT tack on a 'UL' at the end, this will be
> done
> # automatically to create a 32-bit value in your source code.
> F_CPU = 100
>
>
> # Output format. (can be srec, ihex, binary)
> FORMAT = ihex
>
>
> # Target file name (without extension).
> TARGET = MIXER-72x75-0920
>
>
> # List C source files here. (C dependencies are automatically generated.)
> SRC = $(TARGET).c
>
>
> # List Assembler source files here.
> # Make them always end in a capital .S.  Files ending in a lowercase .s
> # will not be considered source files but generated files (assembler
> # output from the compiler), and will be deleted upon "make clean"!
> # Even though the DOS/Win* filesystem matches both .s and .S the same,
> # it will preserve the spelling of the filenames, and gcc itself does
> # care about how the name is spelled on its command-line.
> ASRC =
>
>
> # Optimization level, can be [0, 1, 2, 3, s].
> # 0 = turn off optimization. s = optimize for size.
> # (Note: 3 is not always the best optimization level. See avr-libc
> FAQ.)
> OPT = s
>
>
> # Debugging format.
> # Native formats for AVR-GCC's -g are dwarf-2 [default] or stabs.
> # AVR Studio 4.10 requires dwarf-2.
> # AVR [Extended] COFF format requires stabs, plus an avr-objcopy run.
> DEBUG = dwarf-2
>
>
> # List any extra directories to look for include files here.
> # Each directory must be seperated by a space.
> # Use forward slashes for directory separators.
> # For a directory that has spaces, enclose it in quotes.
> EXTRAINCDIRS = "D:\Google_Drive\AVR-gCC\AVR_inc"
>
>
> # Compiler flag to set the C Standard level.
> # c89   = "ANSI" C
> # gnu89 = c89 plus GCC extensions
> # c99   = ISO C99 standard (not yet fully implemented)
> # gnu99 = c99 plus GCC extensions
> CSTANDARD = -std=gnu99
>
>
> # Place -D or -U options here
> CDEFS = -DF_CPU=$(F_CPU)UL
>
>
> # Place -I options here
> CINCS =
>
>
>
> # Compiler Options 
> #  -g*:  generate debugging information
> #  -O*:  optimization level
> #  -f...:tuning, see GCC manual and avr-libc documentation
> #  -Wall...: warning level
> #  -Wa,...:  tell GCC to pass this to the assembler.
> #-adhlns...: create assembler listing
> CFLAGS = -g$(DEBUG)
> CFLAGS += $(CDEFS) $(CINCS)
> CFLAGS += -O$(OPT)
> CFLAGS += -funsigned-char -funsigned-bitfields -fpack-struct -fshort-enums
> CFLAGS += -Wall -Wstrict-prototypes
> CFLAGS += -Wa,-adhlns=$(<:.c=.lst)
> CFLAGS += $(patsubst %,-I%,$(EXTRAINCDIRS))
> CFLAGS += $(CSTANDARD)
>
>
> # Assembler Options 

error in make

2020-09-22 Thread Royce Pereira
Hi,

Recently I am getting a strange error while  trying to 'make' my project.

"make": *** No rule to make target `c\:\avr-gcc\avr\include\avr\io.h',
needed by `MIXER-72x75-0920.o'.  Stop.

it was working fine until recently. I may have unknowingly
modified something, but i can't figure out the problem. i can tell c\:\ ...
is an invalid path, but i can't find the offending line.
My knowledge of makfile is limited.

Here is my makefile;

# Hey Emacs, this is a -*- makefile -*-
#
# WinAVR Makefile Template written by Eric B. Weddington, Jörg Wunsch, et
al.
#
# Released to the Public Domain
#
# Additional material for this makefile was written by:
# Peter Fleury
# Tim Henigan
# Colin O'Flynn
# Reiner Patommel
# Markus Pfaff
# Sander Pool
# Frederik Rouleau
#
#
# On command line:
#
# make all = Make software.
#
# make clean = Clean out built project files.
#
# make coff = Convert ELF to AVR COFF.
#
# make extcoff = Convert ELF to AVR Extended COFF.
#
# make program = Download the hex file to the device, using avrdude.
#Please customize the avrdude settings below first!
#
# make debug = Start either simulavr or avarice as specified for debugging,
#  with avr-gdb or avr-insight as the front end for debugging.
#
# make filename.s = Just compile filename.c into the assembler code only.
#
# make filename.i = Create a preprocessed source file for use in submitting
#   bug reports to the GCC project.
#
# To rebuild project do "make clean" then "make all".
#


# MCU name
MCU = atmega8


# Processor frequency.
# This will define a symbol, F_CPU, in all source code files equal to
the
# processor frequency. You can then use this symbol in your source code
to
# calculate timings. Do NOT tack on a 'UL' at the end, this will be done
# automatically to create a 32-bit value in your source code.
F_CPU = 100


# Output format. (can be srec, ihex, binary)
FORMAT = ihex


# Target file name (without extension).
TARGET = MIXER-72x75-0920


# List C source files here. (C dependencies are automatically generated.)
SRC = $(TARGET).c


# List Assembler source files here.
# Make them always end in a capital .S.  Files ending in a lowercase .s
# will not be considered source files but generated files (assembler
# output from the compiler), and will be deleted upon "make clean"!
# Even though the DOS/Win* filesystem matches both .s and .S the same,
# it will preserve the spelling of the filenames, and gcc itself does
# care about how the name is spelled on its command-line.
ASRC =


# Optimization level, can be [0, 1, 2, 3, s].
# 0 = turn off optimization. s = optimize for size.
# (Note: 3 is not always the best optimization level. See avr-libc FAQ.)
OPT = s


# Debugging format.
# Native formats for AVR-GCC's -g are dwarf-2 [default] or stabs.
# AVR Studio 4.10 requires dwarf-2.
# AVR [Extended] COFF format requires stabs, plus an avr-objcopy run.
DEBUG = dwarf-2


# List any extra directories to look for include files here.
# Each directory must be seperated by a space.
# Use forward slashes for directory separators.
# For a directory that has spaces, enclose it in quotes.
EXTRAINCDIRS = "D:\Google_Drive\AVR-gCC\AVR_inc"


# Compiler flag to set the C Standard level.
# c89   = "ANSI" C
# gnu89 = c89 plus GCC extensions
# c99   = ISO C99 standard (not yet fully implemented)
# gnu99 = c99 plus GCC extensions
CSTANDARD = -std=gnu99


# Place -D or -U options here
CDEFS = -DF_CPU=$(F_CPU)UL


# Place -I options here
CINCS =



# Compiler Options 
#  -g*:  generate debugging information
#  -O*:  optimization level
#  -f...:tuning, see GCC manual and avr-libc documentation
#  -Wall...: warning level
#  -Wa,...:  tell GCC to pass this to the assembler.
#-adhlns...: create assembler listing
CFLAGS = -g$(DEBUG)
CFLAGS += $(CDEFS) $(CINCS)
CFLAGS += -O$(OPT)
CFLAGS += -funsigned-char -funsigned-bitfields -fpack-struct -fshort-enums
CFLAGS += -Wall -Wstrict-prototypes
CFLAGS += -Wa,-adhlns=$(<:.c=.lst)
CFLAGS += $(patsubst %,-I%,$(EXTRAINCDIRS))
CFLAGS += $(CSTANDARD)


# Assembler Options 
#  -Wa,...:   tell GCC to pass this to the assembler.
#  -ahlms:create listing
#  -gstabs:   have the assembler create line number information; note that
# for use in COFF files, additional information about filenames
# and function names needs to be present in the assembler source
# files -- see avr-libc docs [FIXME: not yet described there]
ASFLAGS = -Wa,-adhlns=$(<:.S=.lst),-gstabs


# Library Options 
# Minimalistic printf