Missing ELF File

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi everyone,

 

This is not a problem statement. Recently, ELF files were not generated and I have searched a lot. At the end, I figured out that the problem is that I have used non-english characters for the .c and .h files, therefore ELF Files were not generated.

 

I have used 'ı' character which is non-english for both .c and .h files 

 

Therefore, the problem may be not as complicated as you think

 

Best regards,

Ramazan Yaman
Electronics Design Engineer

Last Edited: Fri. Oct 11, 2019 - 05:30 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ah - this old chestnut again:

 

https://www.avrfreaks.net/commen...

 

 

monogoly wrote:
the problem

What problem?

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:
What problem?
I think OP was posting this as informational - to let other users know that if their code builds with errors one possible thing to look at is the use of Unicode characters.

 

Of course "missing ELF" is a bit vague. If you did use a character that the compiler couldn't handle you'd kind of hope it might tell you in a bit more detail!

 

Actually if it is ELF files then it presumably means GCC and yet if I build this in avr-gcc:

 

#include <avr/io.h>

char c = 'ı';

int main(void)
{
	while(1);
}

it happily builds an ELF file without error or warning ?!? (it sets 'c' to 63):

.global	c
	.section	.data.c,"aw",@progbits
	.type	c, @object
	.size	c, 1
c:
	.byte	63

(that is the ASCII code for '?' in fact)

Last Edited: Wed. Oct 9, 2019 - 08:47 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
Of course "missing ELF" is a bit vague.

As the linked thread shows, a common symptom is, "recipe for target <file>.o failed"

 

if I build this in avr-gcc ... it happily builds an ELF file without error or warning ?!?

I think OP was talking about having the weird characters in the file names ?

Hence the link

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:

I think OP was posting this as informational - to let other users know that if their code builds with errors one possible thing to look at is the use of Unicode characters.

 

 

from what I read it is more specific as in using those characters in the actual file name and not inside a file.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:
I think OP was talking about having the weird characters in the file names ?

 

he meant special characters in the file name i suppose. but, awneil, a little bit of patience would always help.

Last Edited: Thu. Oct 10, 2019 - 08:21 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meslomp wrote:
in using those characters in the actual file name and not inside a file.
Yup, that's the bit I didn't understand. The issue he's talking about is clearly about having non ASCII characters in the filenames.

 

I *think* it's possible that quoting the names may fix things but I'm too lazy to test that theory ;-)