RE: Building .so files only.

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 l

RE: Building .so files only.

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, -a

Re: Building .so files only.

See , for more details. -- Ralph

RE: Building .so files only.

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 > !

Building Fortran 77 libtool modules

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]) AC_CONFIG_

Re: RFC: doc for `Handling Tools that Produce Many Outputs'

Alexandre Duret-Lutz writes: > Eric> On Sat, Jan 31, 2004 at 11:28:29PM +0100, Alexandre Duret-Lutz wrote: > >> One of the output (here `data.c') is used as a witness of the run of > >> `foo'. [...] > > Eric> Hmm. I understand what you're saying here, but "witness" seems > Eric> an odd choice of

Re: html texinfo install?

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 pref

Re: auto-regenerating Makefile.in and Makefile files

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

Re: auto-regenerating Makefile.in and Makefile files

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 >

Re: installing config.h

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

Re: automake/335: Multi-language man pages

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

Re: i want to use linker ld with libtool on hpux

"Kremp, Johannes" <[EMAIL PROTECTED]> writes: > my binaries are linked against shared libraries. but when move this > libraries in another directory and write this new dirctory in the > environment variable SHLIB_PATH the binary does not find the > libraries. That's HP-UX magic. ;-) > my libto