> > > perl -V shows this is in the INC path:
> > >
> > > /usr/local/lib/perl5/site_perl/5.8.0/i686-linux
> > >
> > > so I think a -A asm/termios.ph would do it.
> >
> > Sounds like a plan. Okay. :)
I just installed the 0.66 release (sorry I didn't get a chance to test it
out sooner) and tried this out with -M asm/termios.ph, but the 'use
SerialPort.pm' still fails. I DO see the file unziped into /tmp, but as a
.pm file. I'm not sure how you work the magic to get those modules found by
the correct name, but I don't think it is working in this case.
I also see you re-implemented the TK widget fix a bit different.
Unfortunatly, this version doesn't work :( If I add back in your original
fix (2nd line here) it works ok:
if ($map{$pfile} =~ /\bTk\b.*\bWidget\.pm/i) {
$content =~ s/if \(defined\(\$name=\$INC\{"\$pkg.pm"\}\)\)/if (0)/;
> Now I've got a different problem when I run the resulting binary on a
> different linux box. I get this message:
>
> [EMAIL PROTECTED] bin]$ /projects/public/a.out
> /projects/public/a.out: /lib/libc.so.6: version `GLIBC_2.3' not found
> (required by /projects/public/a.out)
>
> In fact, I'll get this even with the simplest of script. I tried it on
> both a RH 5.2 and RH 7.2 box. I think the newer libraries I have
> on the RH
> 8.0 box I compiled it on are somehow not compatable? I tried various
> combinations of -l files, but I think this happens right away,
> before the pp
> generated binary can do anything.
I discovered I can run pp binaries I compile on my Red Hat 7.2 box on my Red
Hat 8.0 box, but not the other way around, due to the GLIBC errors above.
> > > > If somebody on Win32 can help testing / porting the shlib support to
> > > > that platform, I'll gladly merge it earlier.
> > >
> > > I can give Win32 a spin also, except I think the latest
> version that PPM
> > > gave me there was 0.63, so the patches wouldn't apply. What is
> > the best way
> > > to check version number?
> >
> > Well if you have MSVC++ (which you will need to compile shlib support
> > anyway) just download the snap and compile it there.
> >
> > If you don't... I'll try putting up a binary for you tomorrow.
>
> Sorry, I don't have any windows C compilers installed here. I'd
> by happy to
> test out your recent updates once you get an updated binary.
When I installed 0.66 on my windows box, I did not get the 'try the
experimental shlib' option, so I wasn't able to test this yet. Trying
the -l option seemed to invoke -log instead.
Bruce
