RE: IBM OS/390 z/OS

[Howard Chu]

Here's the followup to the previous patch, that actually allows libtool to be
configured on  z/OS. I found some things broke during a install/relink, and I
didn't have much luck tracking it down. Since z/OS doesn't embed paths into
binaries anyway, I decided to disable relinking if hardcode_action =
unsupported.

Now that I have this working on 1.4.3 I'll try to integrate with the current
libtool CVS. But I'm posting this patch against 1.4.3 so that back-rev
projects (like OpenLDAP) can use it immediately.

Note - this patch requires all code to be compiled with the XPLINK calling
convention. I've already noted this in the OpenLDAP FAQ on porting to OS/390,
just wanted to reiterate here.

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

> -----Original Message-----
> From: Howard Chu [mailto:address@hidden
> Sent: Wednesday, June 11, 2003 4:48 AM
> To: 'address@hidden'
> Subject: IBM OS/390 z/OS
>
>
> This is a diff against libltdl from libtool 1.4.3 to support
> dynamic loading on IBM OS/390. It's obviously of limited use,
> as I haven't got configure detecting all the things it needs
> to know yet. I'm currently using this with a manually edited
> libtool script to generate shared libraries. (blech...) Since
> I saw the patches/discussion go by about controlling which
> languages libtool detects, I figure it won't be too long
> before we can get the C compiler fully supported in this
> environment, while ignoring C++, Fortran, etc...
>
>   -- Howard Chu
>   Chief Architect, Symas Corp.       Director, Highland Sun
>   http://www.symas.com               http://highlandsun.com/hyc
>   Symas: Premier OpenSource Development and Support
>

dif.txt
Description: Text document