On 30 June 2015 at 23:06, Bob Friesenhahn wrote:
> On Tue, 30 Jun 2015, Gavin Smith wrote:
>>
>>
>> What you say about using a different compiler is worrying, though, and
>> I hadn't thought about it before. So basically when compiling an XS
>> module, you need to use whatever compiler was used to
On Tue, 30 Jun 2015, Gavin Smith wrote:
What you say about using a different compiler is worrying, though, and
I hadn't thought about it before. So basically when compiling an XS
module, you need to use whatever compiler was used to compile perl in
the first place? I think we could retrieve this
On 30 June 2015 at 22:41, Bob Friesenhahn wrote:
>> as well as a heap of other variable definitions copied from the
>> MakeMaker Makefile. Now I have to see how ExtUtils:MakeMaker knew what
>> flags to use to see if I can replicate it.
>
>
> These definitely come from how Perl was originally compi
On Tue, 30 Jun 2015, Krishnan Rajiyah wrote:
However, the problem I had with m4 make was not with perl, it said that
automake-1.14 was missing from the system. This does not make sense since
that would mean that there would be a cycle in the dependency tree.
Most automake projects know how to
On Tue, 30 Jun 2015, Gavin Smith wrote:
as well as a heap of other variable definitions copied from the
MakeMaker Makefile. Now I have to see how ExtUtils:MakeMaker knew what
flags to use to see if I can replicate it.
These definitely come from how Perl was originally compiled and built.
If a
-- Forwarded message -
From: Krishnan Rajiyah
Date: Mon, Jun 29, 2015 at 10:40 AM
Subject: installation of automake, autoconf, m4 error
To: ,
Hello GNU,
I have been trying to install automake, autoconf, and m4 on my
NetBSD-4.0.1-x68k system. As I understand from your website, a
On 30 June 2015 at 14:25, Bob Friesenhahn wrote:
> In addition to behavior issues, a major problem is that the re-link
> capabilities offered by libtool are not available. If one links from the
> Perl module to a shared library in the build tree, then there is the risk of
> continued reference to
On Tue, 30 Jun 2015, Gavin Smith wrote:
Hello all,
I wonder if anyone could give pointers to advice on how to integrate a
Perl XS module with an Automake build system? Over at the Texinfo
project we're starting to replace parts of makeinfo with loadable
native-code modules, for speed.
The prob
Hello all,
I wonder if anyone could give pointers to advice on how to integrate a
Perl XS module with an Automake build system? Over at the Texinfo
project we're starting to replace parts of makeinfo with loadable
native-code modules, for speed.
The problem is that the Makefiles produced by ExtUt
On Tue, 30 Jun 2015, 远猷 wrote:
thanks for your reply!
but why forbidding “include” a sub-makefiles.am with absolute path?
Automake projects are expected to be self-contained and not refer to
anything outside of the package.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.si
於 二，2015-06-30 於 09:37 +0200，Thomas Jahns 提到：
> On 06/29/15 17:31, Alex Vong wrote:
> > Thanks for telling me there is no portable flag for doing so.
> > I am now using AC_SUBST() to set the value of STREAM and append `
> > $(STREAM)>/dev/null' to every make command. If the user configure with
> >
On 06/29/15 17:31, Alex Vong wrote:
Thanks for telling me there is no portable flag for doing so.
I am now using AC_SUBST() to set the value of STREAM and append `
$(STREAM)>/dev/null' to every make command. If the user configure with
--enable-verbose-compiler, then STREAM will be set to 0, other
12 matches
Mail list logo
