Andrew Suffield <[EMAIL PROTECTED]> writes:
> On Mon, Jul 28, 2003 at 05:33:43PM -0500, Raja R Harinath wrote:
>> Andrew Suffield <[EMAIL PROTECTED]> writes:
>>
>> > autoreconf has a habit of doing silly things like running autopoint,
>> > which then cheerfully adds a bunch of gunk to the source
On Mon, Jul 28, 2003 at 05:33:43PM -0500, Raja R Harinath wrote:
> Hi,
>
> Andrew Suffield <[EMAIL PROTECTED]> writes:
>
> > autoreconf has a habit of doing silly things like running autopoint,
> > which then cheerfully adds a bunch of gunk to the source tree which
> > you didn't want. I've never
Hi,
Andrew Suffield <[EMAIL PROTECTED]> writes:
> On Mon, Jul 28, 2003 at 11:39:48PM +0200, Alexandre Duret-Lutz wrote:
>> >>> "Andrew" == Andrew Suffield <[EMAIL PROTECTED]> writes:
>>
>> [...]
>>
>
>>
>> This whole script (including its last part) can be replaced by
>>
>> autoreconf -im
On Mon, Jul 28, 2003 at 11:39:48PM +0200, Alexandre Duret-Lutz wrote:
> >>> "Andrew" == Andrew Suffield <[EMAIL PROTECTED]> writes:
>
> [...]
>
>
> This whole script (including its last part) can be replaced by
>
> autoreconf -im
>
> (I'd use -vfim, though.)
autoreconf has a habit of doing
>>> "Derek" == Derek Robert Price <[EMAIL PROTECTED]> writes:
Derek> Bjarke Freund-Hansen wrote:
>> I'm new at developing on POSIX systems, so I have a few questions (as
>> the subject might indicate ;))
>>
>> Should I include aclocal.m4 in MAINTAINERCLEANFILES, and regenerate it
>> every t
>>> "Andrew" == Andrew Suffield <[EMAIL PROTECTED]> writes:
[...]
Andrew> #!/usr/bin/env bash
Andrew> # For the lazy people, this does all the auto* stuff needed before
Andrew> # ./configure && make will work
Andrew> # (This is a maintainer script; it should never have to be run on
Andrew> #
On Mon, Jul 28, 2003 at 11:02:58PM +0200, Simon Richter wrote:
> Usually I use an autogen.sh like this, works on most systems:
>
> #! /bin/sh -ex
> aclocal-1.7 -I m4 || aclocal-1.6 -I m4 || aclocal -I m4
> autoheader
> automake-1.7 -a || automake-1.6 -a || automake -a
> autoconf
Here's what I use
Hi,
> Should I include aclocal.m4 in MAINTAINERCLEANFILES, and regenerate it
> every time i regenerate the built files? (runs autogen.sh)
Usually I don't care about that file. It will be regenerated every time
someone calls aclocal, so there is no need to clean it out.
> Is it advisable to keep
Bjarke Freund-Hansen wrote:
I'm new at developing on POSIX systems, so I have a few questions (as
the subject might indicate ;))
Should I include aclocal.m4 in MAINTAINERCLEANFILES, and regenerate it
every time i regenerate the built files? (runs autogen.sh)
It depends whether you want to expect e
I'm new at developing on POSIX systems, so I have a few questions (as
the subject might indicate ;))
Should I include aclocal.m4 in MAINTAINERCLEANFILES, and regenerate it
every time i regenerate the built files? (runs autogen.sh)
Is it advisable to keep the generated configure and friends on the
Alexandre Duret-Lutz wrote:
> On Mon, Jul 28, 2003 at 01:09:21PM +0200, Markus Werle wrote:
> > Hi!
> >
> > Though I appreciate the automatic dependency tracking mechanism,
> > I sometimes encounter problems with this approach using Intel's C++
> > compiler. For reasons I do not understand prefixe
On Mon, Jul 28, 2003 at 01:09:21PM +0200, Markus Werle wrote:
> Hi!
>
> Though I appreciate the automatic dependency tracking mechanism,
> I sometimes encounter problems with this approach using Intel's C++
> compiler. For reasons I do not understand prefixed objects get rebuilt,
> so either depcom
Hi!
Though I appreciate the automatic dependency tracking mechanism,
I sometimes encounter problems with this approach using Intel's C++
compiler. For reasons I do not understand prefixed objects get rebuilt,
so either depcomp cannot properly deal with Intel's Compiler (which is
handled as if it w
13 matches
Mail list logo
