Skip to content

Problem compiling in latest release on Ubuntu: permission denied error #330

Closed
@jerabaul29

Description

@jerabaul29

The Arduino IDE suggested that I update the Artemis boards. I suppose this follows the release you had a couple of days ago.

I accepted, but now getting the following kind of errors:

Detecting libraries used...
/home/jrmet/.arduino15/packages/SparkFun/tools/arm-none-eabi-gcc/8-2018-q4-major/bin/arm-none-eabi-g++ -include /home/jrmet/.arduino15/packages/SparkFun/hardware/apollo3/2.0.4/variants/SFE_ARTEMIS/mbed/mbed_config.h -include /home/jrmet/.arduino15/packages/SparkFun/hardware/apollo3/2.0.4/cores/arduino/sdk/ArduinoSDK.h -iprefix/home/jrmet/.arduino15/packages/SparkFun/hardware/apollo3/2.0.4/cores/ @/home/jrmet/.arduino15/packages/SparkFun/hardware/apollo3/2.0.4/variants/SFE_ARTEMIS/mbed/.cxx-flags -w -x c++ -E -CC -DARDUINO=10813 -DARDUINO_APOLLO3_SFE_ARTEMIS -DARDUINO_ARCH_MBED -DARDUINO_ARCH_APOLLO3 -DMBED_NO_GLOBAL_USING_DIRECTIVE -DCORDIO_ZERO_COPY_HCI -I/home/jrmet/.arduino15/packages/SparkFun/hardware/apollo3/2.0.4/cores/arduino -I/home/jrmet/.arduino15/packages/SparkFun/hardware/apollo3/2.0.4/variants/SFE_ARTEMIS -I/home/jrmet/.arduino15/packages/SparkFun/hardware/apollo3/2.0.4/cores/arduino -I/home/jrmet/.arduino15/packages/SparkFun/hardware/apollo3/2.0.4/cores/arduino/mbed-bridge -I/home/jrmet/.arduino15/packages/SparkFun/hardware/apollo3/2.0.4/cores/arduino/mbed-bridge/core-api @/home/jrmet/.arduino15/packages/SparkFun/hardware/apollo3/2.0.4/variants/SFE_ARTEMIS/mbed/.includes -I/home/jrmet/.arduino15/packages/SparkFun/hardware/apollo3/2.0.4/cores/mbed-os/drivers/ /tmp/arduino_build_445418/sketch/recipe_RTC.ino.cpp -o /dev/null -DARDUINO_LIB_DISCOVERY_PHASE
Alternatives for opening dependency file /dev/null.d: []
<built-in>: fatal error: opening dependency file /dev/null.d: Permission deniedResolveLibrary(opening dependency file /dev/null.d)

compilation terminated.  -> candidates: []

exit status 1
Error compiling for board RedBoard Artemis.

This sounds strange, as /dev/null does exist on my system of course, and I am of course able to write to it:

/dev$ echo "bla" > null

Wonder if this is because the flag makes the code try to open / "acquire" the /dev/null file, rather than just writing to it (?).

Any idea how to fix?

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions