On Sun, Nov 1, 2009 at 6:45 AM, Ralf Wildenhues wrote:
> Since the 1.11 release I have not seen one bug report about
> $AUTOMAKE_JOBS aka. automake running several Perl threads to
> update several Makefile.in files concurrently, for speed.
> If you have more than a couple of Makefile.am files and
Hi Ralf - I figured out my problem. See below; basically, I'm a numbskull.
On Wed, Apr 22, 2009 at 1:09 AM, Ralf Wildenhues wrote:
> Here's a few reasons why this may not have worked as intended:
>
> - config.h wasn't even updated. configure, more precisely
> config.status, updates the header la
I have a project using autoconf + automake + autoheader, and clearly
the results of my builds depends on what is in config.h. Thus, I would
expect that when I run ./configure, everything in the build tree would
be marked as out-of-date and everything would be rebuilt - that is, I
would expect targe
I'm maintaining an autotools-configured project, and I've noticed that
the make install resulting from my build (on x86_64 arch, linux) puts
generated libraries in prefix/lib instead of prefix/lib64 - is there
something I should do differently, or is the the expected behaviour?
Thanks,
Jason
