The answer from Sep 2017 stated that a parent cannot use it’s own macro library, but it seems that this issue has been fixed.
So, if you have a blueprint A with macro M and a blueprint B inherited from A and you want to use macro M inside of B, you should create a macro library C inherited from A and move the definition of M into C. Now you can call M from both A and B.