Dimitrios Apostolou writes:
> By the way, it seems I'm missing an important piece of the puzzle
> regarding how automake operates. Can someone explain the following?
>
> ?LZIP?DIST_TARGETS += dist-lzip
> ?XZ?DIST_TARGETS += dist-xz
> ?SHAR?DIST_TARGETS += dist-shar
> ?BZIP2?DIST_TARGETS += di
Yann Dirson writes:
> It is not uncommon for software packages to build tools to be executed
> at build time, to generate data files or more input files to compile.
>
> ...
>
> For the second point, it would seem a good idea at some point to
> support a "native_" prefix, so setting eg. "native_PRO
Stefano Lattarini writes:
> So I ask: do you think it would be worthwhile to curb the quantity
> of patches posted here, by posting only the patches judged worth
> of "general interest"? Or, if that sounds overly "harsh", what
> should I/we do to ensure important changes have more visibility?
I
Kerrick Staley writes:
> Really, I'd just like to get gobject-introspection to compile on Arch Linux.
> The problem is that gobject-introspection's configure.ac has the line
>
> AM_PATH_PYTHON([2.5])
>
> but gobject-introspection can't actually work with Python 3 or higher (the
> default on Arch)
Kerrick Staley writes:
> Usually, when AM_PATH_PYTHON is invoked with an argument of the form
> 2.X, it means that only a Python 2 interpreter should be used, and not
> a Python 3 interpreter. However, the "python" command invokes a Python
> 3 interpreter on some systems (see [1]), so if we try "p
On Fri, Sep 21, 2012 at 12:53 AM, Stefano Lattarini
wrote:
> Another ping. Automake 1.13 will need to know the interface of this
> new Autoconf feature in order to integrate with it correctly, and start
> deprecating ACLOCAL_AMFLAGS (in documentation only until Autoconf 2.70
> is out; after that,
On Mon, Jul 23, 2012 at 10:16 PM, Stefano Lattarini
wrote:
> On 07/23/2012 01:26 PM, Jack Kelly wrote:
>> I think the way to do this would be as an improvement to make batch
>> mode more palatable in general. I think an environment variable or a
>> change to default b
Overall, I think the correct action is to set aside this silent-rules
wild-goose-chase.
On Mon, Jul 23, 2012 at 7:26 PM, Stefano Lattarini
wrote:
> On 07/23/2012 10:29 AM, Jack Kelly wrote:
>> On Tue, Jul 17, 2012 at 7:04 PM, Stefano Lattarini
>> wrote:
>>> Maybe we c
On Tue, Jul 17, 2012 at 7:04 PM, Stefano Lattarini
wrote:
> Maybe we could try to write to the Emacs list for help at this point...
I wrote the emacs list, and they pointed me to the NOMESSAGE argument
for (load). Unfortunately the rabbit hole goes deeper...
Emacs defines a variable, site-run-fi
On Sun, Jul 15, 2012 at 6:03 PM, Stefano Lattarini
wrote:
> At least we should find a way to silence all messages that are not
> real warnings or errors... Otherwise, adding silent rules support
> would just be pointless.
I have been asking about this on SO, and there has been a little
progress
Hi automakers,
I noticed that the --batch argument to emacs implies -q, so I patched
out -q. Patch attached, which passes all lisp tests on my machine.
Apply to experimental/elisp-work.
-- Jack
0001-elisp-batch-implies-q-remove-q.patch
Description: Binary data
On Sun, Jul 15, 2012 at 7:33 AM, Stefano Lattarini
wrote:
> On 07/14/2012 02:18 PM, Jack Kelly wrote:
>> I had a crack at refactoring the elisp compilation, getting rid of
>> elisp-comp and compiling files via a suffix rule. Patch is attached.
>>
>> I am not submit
On Sun, Jul 15, 2012 at 7:51 AM, Stefano Lattarini
wrote:
> * lib/am/lisp.am (.el.elc): ... here: we don't chdir around anyway,
> nor move or copy around our source '.el' files. Update comments,
> and re-wrap them while we are at it.
>
> Signed-off-by: Stefano Lattarini
> ---
> lib/am/lisp.am |
Hi automakers,
I had a crack at refactoring the elisp compilation, getting rid of
elisp-comp and compiling files via a suffix rule. Patch is attached.
I am not submitting this for inclusion yet, I want to generate some
discussion first. I have the following concerns:
1. I would like to add silen
On Fri, Jul 13, 2012 at 7:52 PM, Akim Demaille wrote:
> Le 12 juil. 2012 à 17:51, Stefano Lattarini a écrit :
>> Also, taking a step back, we might ask: do we actually need continuing to
>> support DOS? We see that doing so might (as in this case) add an extra
>> burden on the developers, for no
On Fri, Jul 6, 2012 at 7:57 AM, Stefano Lattarini
wrote:
> Usually I'd agree, and in fact I had done as you're suggesting in a
> previous attempt; but that caused the test 'lisp3.sh' to fail :-/
> With the patch I've posted, the testsuite remains clean at least.
>
> So I say we commit my patch: al
On Fri, Apr 27, 2012 at 10:05 PM, Eric Blake wrote:
> On 04/27/2012 03:18 AM, Stefano Lattarini wrote:
>> On 04/27/2012 05:30 AM, Peter Johansson wrote:
>> +++ b/aclocal.in
>> @@ -840,9 +840,8 @@ $output";
>> # name in the header.
>> $output = "# generated automatically by aclocal $VERSION -
On Tue, Feb 1, 2011 at 7:31 AM, Stefano Lattarini
wrote:
> On Monday 31 January 2011, Jack Kelly wrote:
>> I've noticed that if you put AM_PATH_PYTHON in configure.ac, it
>> doesn't add an entry for PYTHON in ./configure --help. Is PYTHON meant
>> to be a user
Hi Ralf,
On Fri, Sep 25, 2009 at 5:02 AM, Ralf Wildenhues wrote:
> Hi Jack,
>
> * Jack Kelly wrote on Wed, Sep 23, 2009 at 11:30:54AM CEST:
>> On Wed, Sep 23, 2009 at 2:02 PM, Ralf Wildenhues wrote:
>> > Uh, oh, more bikeshed color questions. Let's try to find
it, I'll cook up some
tests and we can try to get this committed soonish.
From 6ba77498485395acc5b3eb91ef346244dc29b03b Mon Sep 17 00:00:00 2001
From: Jack Kelly
Date: Tue, 22 Sep 2009 12:24:04 +1000
Subject: [PATCH] Add silent rules support for texinfo outputs.
* automake.in (define_
On Wed, Sep 23, 2009 at 8:37 AM, Jack Kelly wrote:
> Hi Ralf,
>
> Thanks for the review. I agree with most of your remarks.
>
> On Wed, Sep 23, 2009 at 6:42 AM, Ralf Wildenhues
> wrote:
>> * Jack Kelly wrote on Tue, Sep 22, 2009 at 04:33:27AM CEST:
>>>
Hi Ralf,
Thanks for the review. I agree with most of your remarks.
On Wed, Sep 23, 2009 at 6:42 AM, Ralf Wildenhues wrote:
> * Jack Kelly wrote on Tue, Sep 22, 2009 at 04:33:27AM CEST:
>> + tagvars and verbose vars.
>> + * automake.in (define_verbose_tagvar): increas
>From ae772ea28436cb0c49a423b541d6b51f3e907cc9 Mon Sep 17 00:00:00 2001
From: Jack Kelly
Date: Tue, 22 Sep 2009 12:24:04 +1000
Subject: [PATCH] Add silent rules support for dvips, makeinfo,
makeinfo --html, texi2dvi and texi2pdf.
---
ChangeLog | 16
automake.in
23 matches
Mail list logo