From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: ptxdist@pengutronix.de, Bruno Thomsen <bth@kamstrup.com>
Subject: Re: [ptxdist] [PATCH 2/2] php5: move away from staging
Date: Tue, 12 May 2020 11:17:08 +0200 [thread overview]
Message-ID: <CAH+2xPDOmd2DEVZT-0jRUxiGajnM-xio6tSf0o++xBBnwNGM8Q@mail.gmail.com> (raw)
In-Reply-To: <20200507080614.GA1153@pengutronix.de>
Den tor. 7. maj 2020 kl. 10.06 skrev Michael Olbrich <m.olbrich@pengutronix.de>:
> > > - help
> > > - STAGING: remove in ptxdist-2021.05.0
> > > - Old version that need to be updated. Fails to build with gcc >= 9.x on
> > > - on some architectures (AArch64).
> >
> > Forgot to add that it compiles with gcc from the following toolchains:
> >
> > arm-v5te-linux-gnueabi/gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized
> > arm-v7a-linux-gnueabihf/gcc-9.2.1-clang-8.0.1-glibc-2.30-binutils-2.32-kernel-5.0-sanitized
> >
> > I have not tested with an AArch64.
>
> It still fails to build. So I'm not quite sure what I should to with this.
> I just moved this to staging when it broke. But now I checked upstream and
> I noticed, that php5 has been discontinued for more than one year. So I
> think this should remain in staging, but I suppose I could apply the first
> patch, so that at least the last release is available.
Okay sound good. Let's keep it in staging and just close known CVEs
with version bump.
Bruno
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-05-12 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 14:04 [ptxdist] [PATCH 1/2] php5: version bump to 5.6.40 Bruno Thomsen
2020-04-29 14:04 ` [ptxdist] [PATCH 2/2] php5: move away from staging Bruno Thomsen
2020-04-29 14:29 ` Bruno Thomsen
2020-05-07 8:06 ` Michael Olbrich
2020-05-12 9:17 ` Bruno Thomsen [this message]
2020-05-19 12:23 ` [ptxdist] [APPLIED] php5: version bump to 5.6.40 Michael Olbrich
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=CAH+2xPDOmd2DEVZT-0jRUxiGajnM-xio6tSf0o++xBBnwNGM8Q@mail.gmail.com \
--to=bruno.thomsen@gmail.com \
--cc=bth@kamstrup.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