I wrote:

> Jonathan McDowell <[EMAIL PROTECTED]> writes:
> 
> > The comp.unix.programmer FAQ (Section 6.2) suggests that to build static
> > libraries out of other static libraries you should use the original
> > object files.
> >
> > I've attached the output of a "make" on my system with a clean 0.1.20.
> > Also the output of "./configure" in case that's of use.
> 
> But apprearantly I changed that some time ago. I don't know what is
> the best way to handle this; should object files that are needed on
> some platforms but not others be included in liblsh.a, or linked into
> the executables later?

I think the following patch to src/Makefile.am.in should restore the
old behaviour. Can you try if it works for you?

/Niels

--- Makefile.am.in      1999/12/09 22:16:35     1.69
+++ Makefile.am.in      1999/12/28 14:19:09
@@ -64,7 +64,7 @@
        translate_signal.c tty.c twofish.c unpad.c userauth.c \
        werror.c write_buffer.c xalloc.c zlib.c

-liblsh_a_LIBADD = @LIBOBJS@
+# liblsh_a_LIBADD = @LIBOBJS@

 atoms_defines.h: atoms.in process_atoms
        $(BASH) $(srcdir)/process_atoms header <$(srcdir)/atoms.in
>$@T
@@ -106,7 +106,7 @@
 #        $(PERL) $(top_srcdir)/misc/mk-reverse-table ssh.h >$@T
 #        if test -s $@T ; then mv -f $@T $@ ; else touch $@ ; fi

-LDADD = liblsh.a symmetric/libsymmetric.a
+LDADD = liblsh.a symmetric/libsymmetric.a @LIBOBJS@

 # Is this rule needed?
 # all-recursive check-recursive: config.h

Reply via email to