Hi,
Is there a way to instruct automake to ignore the exit status for
info_TEXINFOS variable rule? I need this because, texinfo
documentation is incomplete with many dangling references.
thanks,
--
bvk.chaitanya
On Mon, Apr 19, 2010 at 6:46 PM, BVK Chaitanya wrote:
>
> Is there a way to instruct automake to ignore the exit status for
> info_TEXINFOS variable rule? I need this because, texinfo
> documentation is incomplete with many dangling references.
>
I got this fixed by adding --no-validate flag to
On Wed, Apr 14, 2010 at 9:49 PM, NightStrike wrote:
> On Sat, Apr 10, 2010 at 9:46 PM, NightStrike wrote:
>> On Sat, Apr 10, 2010 at 9:43 PM, NightStrike wrote:
>>> Would it be out of the question to teach automake how to handle a def
>>> file as a source file for a library? On windows platform
Hello Ole, Russ,
* Russ Allbery wrote on Fri, Apr 16, 2010 at 10:27:11PM CEST:
> Ole Tange writes:
> > $ cat src/Makefile.am
> > dist_bin_SCRIPTS = parallel
> > man_MANS = parallel.1
>
> > parallel.1: parallel
> >pod2man --release='$(PACKAGE_VERSION)' --center='$(PACKAGE_NAME)' \
> >
Hello Roberto,
* Roberto Bagnara wrote on Sun, Apr 18, 2010 at 02:33:25PM CEST:
> we are about to release PPL 0.11 and Sebastian Pop (who is working
> on GCC/Graphite) encountered a problem we never met, despite the fact
> that we continuously build the PPL with make -j 7 on a machine with
> 2 CPU
Hello,
* NightStrike wrote on Mon, Apr 19, 2010 at 05:09:04PM CEST:
> >>> Is this possible? Is there anyone willing to do it?
> >>
> >> Addendum: A big benefit for me (other than many other things) is that
> >> it lets automake handle figuring out dependencies. In my example,
> >> libx.a doesn'
* Ralf Wildenhues wrote on Mon, Apr 19, 2010 at 06:55:30PM CEST:
> * Russ Allbery wrote on Fri, Apr 16, 2010 at 10:27:11PM CEST:
> > Ole Tange writes:
> > > $ cat src/Makefile.am
> > > dist_bin_SCRIPTS = parallel
> > > man_MANS = parallel.1
> >
> > > parallel.1: parallel
> > >pod2man --rel
On 04/19/2010 07:08 PM, Ralf Wildenhues wrote:
Generated include headers need to be listed in BUILT_SOURCES so when
building for the first time, they are created early. You know that,
and in most cases, ppl.hh ends up there correctly, but it doesn't when
the Automake conditional BUILD_CXX_INTERF
Hi Ralf,
I've been thinking a lot about the JAVA primary lately. It turns out
that Automake's handling of Java sources is pretty efficient.
Experiments indicate that building ~500 Java source files in a single
command takes about 15 seconds on a 1.8 GHz CPU with 512 MB RAM. That
same set of 5
Ralf Wildenhues writes:
> * Ralf Wildenhues wrote on Mon, Apr 19, 2010 at 06:55:30PM CEST:
>> * Russ Allbery wrote on Fri, Apr 16, 2010 at 10:27:11PM CEST:
parallel.1: parallel
pod2man --release='$(PACKAGE_VERSION)' --center='$(PACKAGE_NAME)' \
--section=1 paralle
* Russ Allbery wrote on Mon, Apr 19, 2010 at 08:39:48PM CEST:
> Ralf Wildenhues writes:
> > * Ralf Wildenhues wrote on Mon, Apr 19, 2010 at 06:55:30PM CEST:
> >> * Russ Allbery wrote on Fri, Apr 16, 2010 at 10:27:11PM CEST:
>
> parallel.1: parallel
> pod2man --release='$(PACKAGE_
Hi John,
* John Calcote wrote on Mon, Apr 19, 2010 at 08:25:22PM CEST:
> Since the current implementation of the JAVA primary is not managing
> individual source/object dependencies (something that's difficult to
> do anyway because of inner and anonymous class definitions), would
> it not be prud
On Mon, Apr 19, 2010 at 8:25 PM, John Calcote wrote:
[...]
> Builds in the Java world generally specify source files found
> within a subtree using a globbing mechanism, with optionally
> specified inclusions and exclusions.
Yes, they do. BTW, does anyone know why?
With some sarcasm someone cou
Ralf Wildenhues writes:
> * Russ Allbery wrote on Mon, Apr 19, 2010 at 08:39:48PM CEST:
>> Ralf Wildenhues writes:
>>> * Ralf Wildenhues wrote on Mon, Apr 19, 2010 at 06:55:30PM CEST:
* Russ Allbery wrote on Fri, Apr 16, 2010 at 10:27:11PM CEST:
>> parallel.1: parallel
>>pod
Hi Steffen,
On 4/19/2010 1:22 PM, Steffen Dettmer wrote:
On Mon, Apr 19, 2010 at 8:25 PM, John Calcote wrote:
[...]
Builds in the Java world generally specify source files found
within a subtree using a globbing mechanism, with optionally
specified inclusions and exclusions.
Yes,
* John Calcote wrote on Mon, Apr 19, 2010 at 09:52:51PM CEST:
> I can certainly see how we may want to stick with the Automake
> "static source file specification" rules for the reasons you point
> out. In this case, it becomes more of an evangelistic documentation
> issue. :) That is, we might be
16 matches
Mail list logo
