After an update with 'emerge --update --deep --newuse world', I just issued 'perl-cleaner --reallyall' as usual. It seems the script is running well except an error message pumped up.
* Locating ebuilds linked against libperl [snip] * Adding to list: dev-perl/Archive-Zip:0 * Adding to list: dev-vcs/git:0 scanelf: mmap on '/lib64/udev/devices/core' of 140737486262272 bytes failed :( * Adding to list: app-text/po4a:0 * Adding to list: perl-core/ExtUtils-ParseXS:0 [snip]
I am not sure if the message harmful yet. Do you have ever experencied some similiar issue during updating perl modules?
it's not harmful, this message hangs years with perl-cleaner. It just shows maximum size of memeory available on 64bit box.