| Summary: | sys-apps/sandbox doesn't compile using clang | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Dante Robinson <danterobinson2000> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
emerge --info config.log |
||
Created attachment 833173 [details]
emerge --info
Please include: !!! Please attach the following file when seeking support: !!! /var/tmp/portage/sys-apps/sandbox-2.29/work/sandbox-2.29-abi_x86_64.amd64/config.log * ERROR: sys-apps/sandbox-2.29::gentoo failed (configure phase): I can't reproduce this yet. If it were that simple, stage builds would fail, so there's something more to this. Created attachment 833179 [details]
config.log
(In reply to Sam James from comment #2) > Please include: > > !!! Please attach the following file when seeking support: > !!! > /var/tmp/portage/sys-apps/sandbox-2.29/work/sandbox-2.29-abi_x86_64.amd64/ > config.log > * ERROR: sys-apps/sandbox-2.29::gentoo failed (configure phase): > > I can't reproduce this yet. If it were that simple, stage builds would fail, > so there's something more to this. I was thinking this as well and assuming you guys were just compiling with gcc it's been like this for awhile I have mitigating it for weeks. Maybe it's something to do with my global use flags? (In reply to Dante Robinson from comment #4) > (In reply to Sam James from comment #2) > > Please include: > > > > !!! Please attach the following file when seeking support: > > !!! > > /var/tmp/portage/sys-apps/sandbox-2.29/work/sandbox-2.29-abi_x86_64.amd64/ > > config.log > > * ERROR: sys-apps/sandbox-2.29::gentoo failed (configure phase): > > > > I can't reproduce this yet. If it were that simple, stage builds would fail, > > so there's something more to this. > > I was thinking this as well and assuming you guys were just compiling with > gcc it's been like this for awhile I have mitigating it for weeks. Maybe > it's something to do with my global use flags? Always try to narrow down what's interesting about your system. In this case, it's mold. *** This bug has been marked as a duplicate of bug 830463 *** (In reply to Sam James from comment #5) > (In reply to Dante Robinson from comment #4) > > (In reply to Sam James from comment #2) > > > Please include: > > > > > > !!! Please attach the following file when seeking support: > > > !!! > > > /var/tmp/portage/sys-apps/sandbox-2.29/work/sandbox-2.29-abi_x86_64.amd64/ > > > config.log > > > * ERROR: sys-apps/sandbox-2.29::gentoo failed (configure phase): > > > > > > I can't reproduce this yet. If it were that simple, stage builds would fail, > > > so there's something more to this. > > > > I was thinking this as well and assuming you guys were just compiling with > > gcc it's been like this for awhile I have mitigating it for weeks. Maybe > > it's something to do with my global use flags? > > Always try to narrow down what's interesting about your system. In this > case, it's mold. > > *** This bug has been marked as a duplicate of bug 830463 *** That's the first thing I remove all the time. Your right it runs without mold I swore would have checked that before using gcc, my bad... |
Created attachment 833171 [details] build.log Throws error saying `checking libc path... configure: error: Unable to determine LIBC PATH ()` setting it to compile with GCC allows sandbox to compile. This was tested on a clang-llvm profile.