Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#30189 - glibc-2.15 bugs: mq_getattr: Function not implemented
Attached to Project:
Arch Linux
Opened by Binghoo Dang (dangbinghoo) - Friday, 08 June 2012, 09:06 GMT
Last edited by Allan McRae (Allan) - Friday, 08 June 2012, 12:57 GMT
Opened by Binghoo Dang (dangbinghoo) - Friday, 08 June 2012, 09:06 GMT
Last edited by Allan McRae (Allan) - Friday, 08 June 2012, 12:57 GMT
|
DetailsDescription:
the new glibc package has bugs with mq_getattr() function. programs using mq_getattr() can be compiled with err, but when reports mq_getattr: Function not implemented in excution. This is an known bug with glibc2.15 upstream. here is the link about this. http://sourceware.org/ml/libc-help/2012-03/msg00024.htm Additional info: * package version(s) [dbh@dbh jz-mqr]$ pacman -Ss ^glibc core/glibc 2.15-10 (base) [Installed] * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Allan McRae (Allan)
Friday, 08 June 2012, 12:57 GMT
Reason for closing: Fixed
Additional comments about closing: glibc-2.15-11 in [testing]
Friday, 08 June 2012, 12:57 GMT
Reason for closing: Fixed
Additional comments about closing: glibc-2.15-11 in [testing]
Comment by Allan McRae (Allan) -
Friday, 08 June 2012, 09:58 GMT
This appears fixed somewhere in glibc git (at least the relevant tests no longer fail...). Glibc git is currently frozen pending the 2.16 release, so I will wait until the release to get this fixed. If the fix is needed earlier, someone should find the commit that fixed it...
Comment by Allan McRae (Allan) -
Friday, 08 June 2012, 10:48 GMT
In fact... it appears an update somewhere else fixed this as a plain rebuild fixes the issue. So I will push one later today.