* [Buildroot] Buildroot 2016.05: no path to staging for one toolchain @ 2019-06-17 9:31 Sergey Naumov 2019-06-17 17:27 ` Yann E. MORIN 0 siblings, 1 reply; 3+ messages in thread From: Sergey Naumov @ 2019-06-17 9:31 UTC (permalink / raw) To: buildroot Hello. I've integrated multiple external toolchains into Buildroot so far, but I see the issue I've never seen before: When compiling openssl, zlib.h header can't be found. I checked paths compiler looks for headers, and see the following: *~/git/buildroot-oem/output/build/openssl-1.0.2k/crypto/comp$ LD_LIBRARY_PATH=/home/snaumov/git/buildroot-oem/toolchain/crosstools-mips-gcc-4.6-linux-3.4-uclibc-0.9.32-binutils-2.21.Rel1.2/usr/lib /home/snaumov/git/buildroot-oem/output/host/usr/bin/mips-linux-gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include -fPIC -DOPENSSL_PIC -DZLIB_SHARED -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -ffunction-sections -fdata-sections -fomit-frame-pointer -Wall -c -o c_zlib.o c_zlib.c -E -Wp,-v#include "..." search starts here:#include <...> search starts here: .. ../.. ../modes ../asn1 ../evp ../../include /home/snaumov/git/buildroot-oem/toolchain/rsdk-1.5.6-5281-EB-2.6.30-0.9.30.3-131105/include /home/snaumov/git/buildroot-oem/toolchain/rsdk-1.5.6-5281-EB-2.6.30-0.9.30.3-131105/include/gccEnd of search list.c_zlib.c:25:19: error: zlib.h: No such file or directory* For other toolchains I see also a path to buildroot staging dir. At the same time I see that this path is not provided as an additional -I argument to compiler: *~/git/buildroot-oem/output/build/openssl-1.0.2k/crypto/comp$ LD_LIBRARY_PATH=/home/snaumov/git/buildroot-oem/toolchain/crosstools-mips-gcc-4.6-linux-3.4-uclibc-0.9.32-binutils-2.21.Rel1.2/usr/lib /home/snaumov/git/buildroot-oem/output/host/usr/bin/mips-linux-gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include -fPIC -DOPENSSL_PIC -DZLIB_SHARED -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -ffunction-sections -fdata-sections -fomit-frame-pointer -Wall -c -o c_zlib.o c_zlib.c -E -Wp,-vignoring duplicate directory "/home/snaumov/git/buildroot-oem/toolchain/crosstools-mips-gcc-4.6-linux-3.4-uclibc-0.9.32-binutils-2.21.Rel1.2/usr/bin/../lib/gcc/../../lib/gcc/mips-unknown-linux-uclibc/4.6.2/include"ignoring nonexistent directory "/home/snaumov/git/buildroot-oem/output/host/usr/mips-buildroot-linux-uclibc/sysroot/usr/local/include"ignoring duplicate directory "/home/snaumov/git/buildroot-oem/toolchain/crosstools-mips-gcc-4.6-linux-3.4-uclibc-0.9.32-binutils-2.21.Rel1.2/usr/bin/../lib/gcc/../../lib/gcc/mips-unknown-linux-uclibc/4.6.2/include-fixed"ignoring duplicate directory "/home/snaumov/git/buildroot-oem/toolchain/crosstools-mips-gcc-4.6-linux-3.4-uclibc-0.9.32-binutils-2.21.Rel1.2/usr/bin/../lib/gcc/../../lib/gcc/mips-unknown-linux-uclibc/4.6.2/../../../../mips-unknown-linux-uclibc/include"#include "..." search starts here:#include <...> search starts here: .. ../.. ../modes ../asn1 ../evp ../../include /home/snaumov/git/buildroot-oem/toolchain/crosstools-mips-gcc-4.6-linux-3.4-uclibc-0.9.32-binutils-2.21.Rel1.2/usr/bin/../lib/gcc/mips-unknown-linux-uclibc/4.6.2/include /home/snaumov/git/buildroot-oem/toolchain/crosstools-mips-gcc-4.6-linux-3.4-uclibc-0.9.32-binutils-2.21.Rel1.2/usr/bin/../lib/gcc/mips-unknown-linux-uclibc/4.6.2/include-fixed /home/snaumov/git/buildroot-oem/toolchain/crosstools-mips-gcc-4.6-linux-3.4-uclibc-0.9.32-binutils-2.21.Rel1.2/usr/bin/../lib/gcc/mips-unknown-linux-uclibc/4.6.2/../../../../mips-unknown-linux-uclibc/include /home/snaumov/git/buildroot-oem/output/host/usr/mips-buildroot-linux-uclibc/sysroot/usr/includeEnd of search list.* The highlighted directory is clearly out of toolchain and buildroot-specific. I thought that it could be related to toolchain-wrapper, but I see that in both cases exactly the same options are used to build it and there is no sysroot/usr/include path embedded into the binary. Where should I look at to add path to the staging dir? Thanks in advance, Sergey. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190617/8bac8caa/attachment.html> ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] Buildroot 2016.05: no path to staging for one toolchain 2019-06-17 9:31 [Buildroot] Buildroot 2016.05: no path to staging for one toolchain Sergey Naumov @ 2019-06-17 17:27 ` Yann E. MORIN 2019-06-18 9:58 ` Sergey Naumov 0 siblings, 1 reply; 3+ messages in thread From: Yann E. MORIN @ 2019-06-17 17:27 UTC (permalink / raw) To: buildroot Segey, All, First of all, your title is about Buildroot 2016.05: are you really still usign that version? If so, this is a three-year old version, so don;t expect much support on that old version. On 2019-06-17 12:31 +0300, Sergey Naumov spake thusly: > Hello. > I've integrated multiple external toolchains into Buildroot so far, but I see the issue I've never seen before: > When compiling openssl, zlib.h header can't be found. I checked paths compiler looks for headers, and see the following: > ~/git/buildroot-oem/output/build/openssl-1.0.2k/crypto/comp$ > LD_LIBRARY_PATH=/home/snaumov/git/buildroot-oem/toolchain/crosstools-mips-gcc-4.6-linux-3.4-uclibc-0.9.32-binutils-2.21.Rel1.2/usr/lib Setting LD_LIBRARY_PATH shjould not be needed, especially since it is known to actuall y break some packages, and we've remove use of it a long time ago (evem before 2016.05). > /home/snaumov/git/buildroot-oem/output/host/usr/bin/mips-linux-gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include > ?-fPIC -DOPENSSL_PIC -DZLIB_SHARED -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 ?-Os ?-ffunction-sections -fdata-sections -fomit-frame-pointer -Wall ? > -c -o c_zlib.o c_zlib.c -E -Wp,-v > #include "..." search starts here: > #include <...> search starts here: > ?.. > ?../.. > ?../modes > ?../asn1 > ?../evp > ?../../include > ?/home/snaumov/git/buildroot-oem/toolchain/rsdk-1.5.6-5281-EB-2.6.30-0.9.30.3-131105/include > ?/home/snaumov/git/buildroot-oem/toolchain/rsdk-1.5.6-5281-EB-2.6.30-0.9.30.3-131105/include/gcc So, we have had a report (and a patch) about the RSDK toolchains in the past: https://patchwork.ozlabs.org/patch/947617/ Could you try that and report? It is indeed a very old patch, not yet applied, because the problem could not be reproduced (I think) because the RSDK toolchain is not available publicly (is it?) Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] Buildroot 2016.05: no path to staging for one toolchain 2019-06-17 17:27 ` Yann E. MORIN @ 2019-06-18 9:58 ` Sergey Naumov 0 siblings, 0 replies; 3+ messages in thread From: Sergey Naumov @ 2019-06-18 9:58 UTC (permalink / raw) To: buildroot Hi Yann. Thanks for your response. I've managed to find the root cause and fix it. Unlike other toolchains I experienced problems with, this one correctly reported path to libc.a to find a sysroot, but the problem was that --sysroot option which toolchain-wrapper.c provides, not resulted into new headers search path for this toolchain. I digged into buildroot source code and found out that I can use BR2_TARGET_OPTIMIZATION option to provide additional CFLAGS. BR2_TARGET_OPTIMIZATION="-isystem =/usr/include" resolved the problem. Also I do not know whether there is a problem in recent buildroot, but in 2016.05 attempt to specify alternative "march" to buildroot config always resulted in overriding of provided value with default "mips32" one. I had to make the following little patch to fix it: config BR2_GCC_TARGET_ARCH - string + string "march" Thanks, Sergey. ??, 17 ???. 2019 ?. ? 20:27, Yann E. MORIN <yann.morin.1998@free.fr>: > Segey, All, > > First of all, your title is about Buildroot 2016.05: are you really > still usign that version? If so, this is a three-year old version, so > don;t expect much support on that old version. > > On 2019-06-17 12:31 +0300, Sergey Naumov spake thusly: > > Hello. > > I've integrated multiple external toolchains into Buildroot so far, but > I see the issue I've never seen before: > > When compiling openssl, zlib.h header can't be found. I checked paths > compiler looks for headers, and see the following: > > ~/git/buildroot-oem/output/build/openssl-1.0.2k/crypto/comp$ > > > LD_LIBRARY_PATH=/home/snaumov/git/buildroot-oem/toolchain/crosstools-mips-gcc-4.6-linux-3.4-uclibc-0.9.32-binutils-2.21.Rel1.2/usr/lib > > Setting LD_LIBRARY_PATH shjould not be needed, especially since it is > known to actuall y break some packages, and we've remove use of it a > long time ago (evem before 2016.05). > > > /home/snaumov/git/buildroot-oem/output/host/usr/bin/mips-linux-gcc -I.. > -I../.. -I../modes -I../asn1 -I../evp -I../../include > > -fPIC -DOPENSSL_PIC -DZLIB_SHARED -DZLIB -DOPENSSL_THREADS -D_REENTRANT > -DDSO_DLFCN -DHAVE_DLFCN_H -D_LARGEFILE_SOURCE > > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -ffunction-sections > -fdata-sections -fomit-frame-pointer -Wall > > -c -o c_zlib.o c_zlib.c -E -Wp,-v > > #include "..." search starts here: > > #include <...> search starts here: > > .. > > ../.. > > ../modes > > ../asn1 > > ../evp > > ../../include > > > /home/snaumov/git/buildroot-oem/toolchain/rsdk-1.5.6-5281-EB-2.6.30-0.9.30.3-131105/include > > > /home/snaumov/git/buildroot-oem/toolchain/rsdk-1.5.6-5281-EB-2.6.30-0.9.30.3-131105/include/gcc > > So, we have had a report (and a patch) about the RSDK toolchains in the > past: > https://patchwork.ozlabs.org/patch/947617/ > > Could you try that and report? It is indeed a very old patch, not yet > applied, because the problem could not be reproduced (I think) because > the RSDK toolchain is not available publicly (is it?) > > Regards, > Yann E. MORIN. > > -- > > .-----------------.--------------------.------------------.--------------------. > | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' > conspiracy: | > | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ > | > | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is > no | > | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v > conspiracy. | > > '------------------------------^-------^------------------^--------------------' > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190618/b4b35f3b/attachment.html> ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-06-18 9:58 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2019-06-17 9:31 [Buildroot] Buildroot 2016.05: no path to staging for one toolchain Sergey Naumov 2019-06-17 17:27 ` Yann E. MORIN 2019-06-18 9:58 ` Sergey Naumov
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox