Florian Weimer wrote:
> And I thought Wine can run 32-bit Windows applications against 64-bit
> system libraries these days? Or at least it's getting there. Then Wine
> wouldn't be a reason to keep 32-bit builds around.
>
> | *** WoW64
> |
> | - The 64-bit Windows-on-Windows (WoW64) architectur
On Fri, Mar 3 2023 at 03:21:33 PM +0100, Florian Weimer
wrote:
Is Valve already maintaining a 32-bit distribution? If not, where
would
their Flatpak get the builds from?
There is already a Steam flatpak based on freedesktop-sdk, which builds
just enough i686 stuff for Steam to work.
A
* Michael Catanzaro:
> If the i686 builds only exist for Steam and Wine, can we say users
> should switch to containerized distributions instead (e.g. flatpak,
> snap, or whatever)?
Is Valve already maintaining a 32-bit distribution? If not, where would
their Flatpak get the builds from?
And I
On Fri, Mar 3, 2023 at 2:34 PM Michael Catanzaro wrote:
>
> On Fri, Mar 3 2023 at 12:03:12 PM +, Daniel P. Berrangé
> wrote:
> > Yes, this whole episode makes me want to kill off i686 builds of
> > everything
> > I maintain, even when its not a leaf package. I only spent time
> > investigatin
On Fri, Mar 3 2023 at 12:03:12 PM +, Daniel P. Berrangé
wrote:
Yes, this whole episode makes me want to kill off i686 builds of
everything
I maintain, even when its not a leaf package. I only spent time
investigating
the root cause in gnutls because I saw valgrind warnings and wanted
to be
On 03/03/2023 13:03, Daniel P. Berrangé wrote:
Yes, this whole episode makes me want to kill off i686 builds of everything
I maintain, even when its not a leaf package.
Me too. It worth the F39 System-Wide proposal: drop all i686 builds that
are not needed by Wine/Steam.
--
Sincerely,
Vita
On Fri, Mar 03, 2023 at 12:56:27PM +0100, Florian Weimer wrote:
> * Daniel P. Berrangé:
>
> > AFAICT, Fedora either keeps 32-bit time_t, or kills i686 for good.
>
> I agree with this position.
>
> For additional details, here is what I wrote in the other thread
> (regarding defaulting time64):
>
* Daniel P. Berrangé:
> AFAICT, Fedora either keeps 32-bit time_t, or kills i686 for good.
I agree with this position.
For additional details, here is what I wrote in the other thread
(regarding defaulting time64):
| That still needs some per-package work (mainly for scripting languages
| using
Daniel P. Berrangé wrote:
> The main reason for i686 continuing to exist at all in Fedora is to
> facilitate running of externally distributed 32-bit apps (for example
> wine/steam related). Those apps are all going to be built with 32-bit
> time_t.
WINE is packaged in Fedora. If Fedora rebuilds e
On Thu, Mar 02, 2023 at 02:35:11PM +0100, Miroslav Lichvar wrote:
> On Thu, Mar 02, 2023 at 11:57:42AM +, Daniel P. Berrangé wrote:
> > If any other Fedora maintainer looks after packages that use GNULIB,
> > then it is quite likely that they also need to add --disable-year2038
> > to their spe
On Thu, Mar 02, 2023 at 02:35:11PM +0100, Miroslav Lichvar wrote:
> On Thu, Mar 02, 2023 at 11:57:42AM +, Daniel P. Berrangé wrote:
> > If any other Fedora maintainer looks after packages that use GNULIB,
> > then it is quite likely that they also need to add --disable-year2038
> > to their spe
On Thu, Mar 02, 2023 at 11:57:42AM +, Daniel P. Berrangé wrote:
> If any other Fedora maintainer looks after packages that use GNULIB,
> then it is quite likely that they also need to add --disable-year2038
> to their specfiles to avoid i686 brokenness when talking to any
> non-glibc libraries
On Thu, Mar 02, 2023 at 11:06:04AM +, Richard W.M. Jones wrote:
> On Mon, Feb 27, 2023 at 06:28:56PM +, Richard W.M. Jones wrote:
> > It seems as if there is some issue with TLS (is gnutls borked on i686?)
>
> Yes as it happens, see the thread here:
>
> https://sourceware.org/pipermail/li
On Mon, Feb 27, 2023 at 06:28:56PM +, Richard W.M. Jones wrote:
> It seems as if there is some issue with TLS (is gnutls borked on i686?)
Yes as it happens, see the thread here:
https://sourceware.org/pipermail/libc-alpha/2023-March/145992.html
Rich.
--
Richard Jones, Virtualization Group,
14 matches
Mail list logo
