Perl and linux emulation

2004-06-08 Thread Jason Godfrey
Hello.

I have a perl module (Adobe's FDF toolkit) that uses two .so files as part
of it's magic. These files come precompiled for Linux. Not surprisingly, when
I try to do a perl use on the module I get an error like this:

Can't load '/usr/local/lib/perl5/site_perl/5.6.1/FDF.so' for module Acrobat::FDF: 
Shared object libc.so.6 not found at 
/usr/local/lib/perl5/5.6.1/i386-freebsd/DynaLoader.pm line 206.
 at /usr/local/lib/perl5/5.6.1/Acrobat/FDF.pm line 741


Is there a way to use a Linux compiled .so file with the a perl compiled for
FreeBSD? If not, does anyone know of a way to easily install a seperate perl
compiled as a linux binary?

Thanks
- Jason
 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Disk activity leading to hangs

2002-11-03 Thread Jason Godfrey

(CC'ing to freebsd-hackers, since a previous discussion took place there.)

Thanks. I tried pinging the machine after a hang, but no response. 

After a bit of experimentation it seems that the hang (at least on the AMD)
occurs under write activity. (A yes  /tmp/foo hangs it.) It seems to hold up
under read loads.

I'm hoping someone on the lists has either a workaround/fix or could maybe say
I've hit this, but when I switched to a non-maxtor drive things worked.

- Jason

On Sat, Nov 02, 2002 at 10:12:09PM -0800, Jeff Jirsa wrote:
 On Sat, 2 Nov 2002, Jason Godfrey wrote:
 
 
  Basically under heavy disk load (buildworld, large package install, nightly
  script run) the system will hang hard. The two systems have very little in
  common, one is a P2 400 running FreeBSD-Stable from Oct 2, the other (a new
  machine) is a AMD 1600+ running FreeBSD 4.5-Release. The faster machine seems
  to hit the hange much more regularly.
 
  The only thing in common between the two machines I can think of is that they
  both have Maxtor IDE drives on a Ultra-ATA channel. (On the P2 400 I've been
  running in PIO mode, as that _seems_ to reduce the frequency of the hangs.
  On the AMD it seems to make no difference.)
 
 
 I've seen it too, with a 4.5 system with a maxtor drive. Unfortunately,
 I've never been able to track it down to anything certain: I was (and
 still am) leaning towards poor hardware over an OS fault. The only thing
 leading me to believe it's NOT a hardware issue is that the kernel seems
 to be running, although nothing responds: network activity lights flash on
 the NIC and switch, but NOTHING else works (have to powercycle).
 
 I remember someone else pointing out the same problem about a year ago,
 and nobody ever offered any explanation of the problem or even hinted at a
 solution.
 
 The last thread is here (watch the line wrap):
 
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=6504+0+archive/2002/freebsd-hackers/20020512.freebsd-hackers
 
 
 - Jeff

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Disk activity leading to hangs

2002-11-02 Thread Jason Godfrey
Hello.

I am experiencing a hang on two machines that I think may be related. I am
hoping someone on the list may know a solution.

Basically under heavy disk load (buildworld, large package install, nightly
script run) the system will hang hard. The two systems have very little in 
common, one is a P2 400 running FreeBSD-Stable from Oct 2, the other (a new
machine) is a AMD 1600+ running FreeBSD 4.5-Release. The faster machine seems
to hit the hange much more regularly. 

The only thing in common between the two machines I can think of is that they
both have Maxtor IDE drives on a Ultra-ATA channel. (On the P2 400 I've been
running in PIO mode, as that _seems_ to reduce the frequency of the hangs.
On the AMD it seems to make no difference.) 

Does anyone have an idea? It's been an annoyance on my P2, but it is making
the AMD (a freinds computer I am helping setup) almost unusable.) 

Thanks
- Jason

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message