in reply to Re^6: Weird problems building Scalar-List-Utils-1.18 on Win32+MinGW
in thread Weird problems building Scalar-List-Utils-1.18 on Win32+MinGW
"Perl_report_uninit() is not a public Perl API, so extensions are not allowed to call it. On Linux this cannot be enforced as all internal symbols are being exported anyways, but on Windows (and AIX) you can only call APIs that are marked as 'public' in the embed.fnc file in the core Perl distribution."That is what I suspected what was going on, without knowing for sure or being able to stick any labels on it. You see: I couldn't find a trace of it in perlapi, so I suspected it wasn't official, but then I examined the perl source code for the difference between this symbol and stuff that is official, I just couldn't find any. Well, I seem to have been looking in the wrong place.
Thanks for filling in the blanks.
Quote from the parent, by the same author:
I don't think this is in any way a similar problem to the one with S::L::U-1.18.When I said that, I wasn't talking about the behaviour on ActivePerl, but about the symbol Perl_seed which likely is similar.
I can't find any trace of "seed" in perlapi either. For a core module, that's bad, IMO.
vkon posted the cookbook recipe for how to handle this, so I think that probably about wraps it up for me.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^8: Weird problems building Scalar-List-Utils-1.18 on Win32+MinGW
by syphilis (Archbishop) on Jun 21, 2006 at 11:04 UTC |