This is a notty one. The behavour has indeed changed, ENOENT was the
previous return and now we return EINVAL. I do not have a POSIX manual
to hand, but the gist of the restriction is as below:
Empty pathname
In the original Unix, the empty pathname referred to the current
directory. Nowadays POSIX decrees that an empty pathname must not be
resolved successfully. Linux returns ENOENT in this case.
It could be argued that the new behaviour is just as valid. A change is
however unhelpful. Especially as kernel behaviour is exposed in
chroots.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/817187
Title:
change in readlink() errno in 2.6.39 and later kernels causes FTBFS
for packages with older gnulib
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/817187/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
