Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Julien Olivain <ju.o@free.fr>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/gdb: gdbserver does not need zlib
Date: Mon, 25 Sep 2023 07:33:24 +0200	[thread overview]
Message-ID: <87o7hqes0r.fsf@48ers.dk> (raw)
In-Reply-To: <20230917152303.1300577-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Sun, 17 Sep 2023 17:23:03 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > Since 3341ceb1e585 (package/gdb: zlib is mandatory, not optional), zlib
 > has become a mandatory dependencies of the gdb package.

 > However, zlib is only needed for the debugger, gdb itself, while the
 > server, gdbserver, does not use it.

 > This means that, when building an SDK to be later reused as an external
 > toolchain, the zlib headers and libraries are present in the sysroot of
 > the toolchain, tainting the toolchain and making it unsuitable to be
 > reused.

 > As Julien noticed, for example, tcl will try and link with zlib if
 > available, and at build time it is. But at runtime, it is not, and thus
 > tclsh fails to run; see 7af8dee3a8a0 (package/tcl: add mandatory
 > dependency to zlib)

 > When we only need to build gdbserver, we still need to configure and
 > build the whole gdb distribution, which means we call the top-level
 > configure script; that script has no option to disable the detection
 > of zlib: it wants to either use a system one, or it will build the
 > bundled one.

 > So, when we onlyt build gdbserver, we tell configure to not use a system
 > zlib, which triggers a build of the bundled one, which we do not use...

 > Reported-by: Julien Olivain <ju.o@free.fr>
 > Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
 > Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
 > Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Committed to 2023.02.x, 2023.05.x and 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-09-25  5:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 15:23 [Buildroot] [PATCH] package/gdb: gdbserver does not need zlib Yann E. MORIN
2023-09-17 19:32 ` Arnout Vandecappelle via buildroot
2023-09-17 19:41   ` Yann E. MORIN
2023-09-25  5:33 ` Peter Korsgaard [this message]

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=87o7hqes0r.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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