From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Thomas De Schampheleire <patrickdepinguin@gmail.com>
Cc: Mao Han <han_mao@c-sky.com>, buildroot <buildroot@buildroot.org>,
Qu Xianmiao <xianmiao_qu@c-sky.com>, Guo Ren <ren_guo@c-sky.com>,
Mark Corbin <mark.corbin@embecosm.com>,
linux-csky@vger.kernel.org,
Chen Hongdeng <hongdeng_chen@c-sky.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/toolchain-external: ensure ARCH_LIB_DIR exist
Date: Fri, 10 Jan 2020 12:15:50 +0100 [thread overview]
Message-ID: <20200110121550.36c1aba9@windsurf> (raw)
In-Reply-To: <CAAXf6LUVA4QkSmz8OaSOyqzKaw--eD5r0zAD+zONfyGROv1MZw@mail.gmail.com>
On Fri, 10 Jan 2020 11:57:00 +0100
Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
> Finally, please provide a defconfig that allows to reproduce and test
> this problem.
I agree that we need to have access to the toolchain causing problems,
so that we can understand better what are the issues, and what is the
best solution to solve them.
This would also ideally allow to add a test case in Buildroot for this
toolchain, to make sure it keeps working moving forward.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-10 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 3:57 [PATCH 1/2] package/toolchain-external: ensure ARCH_LIB_DIR exist Mao Han
2020-01-02 3:57 ` [PATCH 2/2] toolchain: Get ld.so name if available Mao Han
2020-01-26 15:31 ` [Buildroot] " Yann E. MORIN
2020-02-05 10:30 ` Thomas De Schampheleire
2020-01-10 10:57 ` [Buildroot] [PATCH 1/2] package/toolchain-external: ensure ARCH_LIB_DIR exist Thomas De Schampheleire
2020-01-10 11:15 ` Thomas Petazzoni [this message]
2020-01-13 3:34 ` Mao Han
2020-01-16 9:36 ` Thomas De Schampheleire
2020-01-17 2:35 ` Mao Han
2020-01-24 15:00 ` Thomas De Schampheleire
2020-01-26 15:34 ` Yann E. MORIN
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=20200110121550.36c1aba9@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=han_mao@c-sky.com \
--cc=hongdeng_chen@c-sky.com \
--cc=linux-csky@vger.kernel.org \
--cc=mark.corbin@embecosm.com \
--cc=patrickdepinguin@gmail.com \
--cc=ren_guo@c-sky.com \
--cc=xianmiao_qu@c-sky.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).