unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: John Kehayias <john.kehayias@protonmail.com>, 67608-done@debbugs.gnu.org
Subject: bug#67608: qtbase fails to build on i686
Date: Wed, 6 Dec 2023 14:21:24 +0200	[thread overview]
Message-ID: <ZXBnRPFS61aC1Ppe@3900XT> (raw)
In-Reply-To: <871qc2yht9.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]

On Sun, Dec 03, 2023 at 06:42:10PM -0500, Maxim Cournoyer wrote:
> John Kehayias <john.kehayias@protonmail.com> writes:
> 
> > Hi Maxim,
> >
> > On Sun, Dec 03, 2023 at 01:32 PM, Maxim Cournoyer wrote:
> >
> >> Hi,
> >>
> >> After recent mesa/xorg upgrades, qtbase fails to build on i686, per
> >> <https://ci.guix.gnu.org/build/2700964/details>.
> >
> > I saw this when I was working on the mesa-updates branch, but I didn't
> > think it was a new failure. I looked back just now and even going to
> > July or further back I don't see any successful builds of qtbase-6.*
> > on i686-linux. The most recent version has the same failures as this
> > log, pre-mesa-updates. Looked like a previous version of qtbase-6 had
> > a different failure though.
> 
> Indeed.  I wonder why Cuirass flagged the failure as a new one.

Maybe it was mixing up qtbase@5 and qtbase@6 for determining if it had
successfully built before?

> [...]
> 
> > As for the actual cause, I don't have a clue. There was a failure
> > cause by an update on that branch, which I had fixed in
> > aee3c5a894fddf88810f18fa8880b423b078b3fa (from libxkbcommon update).
> >
> > Was there a version of qtbase-6 that builds on i686?
> 
> OK.  I don't seem to find one looking at CI.  We should probably report
> this upstream if it hasn't already been.

I found it broken when I was going through a big rebuild and I believe
it tracked it down to the -DFEATURE_xxx=OFF flags that we've been
carrying since qt-4.  Once I removed them i686 stopped trying to use
128-bit numbers and compiled successfully.  As a comparison, Debian
doesn't use those flags.

I've closed the bug since it now builds, but feel free to re-open it if
we want to revisit removing the flags or anything.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03 18:32 bug#67608: qtbase fails to build on i686 Maxim Cournoyer
2023-12-03 19:19 ` John Kehayias via Bug reports for GNU Guix
2023-12-03 23:42   ` Maxim Cournoyer
2023-12-06 12:21     ` Efraim Flashner [this message]
2023-12-06 22:53       ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZXBnRPFS61aC1Ppe@3900XT \
    --to=efraim@flashner.co.il \
    --cc=67608-done@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=maxim.cournoyer@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).