See Linux::NFS::BigDir. Is that the module you're working on?
Yes, I'm the author of Linux::NFS::BigDir.
How often in the past 20 years has that number you're fetching from the header changed? It should be easy to lookup
If I could rely on h2ph, yes, but I can't. Linux distributions have a variation of locations there they think it the best way to keep C header files. On the other hand, they don't distribute broken C libraries, so it is safe to assume I can use it to get the constant.
Instead of generating a throwaway module so you can inline a constant, you should be generate a data file, using the "official" way for data files File::ShareDir / File::ShareDir::Install
That will probably give me a maintenance headache: we just need a new processor coming up or anything else that justify changing that constant.
In reply to Re^4: How to properly use ExtUtils::MakeMaker PL_FILES attribute?
by glasswalk3r
in thread How to properly use ExtUtils::MakeMaker PL_FILES attribute?
by glasswalk3r
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |