On 17 August 2015 at 12:57, Gavin Smith wrote:
> On 17 August 2015 at 12:48, Patrice Dumas wrote:
>> Ok. Here is an updated patch with a new simple test for XSParagraph.
>> It doesn't work, it cannot find XSParagraph::new. I tried to show the
>>
On Sat, Aug 15, 2015 at 04:51:23PM +0200, Patrice Dumas wrote:
On Fri, Aug 14, 2015 at 10:12:07PM +, Karl Berry wrote:
I'm not sure what the Makefile.PL is doing there;
As I understood it, it was for the sake of making a texi2any Perl module
that could be uploaded to CPAN and
On 17 August 2015 at 11:33, Patrice Dumas pertu...@free.fr wrote:
I checked and unsurprisingly it didn't work. I tried to build the .xs
file from the tp/Makefile.PL, but I did not succeed, and information in
internet and in the MakeMaker documentation is scarce and nobody seems
to build .xs
On 17 August 2015 at 11:56, Gavin Smith gavinsmith0...@gmail.com wrote:
Is this a possibility to build a standalone module worth more investigation?
I'll have a look at the patch you posted.
So this:
+my $dlname = undef;
+if ($TEXINFO_XS eq 'module') {
+ $dlname = XSParagraph.so;
+ push
On Mon, Aug 17, 2015 at 11:56:51AM +0100, Gavin Smith wrote:
On 17 August 2015 at 11:33, Patrice Dumas pertu...@free.fr wrote:
I think I've seen something like this error before, due to the version
being 6.0dev instead of 6.0.
Ok, this was it.
We don't need to worry about that test failure
On 17 August 2015 at 12:48, Patrice Dumas pertu...@free.fr wrote:
Ok. Here is an updated patch with a new simple test for XSParagraph.
It doesn't work, it cannot find XSParagraph::new. I tried to show the
methods, but none showed up...
The module name is, at the moment, not XSParagraph, but
On Mon, Aug 17, 2015 at 04:25:25PM +0100, Gavin Smith wrote:
On 17 August 2015 at 15:57, Patrice Dumas pertu...@free.fr wrote:
Here is a patch that seems to work. It mimicks Dynaloader bootstrap for
the searching directories too and I fixed the test to be a working
simple test. This
Hello Gavin,
My answers below
I tried that, and it seems that autogen did not fully worked, as what I
got is the following:
[...]
-| lib/Makefile.am:31: error: Libtool library used but 'LIBTOOL' is undefined
-| lib/Makefile.am:31: The usual way to define 'LIBTOOL' is to add
Hello Gavin,
See https://savannah.gnu.org/bugs/index.php?45759#comment1
VBR,
Vincent Belaïche
---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel
antivirus Avast.
http://www.avast.com
Follow-up Comment #1, bug #45759 (project texinfo):
Ok, now I tried it with the activestate perl, but it seems that MSYS
autotools aren't able to manage it correctly, as I got the following:
-| /bin/sh ../libtool --tag=CC --mode=compile
On 16 August 2015 at 13:46, Vincent Belaïche invalid.nore...@gnu.org wrote:
So I edited manually tp/Texinfo/Convert/XSParagraph/lib/Makefile and
tp/Texinfo/Convert/XSParagraph/Makefile to replace
c:NOS_PR~1msysMINGW-~1I686-4~1.0-Pmingw32bingcc.exe by gcc.
That made it go a little further,
Date: Sun, 16 Aug 2015 15:47:20 +0100
From: Gavin Smith gavinsmith0...@gmail.com
Cc: Eli Zaretskii e...@gnu.org, Vincent Belaïche
vincen...@users.sourceforge.net
On 16 August 2015 at 15:29, Eli Zaretskii invalid.nore...@gnu.org wrote:
Follow-up Comment #2, bug #45759 (project texinfo):
Update of bug #45759 (project texinfo):
Open/Closed:Open = Closed
Status:None = Invalid
___
Reply to this item at:
Follow-up Comment #2, bug #45759 (project texinfo):
The problems you are having happen because ActiveState Perl produces file
names with backslashes, which MSYS Bash then treats as escape characters. For
example, see how this:
c:\NOS_PR~1\msys\MINGW-~1\I686-4~1.0-P\mingw32\bin\gcc.exe
became
On 16 August 2015 at 15:47, Gavin Smith gavinsmith0...@gmail.com wrote:
On 16 August 2015 at 15:29, Eli Zaretskii invalid.nore...@gnu.org wrote:
Follow-up Comment #2, bug #45759 (project texinfo):
The problems you are having happen because ActiveState Perl produces file
names with
On 16 August 2015 at 15:29, Eli Zaretskii invalid.nore...@gnu.org wrote:
Follow-up Comment #2, bug #45759 (project texinfo):
The problems you are having happen because ActiveState Perl produces file
names with backslashes, which MSYS Bash then treats as escape characters. For
example, see
On 16 August 2015 at 17:10, Eli Zaretskii e...@gnu.org wrote:
I think we need to double backslashes in the output of perl -V:cc.
Or convert them to forward slashes.
I've done this.
Hello Gavin,
My answers below
On 14 August 2015 at 20:03, Vincent Belaïche
vincen...@users.sourceforge.net wrote:
Can't locate Texinfo/ModulePath.pm in @INC (@INC contains:
c:/Nos_Programmes/msys/lib/perl5/site_perl/5.8/../tp
/usr/lib/perl5/5.8/msys
/usr/lib/perl5/5.8
I tried that, and it seems that autogen did not fully worked, as what I
got is the following:
$ ./autogen.sh
-| Preparing Texinfo development infrastructure:
-| ./tp/maintain/regenerate_file_lists.pl
-| (cd tp ./maintain/regenerate_docstr.sh Makefile.docstr)
-| (cd tp/tests
On Fri, Aug 14, 2015 at 10:12:07PM +, Karl Berry wrote:
I'm not sure what the Makefile.PL is doing there;
As I understood it, it was for the sake of making a texi2any Perl module
that could be uploaded to CPAN and installed in the normal CPAN way. (I
don't believe that has actually
URL:
http://savannah.gnu.org/bugs/?45759
Summary: Can't find Texinfo::ModulePath
Project: texinfo - GNU documentation system
Submitted by: vincentb1
Submitted on: ven. 14 août 2015 11:26:28 GMT
Category: makeinfo
On 14 August 2015 at 20:03, Vincent Belaïche
vincen...@users.sourceforge.net wrote:
Can't locate Texinfo/ModulePath.pm in @INC (@INC contains:
c:/Nos_Programmes/msys/lib/perl5/site_perl/5.8/../tp /usr/lib/perl5/5.8/msys
/usr/lib/perl5/5.8 /usr/lib/perl5/site_perl/5.8/msys
I'm not sure what the Makefile.PL is doing there;
As I understood it, it was for the sake of making a texi2any Perl module
that could be uploaded to CPAN and installed in the normal CPAN way. (I
don't believe that has actually happened yet, but that was the theory.)
On 14 August 2015 at 12:26, Vincent Belaïche invalid.nore...@gnu.org wrote:
Details:
I just did an svn update of the texi2any tool because I could not compile
texinfo documents with @U{...} macros.
Now I get the following error:
Can't locate Texinfo/ModulePath.pm in @INC (@INC contains:
24 matches
Mail list logo