Makefile.am:24: automake does not support info_TEXINFOS being defined
conditionally
automake-1.10:
automake-1.10: ## Internal Error ##
automake-1.10:
automake-1.10: undefined condition `TRUE' for `info_TEXINFOS'
automake-1.10: info_TEXINFOS:
Bruce Korb writes:
Karl Berry wrote:
2. Please make available enable/disable macros for each output type:
info, html, xml, ps, ...
I agree we could support all the formats (currently: info html xml
docbook ps pdf plaintext) uniformly,
Good.
I would prefer a single
ltmain.sh (GNU libtool) 1.5 (1.1220 2003/04/05 19:32:58)
automake (GNU automake) 1.8
Hi,
I want to create a libtool module written in Fortran 77 and ended up
with the following code:
$ cat configure.ac
AC_INIT([foo], [1.0], [EMAIL PROTECTED])
AM_INIT_AUTOMAKE([1.7 foreign no-define])
Tom Howard writes:
Sorry if I'm being dense, but (after reading the referenced messages) I don't
understand why using the -shared flag will only produce the a .so file.
Won't it still produce a .so.X, .so.X.X.X and .la files as well?
In libtool jargon, .so file is a synonym for a shared
Tom Howard writes:
That's my point. My understanding of Stephen problem is that he doesn't want
to build/install the companion files.
[...]
So in his situation, patching libtool and using -shared isn't really going to
solve his problem. Correct?
As already pointed out by Daniel Reed,
Stephen Torri writes:
So by patching my libtool I should be able to put the -shared flag in my
AM_LDFLAGS for the Makefile.am and only get the shared.so file right?
Yes, but it makes sense adding it to CFLAGS, too.
! If the @samp{-static} option is given, then only a @samp{.o} file is
!
See http://mail.gnu.org/archive/html/libtool/2003-08/msg2.html,
for more details.
--
Ralph
Waldemar Rosenbach [EMAIL PROTECTED] writes:
But what is the best way to deal with the platform depend stuff in the
interface?
A platform independent interface!
--
Ralph
Alexandre Duret-Lutz [EMAIL PROTECTED] writes:
Suggestions so far are to put this information in the source
filename. For instance teaching Automake to install
`pt_BR-foo.1' or `foo.1.pt_BR' as `pt_BR/man1/foo.1',
with the rewriting issues Josef pointed out.
`foo.1.pt_BR' breaks Emacs'
Ralf Corsepius [EMAIL PROTECTED] writes:
Am Mit, 2002-07-03 um 14.58 schrieb Schleicher Ralph (LLI):
To the Automake maintainers: please device a way for adding
user-defined
configure options to configure when re-running configure (e.g., grep
the
configure command line from config.log
Ralf Corsepius [EMAIL PROTECTED] writes:
Am Mit, 2002-07-03 um 09.44 schrieb Ionutz Borcoman:
Or is there a simple command to do this (but keeping all the options
I've give to configure) ?
make
Wrong answer. Read the question more carefully.
To the Automake maintainers: please device a
11 matches
Mail list logo