[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pspp-commits] [SCM] GNU PSPP branch, master, updated. v0.6.1-2063-gf3dc

From: Ben Pfaff
Subject: [Pspp-commits] [SCM] GNU PSPP branch, master, updated. v0.6.1-2063-gf3dc389
Date: Thu, 12 May 2011 02:32:00 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU PSPP".

The branch, master has been updated
       via  f3dc389d453a81ffd3957662e287c96b3a73c4bb (commit)
      from  91629b1685cfb3c0606158257695a6ff6385242f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit f3dc389d453a81ffd3957662e287c96b3a73c4bb
Author: Ben Pfaff <address@hidden>
Date:   Wed May 11 19:31:22 2011 -0700

    configure: Use $LIB<x> for linking a program, not $LTLIB<x>.
    The gettext manual says:
         address@hidden@' is for use without `libtool', address@hidden@' is for
         use with `libtool'
    It has similar wording for libiconv.
    Since there's lots of libtool-related stuff in the PSPP makefiles, I
    assumed that PSPP needed $LTLIB<x>.  But it now appears that this is
    only correct for linking a libtool library, not for linking a
    program that links against libtool libraries.
    On GNU/Linux, both $LIB<x> and $LTLIB<x> expand to the empty string,
    so I couldn't tell from experimenting there.
    This should fix link failures with Mingw, reported by Harry Thijssen


Summary of changes: |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]