mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] flex: Version bump. 2.6.4 -> 2.6.15
Date: Tue, 17 Nov 2026 08:14:32 +0100	[thread overview]
Message-ID: <avv-2Cz6RR7wyFEf@pengutronix.de> (raw)
In-Reply-To: <20261116212822.2097354-1-christian.melki@t2data.com>

On Mon, Nov 16, 2026 at 10:28:22PM +0100, Christian Melki wrote:
> Well. This was a surprise. Seems flex development has picked up again.
> 2.6.4 was in 2017 or something? Idk, but this new flex release schedule
> is like 10 releases in less than a week? AI bonkers?
> This is probably old by the time it's applied judging by the current pace.
> As with all build tools ymmv.

2.6.16 is already out with basically one commit and that looks relevant for
ptxdist... I think I'd like to wait a bit to see what else is coming.

Michael

> https://github.com/westes/flex/releases/tag/v2.6.15
> https://github.com/westes/flex/releases/tag/v2.6.14
> https://github.com/westes/flex/releases/tag/v2.6.13
> https://github.com/westes/flex/releases/tag/v2.6.12
> https://github.com/westes/flex/releases/tag/v2.6.11
> https://github.com/westes/flex/releases/tag/v2.6.10
> https://github.com/westes/flex/releases/tag/v2.6.9
> https://github.com/westes/flex/releases/tag/v2.6.8
> https://github.com/westes/flex/releases/tag/v2.6.7
> https://github.com/westes/flex/releases/tag/v2.6.6
> https://github.com/westes/flex/releases/tag/v2.6.5
> 
> * Patchset removed, was added to upstream
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> ---
>  ...SE_SYSTEM_EXTENSIONS-in-configure.ac.patch | 28 -------------------
>  patches/flex-2.6.4/autogen.sh                 |  4 ---
>  patches/flex-2.6.4/series                     |  4 ---
>  rules/flex.make                               |  4 +--
>  4 files changed, 2 insertions(+), 38 deletions(-)
>  delete mode 100644 patches/flex-2.6.4/0001-build-AC_USE_SYSTEM_EXTENSIONS-in-configure.ac.patch
>  delete mode 100755 patches/flex-2.6.4/autogen.sh
>  delete mode 100644 patches/flex-2.6.4/series
> 
> diff --git a/patches/flex-2.6.4/0001-build-AC_USE_SYSTEM_EXTENSIONS-in-configure.ac.patch b/patches/flex-2.6.4/0001-build-AC_USE_SYSTEM_EXTENSIONS-in-configure.ac.patch
> deleted file mode 100644
> index fe3db5536..000000000
> --- a/patches/flex-2.6.4/0001-build-AC_USE_SYSTEM_EXTENSIONS-in-configure.ac.patch
> +++ /dev/null
> @@ -1,28 +0,0 @@
> -From: Explorer09 <explorer09@gmail.com>
> -Date: Mon, 4 Sep 2017 10:47:33 +0800
> -Subject: [PATCH] build: AC_USE_SYSTEM_EXTENSIONS in configure.ac.
> -
> -This would, e.g. define _GNU_SOURCE in config.h, enabling the
> -reallocarray() prototype in glibc 2.26+ on Linux systems with that
> -version of glibc.
> -
> -Fixes #241.
> ----
> - configure.ac | 2 ++
> - 1 file changed, 2 insertions(+)
> -
> -diff --git a/configure.ac b/configure.ac
> -index 55e774b014be..c879fe1225b1 100644
> ---- a/configure.ac
> -+++ b/configure.ac
> -@@ -25,8 +25,10 @@
> - # autoconf requirements and initialization
> - 
> - AC_INIT([the fast lexical analyser generator],[2.6.4],[flex-help@lists.sourceforge.net],[flex])
> -+AC_PREREQ([2.60])
> - AC_CONFIG_SRCDIR([src/scan.l])
> - AC_CONFIG_AUX_DIR([build-aux])
> -+AC_USE_SYSTEM_EXTENSIONS
> - LT_INIT
> - AM_INIT_AUTOMAKE([1.11.3 -Wno-portability foreign check-news std-options dist-lzip parallel-tests subdir-objects])
> - AC_CONFIG_HEADER([src/config.h])
> diff --git a/patches/flex-2.6.4/autogen.sh b/patches/flex-2.6.4/autogen.sh
> deleted file mode 100755
> index 0280f9ee5..000000000
> --- a/patches/flex-2.6.4/autogen.sh
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -#!/bin/sh
> -
> -autoreconf \
> -	--force
> diff --git a/patches/flex-2.6.4/series b/patches/flex-2.6.4/series
> deleted file mode 100644
> index 72e619f12..000000000
> --- a/patches/flex-2.6.4/series
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -# generated by git-ptx-patches
> -#tag:base --start-number 1
> -0001-build-AC_USE_SYSTEM_EXTENSIONS-in-configure.ac.patch
> -# 140965e37966610be24b28e4f9dec52e  - git-ptx-patches magic
> diff --git a/rules/flex.make b/rules/flex.make
> index 76e0f4c95..c42220af5 100644
> --- a/rules/flex.make
> +++ b/rules/flex.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_FLEX) += flex
>  #
>  # Paths and names
>  #
> -FLEX_VERSION	:= 2.6.4
> -FLEX_SHA256	:= e87aae032bf07c26f85ac0ed3250998c37621d95f8bd748b31f15b33c45ee995
> +FLEX_VERSION	:= 2.6.15
> +FLEX_SHA256	:= ba38801d12d38782e36f2ddd66c118aa9ed3cbed9849194c4e68d9894cd739d9
>  FLEX		:= flex-$(FLEX_VERSION)
>  FLEX_SUFFIX	:= tar.gz
>  FLEX_URL	:= https://github.com/westes/flex/releases/download/v$(FLEX_VERSION)/$(FLEX).$(FLEX_SUFFIX)
> -- 
> 2.43.0
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2026-11-17  7:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 21:28 Christian Melki
2026-11-17  7:14 ` Michael Olbrich [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=avv-2Cz6RR7wyFEf@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    /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