Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: JiangXin <mc.xin@foxmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Romain Naour <romain.naour@gmail.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot]  回复:  [PATCH 1/1] toolchain/helpers.mk: add the processing when LIBPATH is a directory
Date: Mon, 24 Apr 2023 17:48:28 +0200	[thread overview]
Message-ID: <20230424154828.GP2696@scaer> (raw)
In-Reply-To: <tencent_475A705644EC2785AB3F5ED47572AF096207@qq.com>

JiangXin, All,

On 2023-04-24 15:56 +0800, JiangXin spake thusly:
> I build rootfs in docker container based on ubuntu22.04, host arch is x86_64.
> I chose the gcc downloaded by apt to build. 

Ah, we do not support distro toolchains, see the manual, chapter 6.1.2.
External toolchain backend:

    https://buildroot.org/downloads/manual/manual.html#external-toolchain-backend

    We also do not support using the distribution toolchain (i.e. the
    gcc/binutils/C library installed by your distribution) as the
    toolchain to build software for the target. This is because your
    distribution toolchain is not a "pure" toolchain (i.e. only with
    the C/C++ library), so we cannot import it properly into the
    Buildroot build environment.

> After the shell command in helpers.mk is excuted, the following content is output:
> root@824b1b82dfae:~/buildroot-2022.02.11# find /root/buildroot-2022.02.11/output/host/x86_64-buildroot-linux-gnu/sysroot -name
> "ld*.so.*"
> /root/buildroot-2022.02.11/output/host/x86_64-buildroot-linux-gnu/sysroot/etc/ld.so.conf.d
> /root/buildroot-2022.02.11/output/host/x86_64-buildroot-linux-gnu/sysroot/etc/ld.so.cache
> /root/buildroot-2022.02.11/output/host/x86_64-buildroot-linux-gnu/sysroot/etc/ld.so.conf
> /root/buildroot-2022.02.11/output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/ld-linux-x86-64.so.2
> /root/buildroot-2022.02.11/output/host/x86_64-buildroot-linux-gnu/sysroot/lib/ld-linux-x86-64.so.2
> root@824b1b82dfae:~/buildroot-2022.02.11# ls -l
> /root/buildroot-2022.02.11/output/host/x86_64-buildroot-linux-gnu/sysroot/etc/ld.so.conf.d
> total 12
> -rw-r--r-- 1 root root  38 Mar  5  2022 fakeroot-x86_64-linux-gnu.conf
> -rw-r--r-- 1 root root  44 Sep 24  2021 libc.conf
> -rw-r--r-- 1 root root 100 Sep 28  2021 x86_64-linux-gnu.conf
> I added the echo on lines 753-756 of the top-level Makefile, and the build 
> log shows it doesn't get there.

This is weird, because that part should be unconditional. So, it looks
like the build may in fact not be finished successfully. Could you share
the last 50-or so last lines of the log?

> Should the processing of directories be added
> in toolchain/helpers.mk?

As I explained previously, and as confirmed above, support for
ld.so.conf should not be added, and thus the real solution is to
exclude directories in toolchain/helpers.mk line 13:

    find $(STAGING_DIR)/ -name "$${LIBPATTERN}" -not -type d 2>/dev/null

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.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-04-24 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23 15:54 [Buildroot] [PATCH 1/1] toolchain/helpers.mk: add the processing when LIBPATH is a directory MidCheck
2023-04-23 16:40 ` Yann E. MORIN
2023-04-24  7:56   ` [Buildroot] =?gb18030?b?u9i4tKO6ICBbUEFUQ0ggMS8xXSB0b29sY2hhaW4v?= =?gb18030?q?helpers=2Emk=3A_add_the_processing_when_LIBPATH_is_a_directory?= =?gb18030?B?SmlhbmdYaW4=?=
2023-04-24 15:48     ` Yann E. MORIN [this message]
     [not found]       ` <tencent_B90EBB4061EF4F1B15813C6A229F3698F505@qq.com>
2023-04-25 20:03         ` [Buildroot] 回复: 回复: [PATCH 1/1] toolchain/helpers.mk: add the processing when LIBPATH is a directory Arnout Vandecappelle via buildroot

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=20230424154828.GP2696@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=mc.xin@foxmail.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.de_schampheleire@nokia.com \
    --cc=thomas.petazzoni@bootlin.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