The author of that module is Reini Urban. He has a long standing feud with the Perl 5 Porters (the team that writes Perl).
On Fri, Jan 11, 2019 at 11:05 AM Mike Flannigan <mikef...@att.net> wrote: > > > Thanks. > > My Strawberry install finally failed with > Stopping: 'install' failed for 'B::C'. > > I am running ver 5.26 of Strawberry. > > > > I suspect you mean this Readme file: > > INSTALL > > cpan B::C > > On strawberry I needed > perl Makefile.PL FIXIN="perl -S pl2bat.bat" > > On Windows and AIX for 5.12 and 5.14 you need to patch and rebuild CORE perl: > ramblings/Export-store_cop_label-for-the-perl-compiler.patch > > For 5.14 and 5.15 I recommend also the following patches: > ramblings/revert-B-load-BEGIN.patch (The 5.14.1 version) > ramblings/Carp-wo-B.patch > > We generally discourage the use of perl since 5.16 unhandled and > unacknowledged security problems with the implementation of "unicode" > symbols and packagenames, where they really implemented binary names > for all symbols without any checks and further support of such binary > names. Identifiers are not identifiable anymore. > See the warning at perl Makefile.PL. > 5.20 improved support for binary names for most syscalls, dumpers and > APIs, but TR39 and strict names are still not handled, the problems > are not understood and reactions are generally hostile. > 5.18 made it 20% bigger with the implementation of COW strings. > Most strings cannot be stored statically anymore since then. > The best perl versions for the compiler are 5.14.4, 5.22.1 and cperl, > since these are the most tested versions, where the coretest suite passes. > > > The above is only part of the Readme file. > > > I'm not sure what to make of that. > Especially that part that says: > > 'We generally discourage the use of perl since > 5.16 unhandled and unacknowledged security problems' > > > Mike > > > > On 1/11/2019 9:28 AM, Bruce Ferrell wrote: > > I built it on a Linux box, it blew up so I read the README... that has > instructions for how to do it on Windows > > As noted by another poster, it seems to work in spite of the test blowing up > > On 1/11/19 5:37 AM, Mike Flannigan wrote: > > > I could use some more explanation. > > B::C is a module that you install from CPAN. > I assume I don't put Use B::C at the top of > my perl script, but instead perlcc uses it. > > Is perlcc also a module? > Or is that an executable? > I think I see that it is composed of 5 files: > assemble > cc_harness > disassemble > perlcc.PL > pl2exe.pl > > After installing perlcc, do I just open a command > prompt and type perlcc -o hello.exe hello.pl? > > Does all this work on Windows? My guess is Yes. > > > Mike > > > On 1/11/2019 6:57 AM, Andrew Solomon wrote: > > Just a warning - I'm no expert on this topic, but it was such an interesting > question I decided to find out for myself :-) > > I installed B::C and ran > https://metacpan.org/pod/distribution/B-C/script/perlcc.PL > > It actually does the compilation - as opposed to pp which is just packaging > it - so you don't see the perl code of the source file. > > Does that resolve your question? > > Andrew > > > > On Fri, Jan 11, 2019 at 9:59 AM Uday Vernekar <vernekaru...@gmail.com> wrote: >> >> Hi all, >> >> I have a perl code which I need to covert to binary so that nobody can see >> the code. >> >> we used pp package to make the perl code binary but here the user can see >> the code which gets created in tmp. >> >> Need help if anybody knows kindly reply >> >> With regards >> Uday V G > > > > -- > Andrew Solomon > > Perl Trainer, Geekuni http://geekuni.com/ > and...@geekuni.com // +44 7931 946 062 > > > > -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
