public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: stefan11111 <stefan11111@shitposting.expert>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Python 3.11 USE flags being flipped on
Date: Fri, 29 Dec 2023 13:39:11 +0000	[thread overview]
Message-ID: <a7d2c84e0ef62927cf273951b8c833a1@shitposting.expert> (raw)
In-Reply-To: <ZY4bvRfFjBzTXns9@stitch>

On 2023-12-29 01:07, Michael Orlitzky wrote:
> On 2023-12-28 23:00:36, stefan11111 wrote:
>> Should I at least file bugs about those packages?
>> Surely there is no reason to artificially limit the python version in
>> ::gentoo?
> 
> Yes, especially if the package has a test suite that passes under
> python-3.12. Most python packages are community-maintained and it
> feels a lot safer bumping a package you aren't familiar with if it has
> a passing test suite. But even an "it works" report is helpful.

Ran the tests and filed a bug here:
https://bugs.gentoo.org/920933
Has the bug filing form changed?
I don't remember seeing that template when filing bugs.

I skipped dev-libs/glib because it requires dbus and fails with a linker 
error when building it.

I tried adding -Wl,--unresolved-symbols=ignore-all and
-Wl,--warn-unresolved-symbols to my LDFLAGS,
both of which somehow made the compilation fail earlier.

Without those options, the compilation would fail with a linker error.
With those options the compilation failed much earlier with a compiler 
error.
Can anyone explain why that happened?
-- 
Linux-gentoo-x86_64-Intel-R-_Core-TM-_i5-7400_CPU_@_3.00GHz

COMMON_FLAGS="-O3 -pipe -march=native -ftree-vectorize -ffast-math 
-funswitch-loops -fuse-linker-plugin -flto -fdevirtualize-at-ltrans 
-fno-plt -fno-semantic-interposition -fno-common -falign-functions=32 
-fgraphite-identity -floop-nest-optimize"

USE="-* git verify-sig rsync-verify man alsa X grub ssl ipv6 lto 
libressl olde-gentoo asm native-symlinks threads jit jumbo-build minimal 
strip system-man"

INSTALL_MASK="/etc/systemd /lib/systemd /usr/lib/systemd 
/usr/lib/modules-load.d /usr/lib/tmpfiles.d *tmpfiles* /var/lib/dbus 
/lib/udev /usr/share/icons /usr/share/applications 
/usr/share/gtk-3.0/emoji /usr/lib64/palemoon/gtk2"


      reply	other threads:[~2023-12-29 13:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 22:53 [gentoo-user] Python 3.11 USE flags being flipped on stefan11111
2023-12-14 23:38 ` [gentoo-user] " Nikos Chantziaras
2023-12-15  9:09   ` stefan11111
2023-12-15  9:22     ` Arve Barsnes
2023-12-15 11:00       ` stefan11111
2023-12-25  0:11       ` James Massa
2023-12-16  9:47     ` Martin Vaeth
2023-12-27  1:00       ` stefan11111
2023-12-28 15:21         ` Martin Vaeth
2023-12-28 16:11           ` Arve Barsnes
2023-12-28 17:20             ` Martin Vaeth
2023-12-28 18:38           ` stefan11111
2023-12-28 18:50             ` Michael Orlitzky
2023-12-28 20:23             ` Martin Vaeth
2023-12-28 22:18               ` Martin Vaeth
2023-12-28 23:00               ` stefan11111
2023-12-29  1:07                 ` Michael Orlitzky
2023-12-29 13:39                   ` stefan11111 [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=a7d2c84e0ef62927cf273951b8c833a1@shitposting.expert \
    --to=stefan11111@shitposting.expert \
    --cc=gentoo-user@lists.gentoo.org \
    /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