Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Can not compile blinky on ubuntu

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c

Research direction

Start with Makefile and user/user_main.c, especially the os_timer_disarm call and the reported compiler output. Then inspect include/espmissingincludes.h and the library line mentioned in the issue. Done means the blinky example compiles on Ubuntu without the unknown os_timer_t or volatile-qualifier errors.

Written by the indexing model from the issue text.

Description

Hello,

I just try to compile small example
make!
Error ->
CC user/user_main.c
user/user_main.c: In function 'user_init':
user/user_main.c:51:5: error: passing argument 1 of 'ets_timer_disarm' discards 'volatile' qualifier from pointer target type [-Werror]
os_timer_disarm(&some_timer);

Googling ... -> Download espmissingincludes.h, mkdir include and add #include "espmissingincludes.h" in user_main.c
Ok run forward

CC user/user_main.c
In file included from user/user_main.c:2:0:
include/espmissingincludes.h:33:24: error: unknown type name 'os_timer_t'
void ets_timer_arm_new(os_timer_t *a, uint32_t b, bool repeat, bool isMstimer);
^
include/espmissingincludes.h:34:23: error: unknown type name 'os_timer_t'
void ets_timer_disarm(os_timer_t *a);

Google again ... -> change lib line in Makefile
LIBS = c gcc hal pp phy net80211 lwip wpa main pwm upgrade ssl crypto

os_timer_t is still unknown type/

Google again ... no result :(

Dominant language
Makefile
Stars
278
Forks
125
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from esp8266/source-code-examples

All issues in esp8266/source-code-examples

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.