From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/tftpd: fix static build
Date: Sun, 18 Jul 2021 21:18:29 +0200 [thread overview]
Message-ID: <20210718211829.6c4dc00b@windsurf> (raw)
In-Reply-To: <20210718190136.GH12203@scaer>
On Sun, 18 Jul 2021 21:01:36 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > However, given that this is an upstream commit that was applied 7
> > years ago, I think it is pretty safe to apply it to LTS.
>
> I was confused, because both commits (on tftpd and uClibc) are about 7
> years old, so I was wondering which you were referring to...
>
> But yes, you were rerferring to the tftpd commit. Which got me wondering
> why we needed to apply a patch that have been applied upstream 7 years
> ago. Why can't we just bump the version rather than backport patches?
>
> Ah, tftpd hasn't had any new release for the past 10 years now, so *are*
> up-to-date...
>
> But then, yes, why can't we just switch to the latest commit in the git
> tree, then, rather than backport the fix? Given that tftpd hasn't seen
> any commit since 2015, we would not take too big a risk...
But besides that, I'm still confused as to why the problem happened
only once in the autobuilders. It does happen with the powerpc/internal
toolchain/static configuration that failed in the autobuilders, but
doesn't fail with the pre-built br-arm-full-static toolchain, which
also uses a statically-linked uClibc...
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-07-18 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 8:43 [Buildroot] [PATCH 1/1] package/tftpd: fix static build Fabrice Fontaine
2021-07-16 21:21 ` Thomas Petazzoni
2021-07-16 21:36 ` Fabrice Fontaine
2021-07-18 19:01 ` Yann E. MORIN
2021-07-18 19:18 ` Thomas Petazzoni [this message]
2021-07-18 20:25 ` 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=20210718211829.6c4dc00b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.