Is there some reason that *-local targets aren't always valid when their
parent exists? I wanted to define distclean-hdr-local to remove
options.h-SAVED as well as options.h, but I can't seem to get it to
work.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.o
Hi Patrick,
On Fri, Nov 03, 2000 at 07:45:08PM +0100, Patrick Guio wrote:
> Do you think it could be possible to insert this in the libtool?
> Maybe automake/depcomp has to be modified to be able to use the option -MD
> with the cxx compaq compiler for osf machines?
Does the Compaq C++ support i
Dear all
I have now been able to build c++ library on a alphaev6-dec-osf5.0
with templates using cxx
I had to specify in aclocal.m4 instead of
>old_archive_cmds='$AR $AR_FLAGS $oldlib$oldobjs$old_deplibs'
Note that by giving the option -MD one create a file with dependencies
(same style) calle
> "Derek" == Derek R Price <[EMAIL PROTECTED]> writes:
Derek> Akim Demaille wrote:
>> What's wrong with the `missing' approach?
Derek> I ran automake the first time without the '--add-missing'
Derek> argument so when it told me it wouldn't run because "AUTHORS"
Derek> and "missing" weren't p
> "Derek" == Derek R Price <[EMAIL PROTECTED]> writes:
Derek> What's the 'missing' approach?
When autoconf or automake is not found, the script `missing' is then
used, and touches the products.
~/src/am % ./missing --help nostromo 17:21
./missing [OPTION
Akim Demaille wrote:
> What's wrong with the `missing' approach?
I ran automake the first time without the '--add-missing' argument so
when it told me it wouldn't run because "AUTHORS" and "missing" weren't
present I simply touched the files in expectation of figuring out what
GNU wanted of me l
Akim Demaille wrote:
> What's wrong with the `missing' approach? What version of Automake
> are you using? I'm using CVS Automake for my package, and never found
> such problem.
Oh, Version 1.4. And what's 'CVS Automake' as opposed to automake?
Derek
--
Derek Price CVS
"Lars J. Aas" wrote:
> : And I'm totally against AM_MAINTAINER_MODE :)
>
> I always use it. I want every invokation of autoconf and automake to
> be explicit on my behalf. I even hate it when config.status goes into
> recheck mode.
I'm happy enough with them running automatically when the tool
Paul Berrevoets wrote:
> This should already be taken care of by the macro AM_MAINTAINER_MODE. If you use:
> ./configure --enable-maintainer-mode
> then the autoconf/automake targets are enabled. They should be disabled by default.
Doesn't it make more sense to enable/disable the targets bas
On Fri, Nov 03, 2000 at 04:49:23PM +0100, Akim Demaille wrote:
: > "Derek" == Derek R Price <[EMAIL PROTECTED]> writes:
: Derek> This could be a very useful tool but without this feature I
: Derek> cannot use it in good conscience.
:
: What's wrong with the `missing' approach? What version o
Akim Demaille wrote:
> > "Derek" == Derek R Price <[EMAIL PROTECTED]> writes:
>
> Derek> This could be a very useful tool but without this feature I
> Derek> cannot use it in good conscience.
>
> What's wrong with the `missing' approach? What version of Automake
> are you using? I'm using C
> "Derek" == Derek R Price <[EMAIL PROTECTED]> writes:
Derek> This could be a very useful tool but without this feature I
Derek> cannot use it in good conscience.
What's wrong with the `missing' approach? What version of Automake
are you using? I'm using CVS Automake for my package, and ne
This should already be taken care of by the macro AM_MAINTAINER_MODE. If you use:
./configure --enable-maintainer-mode
then the autoconf/automake targets are enabled. They should be disabled by default.
--
Paul
"Derek R. Price" wrote:
> This same applies to targets using autoconf & autoheade
Dear all
I am not sure if this is to be adressed to libtool or maybe automake
since the problem might come from depcom...
Anyway I am trying to build a c++ library using libtool on a
alphaev6-dec-osf5.0
using cxx.
These set up should allow to archive correctly
# The archiver.
AR="ar"
AR_FLAGS
This same applies to targets using autoconf & autoheader.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
A burp is not an answer.
A burp is not an answer.
A burp is not an answer...
Automake seems to be creating targets by default that make use of
automake whether or not the user has automake installed. Timestamps
seem to get fouled up in distribution often enough that I think this is
very bad from a maintenance viewpoint (more questions to answer) and
very rude to users.
I
Hello,
I have a question regarding automake 1.4/1.4a:
Is it possible to build a single library from source files
that reside in a couple of subdirectories beneath?
Something like this:
dir1/libfoo.a
dir1/dir2/a.c
dir1/dir3/b.c
Regards,
Marc
> "phane" == phane Genaud writes:
phane> Hi, on a Irix 6.5 system, using automake 1.4, autoconf 2.12
Please, consider upgrading at least of 2.13. If the trouble persists,
give a try to CVS Autoconf (See http://sources.redhat.com/autoconf/
for details), and report bugs against this CVS Auto
Hi,
on a Irix 6.5 system, using automake 1.4, autoconf 2.12,
i have the SHELL variable undefined
after aclocal;autoconf;autoheader;automake;./configure
The generated Makefile looks like :
[..]
# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
# PARTICULAR PURPOSE.
SHELL = @SHEL
19 matches
Mail list logo
