All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Sergey Matyukevich <geomatsi@gmail.com>
Cc: buildroot@buildroot.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH] toolchain: follow symlinks in ld.*so.* install helper
Date: Sat, 7 Dec 2024 21:47:32 +0100	[thread overview]
Message-ID: <20241207214732.69709f7f@windsurf> (raw)
In-Reply-To: <20241207203633.598905-1-geomatsi@gmail.com>

Hello Sergey,

On Sat,  7 Dec 2024 23:36:26 +0300
Sergey Matyukevich <geomatsi@gmail.com> wrote:

> Current toolchain install helper fails to setup external toolchains with
> merged-usr sysroot. It does not follow lib symlinks when looking for
> ld.*.so.* files. As a result builds fail with various linker errors.
> Follow symlinks in find tool when installing ld*.so.* linker scripts
> from external toolchain directory to staging and target directories.
> 
> Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>

Thanks for the patch!

I need to get back to my backlog, but I believe I had investigated some
toolchain issue, and came back to the same patch/change as you.

This regression was introduced by commit
92207bc03f2358b28e0fd2cc3a41e40504b5d3d4 ("toolchain: handle toolchains
with multiple ld*.so.* files").

I am wondering how I got to debug this? Are there some autobuilder
issues?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-12-07 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-07 20:36 [Buildroot] [PATCH] toolchain: follow symlinks in ld.*so.* install helper Sergey Matyukevich
2024-12-07 20:47 ` Thomas Petazzoni via buildroot [this message]
2024-12-08 20:06   ` Sergey Matyukevich
2025-01-21 18:31     ` Sergey Matyukevich

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=20241207214732.69709f7f@windsurf \
    --to=buildroot@buildroot.org \
    --cc=geomatsi@gmail.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=romain.naour@gmail.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 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.