| Summary: | media-sound/alsa-driver-1.0.14_rc3: fails to install, some patches cannot be applied with non-C locale? | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alexander Skwar <askwar> |
| Component: | Current packages | Assignee: | Gentoo ALSA team [DISABLED] <alsa-bugs> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2006.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | media-sound:alsa-driver-1.0.14_rc3:20070326-083514.log | ||
|
Description
Alexander Skwar
2007-03-26 08:39:19 UTC
Created attachment 114462 [details]
media-sound:alsa-driver-1.0.14_rc3:20070326-083514.log
(In reply to comment #1) > Created an attachment (id=114462) [edit] > media-sound:alsa-driver-1.0.14_rc3:20070326-083514.log Looking through the build log, I found some german messages, as I've got my locale set like so: laskwar@winnb000488 ~ $ locale LANG=de_CH.UTF-8 LC_CTYPE="de_CH.UTF-8" LC_NUMERIC="de_CH.UTF-8" LC_TIME="de_CH.UTF-8" LC_COLLATE="de_CH.UTF-8" LC_MONETARY="de_CH.UTF-8" LC_MESSAGES="de_CH.UTF-8" LC_PAPER="de_CH.UTF-8" LC_NAME="de_CH.UTF-8" LC_ADDRESS="de_CH.UTF-8" LC_TELEPHONE="de_CH.UTF-8" LC_MEASUREMENT="de_CH.UTF-8" LC_IDENTIFICATION="de_CH.UTF-8" LC_ALL= When I set LC_ALL=C, I can build the stuff just fine. That's IMO no good :( I do not know, if it matters or not: I'm using a suspend2 kernel. Uhm. Strange. I'm now able to build alsa driver even with LC_ALL=de_CH.UTF-8. Strange. But the "3 out of 5 hunks FAILED -- saving rejects to file mpu401.c.rej" is still there. First you say it does not build, then you say it does build... If you have a reproducable build failure, please let me reopen and attach the output of: emerge alsa-driver &> alsa-driver.buildlog The build log that you have attached is unfortunately incomplete. (In reply to comment #3) > First you say it does not build, then you say it does build... Yep. Confusing, isn't it? How can something like this happen? > If you have a reproducable build failure, please let me reopen and attach the > output of: > emerge alsa-driver &> alsa-driver.buildlog So the file which emerge creates itself is no good? I'll see if it still fails to compile. But anyway, the main reason I'm replying now is this: > The build log that you have attached is unfortunately incomplete. What do you mean with that? The attached file starts with " [32;01m*[0m Determining the location of the kernel source code" and ends with "!!! A complete build log is located at '/Gentoo/Portage/logs/media-sound:alsa-driver-1.0.14_rc3:20070326-083514.log'.". This is the file I attached and it contains a complete build log. Or what's missing? > Yep. Confusing, isn't it? How can something like this happen? Unknown. But unless an ebuild fails in a consistent way that I can reproduce on my own system, it is not a bug that I can fix. Sorry. However, I will be bumping the alsa-driver ebuild to 1.0.14 final soon, and in doing so the problem (if any exists after all) may get fixed in the process. So if you can not make this fail again, please wait for the new ebuild instead. > This is the file I attached and it contains a complete build log. Or what's > missing? Nothing is missing, I just needed to fully wake up first. I was looking at the error-only log in your bugzilla comment while you did attach a full usable buildlog. My apologies. |
