public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Andreas Ziegler <br025@umbiko.net>
To: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Cc: buildroot@buildroot.org, thomas.petazzoni@bootlin.com,
	Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH v2] package/icu: fix static linking with icu-uc for musl static toolchains
Date: Thu, 26 Mar 2026 08:13:13 +0000	[thread overview]
Message-ID: <4bf2b1929396571923b5401f1b2fe608@umbiko.net> (raw)
In-Reply-To: <CABvxksxxG=fLhCYZBO3d0q5nuQNntY86_FPsLGpsnoguCT0-Yg@mail.gmail.com>

Hi Shubham,

On 2026-03-26 07:01, Shubham Chakraborty wrote:
> Hi Andreas,
> 
> Romain doesn’t seem to be active, so I’d like your guidance on how to
> proceed.
> 
> For v3, would you prefer that I:
> 
>    1. regenerate a single combined patch (replacing 0003 and 0004) 
> using
>    git format-patch, or
>    2. keep 0003 and update it by editing the existing patch to include 
> my
>    changes?
> 
> Also, in this case, should I keep only my Signed-off-by, or retain 
> Romain’s
> attribution in some form?
> 

What I would do is this: Add a comment below the last Signed-off-by, add 
your Signed-off-by, and then modify the patch itself accordingly.

<example>

Add -lstdc++ in Libs.private of icu-uc.pc.

Fixes:
http://autobuild.buildroot.net/results/210/2107f9dfb39eeb6559fb4271c7af8b39aef521ca/

Signed-off-by: Romain Naour <romain.naour@openwide.fr>
---
This patch currently addresses linking against stdc++ for shared-library 
builds. Add -lstdc++ to the static build flags also, to fix 'undefined 
reference' errors when linking programs like xmlcatalog (libxml2)
with musl static toolchains.

Upstream: Inactive-Upstream [Buildroot specific]
Signed-off-by: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
---
  source/Makefile.in | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff -git icu.orig/source/Makefile.in icu/source/Makefile.in

</example>

> Thanks for your guidance.
> 
> Best regards,
> Shubham

<cut>

Kind regards,
Andreas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-03-26  8:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.37807.1772576641.2009750.buildroot@buildroot.org>
2026-03-04  4:35 ` [Buildroot] [PATCH v2] package/icu: fix static linking with icu-uc for musl static toolchains Andreas Ziegler
2026-03-04  6:54   ` Shubham Chakraborty
2026-03-08 11:44     ` Shubham Chakraborty
2026-03-26  7:01       ` Shubham Chakraborty
2026-03-26  8:13         ` Andreas Ziegler [this message]
2026-03-03 16:28 [Buildroot] [PATCH] " Shubham Chakraborty
2026-03-03 18:21 ` [Buildroot] [PATCH v2] " Shubham Chakraborty

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=4bf2b1929396571923b5401f1b2fe608@umbiko.net \
    --to=br025@umbiko.net \
    --cc=buildroot@buildroot.org \
    --cc=chakrabortyshubham66@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox