() Assaf Gordon
() Mon, 5 Jun 2017 18:48:24 +
I would like to avoid requiring a new texinfo to build sed
Why?
Personally, i was very happy to move to Texinfo 6.x, primarily
for the performance improvement.
--
Thien-Thi Nguyen ---
(defun res
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 06:48:24PM +, Assaf Gordon wrote:
> Hi,
>
> In gnu sed we recently expanded the manual with unicode
> content (e.g. '@U{FFFD}' commands in the texinfo file).
>
> A user alerted us that this fails with older texinfo (5.2):
> https://lists.gnu.org/archive/html/sed-devel/
Hi,
In gnu sed we recently expanded the manual with unicode
content (e.g. '@U{FFFD}' commands in the texinfo file).
A user alerted us that this fails with older texinfo (5.2):
https://lists.gnu.org/archive/html/sed-devel/2017-06/msg2.html
Checking the logs I see that @U{} was added circa 20
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
