On Sat, Aug 28, 2021 at 09:15:33PM +0100, Gavin Smith wrote:
>
> We could revisit this issue now the 6.8 release is past. Does anybody know
> where we could ask people who are likely to be knowledgable about and
> experienced with XS modules?
>
> The question is, "how portable is the output of
> From: Gavin Smith
> Date: Sun, 29 Aug 2021 09:23:26 +0100
> Cc: Jacob Bachmeyer , Bruno Haible ,
> Texinfo
>
> On Sun, Aug 29, 2021 at 7:07 AM Eli Zaretskii wrote:
> > How would one try to establish that? Which output files to look at,
> > and what to consider when looking at them?
>
> It
On Sun, Aug 29, 2021 at 7:07 AM Eli Zaretskii wrote:
> How would one try to establish that? Which output files to look at,
> and what to consider when looking at them?
It is the .c files that xsubpp outputs. I want to know if the writers
of xsubpp intended for these .c files to work on other
> From: Gavin Smith
> Date: Sat, 28 Aug 2021 21:15:33 +0100
> Cc: Bruno Haible , bug-texinfo@gnu.org
>
> The question is, "how portable is the output of xsubpp?"
How would one try to establish that? Which output files to look at,
and what to consider when looking at them?
On Wed, Jun 09, 2021 at 08:21:11PM -0500, Jacob Bachmeyer wrote:
> Gavin Smith wrote:
> > Also, if the *.c
> > file was missing from the release and the user didn't have xsubpp, they
> > would
> > have no way to reproduce it, whereas if the *.c is incompatible and they
> > do have xsubpp, they
Gavin Smith wrote:
Also, if the *.c
file was missing from the release and the user didn't have xsubpp, they would
have no way to reproduce it, whereas if the *.c is incompatible and they
do have xsubpp, they could always delete the *.c file and then regenerate
it.
The Perl kit includes
On Wed, Mar 10, 2021 at 11:35:53PM +0100, Bruno Haible wrote:
>
> When you look into the files MiscXS.c, TestXS.c, XSParagraph.c (search for
> PERL_VERSION in there) you can see that
>
> * The generated C code needs to be dependent on the Perl version,
> * xsubpp has produced code that is
Hi Gavin, Jacob,
> > > > Also the files MiscXS.c, TestXS.c, XSParagraph.c were included in the
> > > > tarball, although "make clean" or "make distclean" deletes them. There
> > > > are two possible ways to fix this:
> > >
> > > I think option B below would be the safer one. We check for xsubpp
Gavin Smith wrote:
On Sat, Feb 27, 2021 at 02:41:57PM +0100, Bruno Haible wrote:
Also the files MiscXS.c, TestXS.c, XSParagraph.c were included in the
tarball, although "make clean" or "make distclean" deletes them. There
are two possible ways to fix this:
I think option B below would
On Sat, Feb 27, 2021 at 02:41:57PM +0100, Bruno Haible wrote:
> > So, the cause is that an autogenerated and platform-dependent 'texindex'
> > script was included in the tarball. Removing it from the tarball will fix
> > the issue.
>
> Another way to find this problem is: After unpacking the
> So, the cause is that an autogenerated and platform-dependent 'texindex'
> script was included in the tarball. Removing it from the tarball will fix
> the issue.
Another way to find this problem is: After unpacking the tarball,
$ ./configure && make && make distclean
should leave the same
11 matches
Mail list logo
