ESP8266 Community Forum

how it can locate the library and linker script?
I compile it and it worked after I export the path
export PATH=/home/lilzz/esp-open-sdk/xtensa-lx106-elf/bin:$PATH

but the makefile doesn't have path to library and linker script. so how does it find them?

lilzz wrote:how it can locate the library and linker script?
I compile it and it worked after I export the path
export PATH=/home/lilzz/esp-open-sdk/xtensa-lx106-elf/bin:$PATH

but the makefile doesn't have path to library and linker script. so how does it find them?

They are in one of the locations searched by default. You can instruct the linker to print where it gets libraries by adding -Wl,-t to the compiler command line.
You'd see something like that:


Here libgcc comes from the compiler installation, other libraries come from the sysroot directory.

jcmvbkbc wrote:Here libgcc comes from the compiler installation, other libraries come from the sysroot directory.

OK, I print out the default library path.
/home/lilzz/esp-open-sdk/xtensa-lx106-elf/xtensa-lx106-elf/sysroot/usr/lib/

but how about the path to linker script?
-Teagle.app.v6.ld where is its default path for linker script?

lilzz wrote:but how about the path to linker script?
-Teagle.app.v6.ld where is its default path for linker script?

The linker searches the script in the directories passed to it with -L options, and the compiler driver passes all its default paths to the linker in that manner. You can see it if you add -v to the compiler command line. In open-esp-sdk it's in the sysroot/usr/lib.