[sr #110962] pass_all for z/OS

2024-01-16 Thread Mike Frysinger
Update of sr#110962 (group libtool):

  Status:None => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

you posted the patch to the list -- you don't need to file a bug report too


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/




Re: pass_all for z/OS

2024-01-16 Thread Mike Frysinger
On 17 Jan 2024 02:41, Igor Todorovski wrote:
> I’ve attached the git patch based on the master branch.

can you write a proper git commit and send it with send-email ?
or at least format it with `git format-patch` ?

the first version did:
openedition)

the new one does:
*openedition*)

isn't it always going to be "openedition" exactly ?  no need for globs ?
-mike


signature.asc
Description: PGP signature


RE: pass_all for z/OS

2024-01-16 Thread Igor Todorovski
Hi Mike,

I’ve attached the git patch based on the master branch.

Thanks,
Igor

On 2024-01-14, 1:57 AM, "Mike Frysinger"  wrote:
On 24 Nov 2023 15:19, Igor Todorovski wrote:
> diff --git a/libltdl/m4/libtool.m4 b/libltdl/m4/libtool.m4
> index d812584..f959bae 100644
> --- a/libltdl/m4/libtool.m4
> +++ b/libltdl/m4/libtool.m4

this file doesn't exist.  i don't know what git tree you're working against,
but it isn't the latest libtool one.  please rebase onto the latest version,
and send a proper git patch.  hand written ones like what you've posted here
are a pain to merge as it forces us to do a lot of manual work.
-mike



zos.patch
Description: zos.patch


Re: pass_all for z/OS

2024-01-13 Thread Mike Frysinger
On 24 Nov 2023 15:19, Igor Todorovski wrote:
> diff --git a/libltdl/m4/libtool.m4 b/libltdl/m4/libtool.m4
> index d812584..f959bae 100644
> --- a/libltdl/m4/libtool.m4
> +++ b/libltdl/m4/libtool.m4

this file doesn't exist.  i don't know what git tree you're working against,
but it isn't the latest libtool one.  please rebase onto the latest version,
and send a proper git patch.  hand written ones like what you've posted here
are a pain to merge as it forces us to do a lot of manual work.
-mike


signature.asc
Description: PGP signature


[sr #110962] pass_all for z/OS

2023-11-28 Thread anonymous
URL:
  <https://savannah.gnu.org/support/?110962>

 Summary: pass_all for z/OS
   Group: GNU Libtool
   Submitter: None
   Submitted: Tue 28 Nov 2023 05:16:41 PM UTC
Category: None
Priority: 5 - Normal
Severity: 3 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
Operating System: None


___

Follow-up Comments:


---
Date: Tue 28 Nov 2023 05:16:41 PM UTC By: Anonymous
Hi, I wanted to submit this patch for z/OS:
https://lists.gnu.org/archive/html/libtool-patches/2023-11/msg8.html

It's a simple patch to add pass_all for opendition (z/OS).

Thanks,
Igor







___

Reply to this item at:

  <https://savannah.gnu.org/support/?110962>

___
Message sent via Savannah
https://savannah.gnu.org/




z/OS

2010-07-14 Thread Alon Bar-Lev
Hello,

Does anyone has experience with libtool at z/OS open edition?
It builds static libraries, but it does not know how to build shared objects.

Thanks,
Alon.

___
http://lists.gnu.org/mailman/listinfo/libtool


Re: z/OS

2010-07-14 Thread Ralf Wildenhues
Hi Alon,

* Alon Bar-Lev wrote on Wed, Jul 14, 2010 at 04:48:22PM CEST:
 Does anyone has experience with libtool at z/OS open edition?
 It builds static libraries, but it does not know how to build shared objects.

AFAICS Libtool does not support z/OS yet, which means only static
libraries can be expected to work.

Porting Libtool to a new system is fairly straightforward if all the
documentation is available.  Are you willing to help with this?
If yes, I can start writing a number of questions for it.  You could
send pointers.  Generally, the right thing to do is grab git Libtool,
start reading the PORTING file, follow pointers there, and search for
PORTME in *.m4 files.  When you have something that works, start running
the test suites to find out that you're not quite done yet.  ;-)
Post whatever you can find out, including (very important!) test suite
output.

We may need copyright papers for nontrivial patches (so please don't
post them if you're not willing to go there; in that case it is easier
if you provide pointers and test suggested patches from us).

Hope that helps.

Cheers,
Ralf

___
http://lists.gnu.org/mailman/listinfo/libtool


Re: z/OS

2010-07-14 Thread Alon Bar-Lev
Sure,
I do anything to help.

However, I am missing some details on the z/OS linkage process, even
without libtool I could not find a proper way to create a shared
object (or dll which is the right name at this platform).
If nobody ported libtool to this platform, I will try to figure out
how to do this by-hand first.

Thanks!
Alon.

On Thu, Jul 15, 2010 at 7:43 AM, Ralf Wildenhues ralf.wildenh...@gmx.de wrote:
 Hi Alon,

 * Alon Bar-Lev wrote on Wed, Jul 14, 2010 at 04:48:22PM CEST:
 Does anyone has experience with libtool at z/OS open edition?
 It builds static libraries, but it does not know how to build shared objects.

 AFAICS Libtool does not support z/OS yet, which means only static
 libraries can be expected to work.

 Porting Libtool to a new system is fairly straightforward if all the
 documentation is available.  Are you willing to help with this?
 If yes, I can start writing a number of questions for it.  You could
 send pointers.  Generally, the right thing to do is grab git Libtool,
 start reading the PORTING file, follow pointers there, and search for
 PORTME in *.m4 files.  When you have something that works, start running
 the test suites to find out that you're not quite done yet.  ;-)
 Post whatever you can find out, including (very important!) test suite
 output.

 We may need copyright papers for nontrivial patches (so please don't
 post them if you're not willing to go there; in that case it is easier
 if you provide pointers and test suggested patches from us).

 Hope that helps.

 Cheers,
 Ralf


___
http://lists.gnu.org/mailman/listinfo/libtool


Re: z/OS

2010-07-14 Thread Howard Chu

Alon Bar-Lev wrote:

Sure,
I do anything to help.

However, I am missing some details on the z/OS linkage process, even
without libtool I could not find a proper way to create a shared
object (or dll which is the right name at this platform).
If nobody ported libtool to this platform, I will try to figure out
how to do this by-hand first.


I vaguely remember getting all this working back in 2002-2003. Unfortunately I 
haven't touched any z/OS systems since then, but you may be able to find some 
postings in these archives from back then. Also in the OpenSSL, Cyrus-SASL, 
and OpenLDAP mailing lists from that time period.


The z/OS linker has two operating modes, old style and XPLINK. I seem to 
recall that you can only create DLLs using XPLINK. This has some complications 
because XPLINK throws all object files into a single namespace; if you have 
two object files with the same filename foo.o they will clash and either the 
link will fail or only one of them will be inserted into the result.



Thanks!
Alon.

On Thu, Jul 15, 2010 at 7:43 AM, Ralf Wildenhuesralf.wildenh...@gmx.de  wrote:

Hi Alon,

* Alon Bar-Lev wrote on Wed, Jul 14, 2010 at 04:48:22PM CEST:

Does anyone has experience with libtool at z/OS open edition?
It builds static libraries, but it does not know how to build shared objects.


AFAICS Libtool does not support z/OS yet, which means only static
libraries can be expected to work.

Porting Libtool to a new system is fairly straightforward if all the
documentation is available.  Are you willing to help with this?
If yes, I can start writing a number of questions for it.  You could
send pointers.  Generally, the right thing to do is grab git Libtool,
start reading the PORTING file, follow pointers there, and search for
PORTME in *.m4 files.  When you have something that works, start running
the test suites to find out that you're not quite done yet.  ;-)
Post whatever you can find out, including (very important!) test suite
output.

We may need copyright papers for nontrivial patches (so please don't
post them if you're not willing to go there; in that case it is easier
if you provide pointers and test suggested patches from us).

Hope that helps.

Cheers,
Ralf



___
http://lists.gnu.org/mailman/listinfo/libtool




--
  -- Howard Chu
  CTO, Symas Corp.   http://www.symas.com
  Director, Highland Sun http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/

___
http://lists.gnu.org/mailman/listinfo/libtool


Re: z/OS

2010-07-14 Thread Ralf Wildenhues
Hi Howard,

* Howard Chu wrote on Thu, Jul 15, 2010 at 06:51:30AM CEST:
 
 The z/OS linker has two operating modes, old style and XPLINK. I
 seem to recall that you can only create DLLs using XPLINK. This has
 some complications because XPLINK throws all object files into a
 single namespace; if you have two object files with the same
 filename foo.o they will clash and either the link will fail or only
 one of them will be inserted into the result.

This should be fairly easy to work around: libtool already has machinery
in place to rename objects sub1/foo.o sub2/foo.o that are to be added to
the same static library; we could enable that machinery for shared
objects on systems that need it.

Cheers,
Ralf

___
http://lists.gnu.org/mailman/listinfo/libtool