| Summary: | Compilation failure of sys-process/at-3.1.13-r1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mira Ressel <aranea> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | ||
| Priority: | Normal | ||
| Version: | autobuilds | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Output of $emerge --info =sys-process/at-3.1.13-r1
Build log of sys-process/at-3.1.13-r1 |
||
|
Description
Mira Ressel
2012-03-13 14:32:30 UTC
Created attachment 305205 [details]
Output of $emerge --info =sys-process/at-3.1.13-r1
Created attachment 305207 [details]
Build log of sys-process/at-3.1.13-r1
*** This bug has been marked as a duplicate of bug 294351 *** Something is very strange here. I already had installed bison before. And now, 1 hour later, I retried the emerge (the 3th time), and now everything worked fine - but since I din't #emerge --sync in the last hour, _nothing has changed_ with this ebuild. I really don't unterstand why it works now, but at least it works... Feel free to reopen this bug if you can still reproduce it with sys-devel/bison being installed. No, as I said, I don't think a mssing bison was the problem here, as is was alreay installed before. I just wondered how the bug could disappear on his own while I didn't make any changes to the system. Surely,the misterious disappereance of a bug is no problem, so I won't reopen. |