why must you compile C with embeded perl the same way?

Discussion in 'Perl Misc' started by talan, Apr 16, 2007.

  1. talan

    talan Guest

    Hi. In the camel book, and in perlembed, it says: "COMPILE THE
    PROGRAMS IN EXACTLY THE SAME WAY THAT YOUR PERL WAS COMPILED". Why is
    that? Specifically, if you use ActivePerl in Windows, you didn't
    compile perl at all. What sort of errors can come up if this isn't
    heeded? When is it really important? Thanks.
     
    talan, Apr 16, 2007
    #1
    1. Advertising

  2. talan

    Joe Smith Guest

    talan wrote:
    > Hi. In the camel book, and in perlembed, it says: "COMPILE THE
    > PROGRAMS IN EXACTLY THE SAME WAY THAT YOUR PERL WAS COMPILED". Why is that?


    Take a look at the output from 'perl -V'. There are some compiler flags
    that, if they don't match, will prevent you code from properly linking
    with the core code. For instance: -Duse64bitint -Dusethreads -Uusemymalloc.
    And: useperlio=define d_sfio=undef uselargefiles=define usesocks=undef.

    -Joe
     
    Joe Smith, Apr 16, 2007
    #2
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. penguinista

    Embeded perl & memory management

    penguinista, Jun 30, 2004, in forum: Perl
    Replies:
    0
    Views:
    621
    penguinista
    Jun 30, 2004
  2. Mr. SweatyFinger
    Replies:
    2
    Views:
    2,249
    Smokey Grindel
    Dec 2, 2006
  3. NeoGeoSNK
    Replies:
    25
    Views:
    972
    NeoGeoSNK
    Nov 24, 2006
  4. Nagaraj
    Replies:
    1
    Views:
    919
    Lionel B
    Mar 1, 2007
  5. Dave
    Replies:
    9
    Views:
    222
    thrill5
    Feb 21, 2006
Loading...

Share This Page