Summary: | www-client/firefox-10.0.11 on Alpha - .../work/mozilla-esr10/ipc/chromium/src/base/file_util.cc:228:35: error: 'ftruncate' was not declared in this scope | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Don Wilburn <bodhisattva> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | alpha |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | Alpha | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info for firefox
build log for firefox |
Created attachment 391992 [details]
build log for firefox
Please let me know if it is wrong to attach unsolicited build log attachments to a bug report. Thanks, DW
(In reply to Don Wilburn from comment #1) > Please let me know if it is wrong to attach unsolicited build log > attachments to a bug report. No, that's fine. In fact we welcome and expect build logs. alpha either needs to catch up and stabilze current esr or drop keywords. firefox-10.0 has been eol for over 2 years now. |
Created attachment 391990 [details] emerge --info for firefox This old firefox package is marked stable for alpha, but fails to build on mine. I don't know what's important from the build log. I did try dmesg this time, but there were no messages. I can't blame it on a lack of memory/swap this time. It looks like firefox was marked stable about 2 years ago. I tried current seamonkey first, which failed, so I'm trying to stick with something marked stable. I don't know if it's proper protocol, but I'll make another post so I can attach the build log.