[3663] in Kerberos-V5-bugs

home help back first fref pref prev next nref lref last post

Re: [krbdev.mit.edu #1261] Creation of shared libraries ignore

daemon@ATHENA.MIT.EDU (Sam Hartman)
Thu Nov 21 10:03:09 2002

To: rt-comment@krbdev.mit.edu
Cc: krb5-prs@mit.edu
From: Sam Hartman <hartmans@mit.edu>
In-Reply-To: <rt-1261-3720.2.73764777443787@krbdev.mit.edu> ("Tom Yu via
 RT"'s message of "Fri, 15 Nov 2002 19:30:03 -0500 (EST)")
Message-ID: <tsl7kf7c6ek.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Errors-To: krb5-bugs-admin@mit.edu
Date: Thu, 21 Nov 2002 10:02:43 -0500

>>>>> "Tom" == Tom Yu via RT <rt-comment@krbdev.mit.edu> writes:

>>>>> "Ezra" == Ezra Peisach via RT <rt-comment@krbdev.mit.edu> writes:

    Ezra> a) config/lib.in: Change the invocation of LDCOMBINE in the
    Ezra> creation of the library to include $(LDFLAGS)

    Ezra> This would make the --ldopts a global change for all
    Ezra> architectures.

    Tom> One possible problem with this is that LDFLAGS is meant to be
    Tom> used during program link time.  It is therefore intended to
    Tom> be suitable for passing to the compiler driver.  Different
    Tom> architectures vary as to whether they use ld or $(CC) to
    Tom> build shared libraries, and we'd have to account for the
    Tom> possibility that LDFLAGS that are suitable for the compiler
    Tom> driver might not be suitable for ld.

I contend it is almost always wrong to use ld to build shared libraries:

* cc may link against aditional libraries that are required (see
  hppa/linux--using ld is guaranteed to fail)

* cc may need to include additional flags that may change over time.

_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
http://mailman.mit.edu/mailman/listinfo/krb5-bugs

home help back first fref pref prev next nref lref last post