On Wed, Jun 07, 2017 at 03:07:14PM -0400, Ken Brown wrote:
> >So I guess it should be
> >
> >host_is_windows=no
> >case "$host" in
> > *-mingw32 | *-mingw64 | *-msdosdjgpp | *-cygwin ) host_is_windows=yes
> > ;;
> >esac
> >AM_CONDITIONAL([HOST_IS_WINDOWS], [test "x$host_is_windows" = "xyes"])
On 6/7/2017 1:14 PM, Gavin Smith wrote:
On Tue, Jun 06, 2017 at 09:56:37PM -0400, Ken Brown wrote:
I've committed a change to do this. I copied the test from the
top-level configure.ac to see if we are on MS-Windows:
host_is_windows=no
case "$host" in
*-mingw32 | *-mingw64 | *-msdosdjgpp )
On Tue, Jun 06, 2017 at 09:56:37PM -0400, Ken Brown wrote:
> >I've committed a change to do this. I copied the test from the
> >top-level configure.ac to see if we are on MS-Windows:
> >
> >host_is_windows=no
> >case "$host" in
> >*-mingw32 | *-mingw64 | *-msdosdjgpp ) host_is_windows=yes ;;
On 6/6/2017 5:22 PM, Gavin Smith wrote:
On Mon, Jun 05, 2017 at 08:50:48PM +0100, Gavin Smith wrote:
On Mon, Jun 05, 2017 at 12:14:04PM -0700, Li Er wrote:
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,
On Mon, Jun 05, 2017 at 08:50:48PM +0100, Gavin Smith wrote:
> On Mon, Jun 05, 2017 at 12:14:04PM -0700, Li Er wrote:
> > 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
On Mon, Jun 05, 2017 at 12:14:04PM -0700, Li Er wrote:
> 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 pe
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
On Mon, Jun 05, 2017 at 02:32:43AM -0700, Li Er wrote:
> XSParagraph assumes perl is built with a shared libperl library, which
> is not always the case, in fact, static libperl is the default option
> when building perl. And since XSParagraph adds -lperl to its ldflags,
> it will result in a build
XSParagraph assumes perl is built with a shared libperl library, which
is not always the case, in fact, static libperl is the default option
when building perl. And since XSParagraph adds -lperl to its ldflags,
it will result in a build failure because you can not link a shared
object with a static
> Date: Mon, 05 Jun 2017 02:32:43 -0700 (PDT)
> From: Li Er
>
> I don't know why it adds this flag, I don't think it's meaningful when
> building a XS module, the perl interpreter loads libperl itself.
At least on MS-Windows, this flag is needed even if linking against a
shared Perl library.
XSParagraph assumes perl is built with a shared libperl library, which
is not always the case, in fact, static libperl is the default option
when building perl. And since XSParagraph adds -lperl to its ldflags,
it will result in a build failure because you can not link a shared
object with a static
11 matches
Mail list logo