RE: libtool on OS/390?

[Howard Chu]

> -----Original Message-----
> From: Bob Friesenhahn [mailto:address@hidden

> May experience thus far with libtool and OS/390 is that when libtool
> configures the C++ tag, configure exits since the C++ pre-processing
> doesn't pass Autoconf's sniff test and Autoconf is trained to exit if
> a compiler tool is unusable.
>
> It would be necessary to overcome basic problems like this before
> nuances like shared libraries can be considered.

Thanks for the response. I'm having trouble reconciling it though.

As I understand it, libtool's purpose is to provide portable linking of
objects. However, the projects that I work on which use it, only use it to
provide portable support of shared objects. As such, I don't see shared
libraries as a nuance, but as the sole benefit of the tool. Without shared
library support it offers absolutely no advantage over just driving a
platform's compiler tools directly.

To my mind, C++ support is the nuance. C is the least-common-denominator, not
C++. If you want to talk about portability and basic functionality, then the
discussion should be about getting the C compiler to behave and there it
should end. Configuring anything else should only be done by explicitly
requested options, and none of those options need to be worried about until
much further down the road.

> On Fri, 25 Apr 2003, Howard Chu wrote:
>
> > Has anyone worked on adding shared library support for
> OS/390 to libtool yet?
> > It's coming up fast on my TODO list but I was wondering if
> someone has beaten
> > me to it.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support