FAQ 3.28 I've read perlembed, perlguts, etc., but I can't embed perl in my C program; what am I doing wrong? - comp.lang.perl.misc

Message from discussion FAQ 3.28 I've read perlembed, perlguts, etc., but I can't embed perl in my C program; what am I doing wrong?

PerlFAQ Server

View profile

More options May 11, 3:03 am

Newsgroups: comp.lang.perl.misc

From: PerlFAQ Server <br...@stonehenge.com>

Date: Sun, 11 May 2008 00:03:01 -0700

Local: Sun, May 11 2008 3:03 am

Subject: FAQ 3.28 I've read perlembed, perlguts, etc., but I can't embed perl in my C program; what am I doing wrong?

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

This is an excerpt from the latest version perlfaq3.pod, which
comes with the standard Perl distribution. These postings aim to
reduce the number of repeated questions as well as allow the community
to review and update the answers. The latest version of the complete
perlfaq is at http://faq.perl.org .

--------------------------------------------------------------------

3.28: I've read perlembed, perlguts, etc., but I can't embed perl in my C program; what am I doing wrong?

Download the ExtUtils::Embed kit from CPAN and run `make test'. If the
tests pass, read the pods again and again and again. If they fail, see
perlbug and send a bug report with the output of "make test
TEST_VERBOSE=1" along with "perl -V".

--------------------------------------------------------------------

The perlfaq-workers, a group of volunteers, maintain the perlfaq. They
are not necessarily experts in every domain where Perl might show up,
so please include as much information as possible and relevant in any
corrections. The perlfaq-workers also don't have access to every
operating system or platform, so please include relevant details for
corrections to examples that do not work on particular platforms.
Working code is greatly appreciated.

If you'd like to help maintain the perlfaq, see the details in
perlfaq.pod.

Reply to author Forward