[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: XSParagraph build failure with static libperl
From: |
Li Er |
Subject: |
Re: XSParagraph build failure with static libperl |
Date: |
Mon, 05 Jun 2017 12:14:04 -0700 (PDT) |
I tried my build with TEXINFO_XS=debug and it states 'XSParagraph.so loaded',
so I think it's working well.
If there's no shared libperl, XS module simply uses the symbols exported
by the perl binary. I also had a look at debian's perl distribution, it's
using shared libperl but the XS modules are not linked against it. I think
it's the default behavior under Linux. I don't know much about Windows,
however.
- XSParagraph build failure with static libperl, rslovers, 2017/06/05
- XSParagraph build failure with static libperl, Li Er, 2017/06/05
- Re: XSParagraph build failure with static libperl, Eli Zaretskii, 2017/06/05
- Re: XSParagraph build failure with static libperl, Gavin Smith, 2017/06/05
- Re: XSParagraph build failure with static libperl,
Li Er <=
- Re: XSParagraph build failure with static libperl, Gavin Smith, 2017/06/05
- Re: XSParagraph build failure with static libperl, Gavin Smith, 2017/06/06
- Re: XSParagraph build failure with static libperl, Ken Brown, 2017/06/06
- Re: XSParagraph build failure with static libperl, Gavin Smith, 2017/06/07
- Re: XSParagraph build failure with static libperl, Ken Brown, 2017/06/07
- Re: XSParagraph build failure with static libperl, Gavin Smith, 2017/06/08