From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2016.05: no path to staging for one toolchain
Date: Mon, 17 Jun 2019 19:27:13 +0200 [thread overview]
Message-ID: <20190617172713.GF2216@scaer> (raw)
In-Reply-To: <CAH3pVZN5cJfVmgiFxfNKgLy1YZO3ArpZc3DmRgGCc9Gv=Ya4Kw@mail.gmail.com>
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 prev parent reply other threads:[~2019-06-17 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2019-06-18 9:58 ` Sergey Naumov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190617172713.GF2216@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.