this post was submitted on 21 Jul 2023
939 points (98.7% liked)

linuxmemes

21263 readers
1182 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    939
    It took a lot of work, but I've created the definitive Linux distro flowchart (lemmy.world)
    submitted 1 year ago by atmur@lemmy.world to c/linuxmemes@lemmy.world
    107 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] boonhet@lemm.ee 2 points 1 year ago* (last edited 1 year ago) (1 children)

    Compiling everything with LTO landed me in a situation where a bunch of packages fail to build because apparently having some LTO'd static libraries can cause issues.

    I'm now going to start investigating where exactly the issue is. Trouble is, the package that was giving me errors, depended on a whole lot of static libraries, soooooo.... Good luck to me.

    Being an ultra-madlad, I used to also -ffast-math everything that didn't fail, but because I didn't know about package.env yet, I found it easier to just keep it off rather than turning it off and on again every time I needed to emerge something that failed because of it.

    [–] glibg10b@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

    apparently having some LTO’d static libraries can cause issues

    Yeah, I think I've had that problem once or twice. I think I found the culprits by disabling all build flags for libraries that seemed related, rebuilding them, running emerge @preserved-rebuild and then repeating the process to narrow it down

    dmesg and PFL help with diagnosing crashes due to libraries, but I don't think that would help here

    If it helps, here's my package.env:

    # Build failures
app-emulation/wine-vanilla noflto O3
sys-apps/groff O3
dev-lang/rust noflto
dev-lang/python O3
sys-auth/polkit O3
sys-libs/libomp noflto
sys-libs/compiler-rt noflto
net-libs/nodejs O3
dev-lang/duktape O3
x11-drivers/xf86-video-intel noflto

# Runtime failures
gnome-extra/cjs noflto O3
sys-devel/llvm noflto