Summary: | a courple of apps won't compile without sandbox | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Lukas Miczka <cpu> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lukas Miczka
2004-05-28 09:26:00 UTC
considering sandbox is in the default FEATURES i doubt that's the problem what is the output of `emerge info` if you dont add that line to make.conf ? why dont you try with less suicidal CFLAGS ? Of course I've tried - with: 1. -march=athlon-xp -O3 -fomit-frame-pointer -pipe 2. -march=athlon-xp -O2 -pipe And my current make.conf #FEATURES="sandbox buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork autoaddcvs" #FEATURES="sandbox ccache distcc autoaddcvs" #FEATURES="distcc" #FEATURES="sandbox" I said when I uncomment sandbox I have no problems if not - cannot emerge abiword and mplayer at this moment what about simply CFLAGS="-pipe" ? also, you didnt answer my other question about `emerge info` So you think that it's something wrong with make.global...? And till this update evertyhing worked fine. I'll chceck this tommorow on diffrent computer and report what I've experienced also try pure -O2 march=athlon-xp I'd venture: tempermental hardware induced by optimizations. "Adding" sandbox will not fix a problem. It's enabled by default on x86 unless you explicitly disable it. You're seeing a phantom bug. You can't simply test building something by changing your cflags. You have to rebuild the entire system with something more sane first, then you can try it. |