All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/3] package/android-tools: fix b64_pton() issue with GCC >= 14.x
Date: Fri, 06 Dec 2024 23:44:34 +0100	[thread overview]
Message-ID: <87ser04ejx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20241204204806.159596-4-thomas.petazzoni@bootlin.com> (Thomas Petazzoni's message of "Wed, 4 Dec 2024 21:48:02 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > The android-tools code base uses the __b64_pton() function, which
 > isn't provided by all C libraries. So the Debian patch
 > debian/patches/add_adbd.patch adds an implementation of b64_pton(),
 > but doesn't actually use it, nor defines a prototype for it. Our
 > existing patch 0003-Fix-build-issue-with-uclibc.patch switches the
 > code to use the b64_pton() function... but still without providing a
 > prototype, causing the following build failures with GCC >= 14.x:

 > adb_auth_client.c:75:15: error: implicit declaration of function 'b64_pton'

 > To fix this, we rework 0003-Fix-build-issue-with-uclibc.patch into a
 > patch that:

 >  (1) Renames b64_pton() to adb_b64_pton() to make sure it won't clash
 >      with implementations provided by some C libraries, and adjusts
 >      the call sites accordingly.

 >  (2) Adds a prototype definition of adb_b64_pton() in places where
 >      this function is used.

 > Fixes:

 >   http://autobuild.buildroot.net/results/b25b25337c7ad89c33f8bd20b646850bd993ec53ae9/

 > Even though GCC 14.x support was merged in Buildroot in May 2024, this
 > particular b64_pton() only started appearing on July 15 2024, with the
 > first occurence being:

 >   http://autobuild.buildroot.net/results/1cbe87bbe3c56f28444b3aaba1ba1d05f947d36e/

 > Indeed, it's not before July 15 2024 that we merged commit
 > d201f2f5cd0d1e0389430cda78adead37977a6cd ("package/android-tools: add
 > patches to fix build with GCC 14.x"), which fixed other GCC 14.x
 > issues, which were hiding this b64_pton() problem.

 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed to 2024.02.x and 2024.08.x, thanks.

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

  reply	other threads:[~2024-12-06 22:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04 20:47 [Buildroot] [PATCH 0/3] Fix two android-tools build issues Thomas Petazzoni via buildroot
2024-12-04 20:48 ` [Buildroot] [PATCH 1/3] package/android-tools: convert all patches to Git-formatted patches Thomas Petazzoni via buildroot
2024-12-06 22:44   ` Peter Korsgaard
2024-12-04 20:48 ` [Buildroot] [PATCH 2/3] package/android-tools: fix build issue on mips64 and powerpc64 Thomas Petazzoni via buildroot
2024-12-06 22:44   ` Peter Korsgaard
2024-12-04 20:48 ` [Buildroot] [PATCH 3/3] package/android-tools: fix b64_pton() issue with GCC >= 14.x Thomas Petazzoni
2024-12-06 22:44   ` Peter Korsgaard [this message]
2024-12-04 21:48 ` [Buildroot] [PATCH 0/3] Fix two android-tools build issues Arnout Vandecappelle via buildroot
2024-12-04 21:52   ` Thomas Petazzoni

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=87ser04ejx.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --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.