GNU bug report logs - #54817
Outdated IBM XL Fortran shared library work around

Previous Next

Package: libtool;

Reported by: William T Jones <w.t.jones <at> nasa.gov>

Date: Sat, 9 Apr 2022 15:02:01 UTC

Severity: normal

To reply to this bug, email your comments to 54817 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-libtool <at> gnu.org:
bug#54817; Package libtool. (Sat, 09 Apr 2022 15:02:01 GMT) Full text and rfc822 format available.
Acknowledgement sent to William T Jones <w.t.jones <at> nasa.gov>:
New bug report received and forwarded. Copy sent to bug-libtool <at> gnu.org. (Sat, 09 Apr 2022 15:02:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: William T Jones <w.t.jones <at> nasa.gov>
To: bug-libtool <at> gnu.org
Subject: Outdated IBM XL Fortran shared library work around
Date: Sat, 9 Apr 2022 10:56:55 -0400

Hello,

Libtool 2.4.6 has an apparently outdated work around for the IBM XL 
Fortran compiler's inability to link shared libraries (see m4/libtool.m4 
lines 5208, 5237-5248).

As comments in m4/libtool.m4 state, the problem is with IBM XL Fortran 
version 10.1 on PowerPC.  However, we are now using IBM XL Fortran 
version 16.1 on PPC (ORNL summit) and it does allow linking of shared 
objects with xlf via the same "-qmkshrobj" command line option used by 
xlc and xlC on lines 5208-5210 of m4/libtool.m4.

To make matters worse, the workaround of using $LD to link shared 
libraries with Fortran objects does not easily work when linking mixed 
language object code into such a shared library (one needs to know IBM 
XL paths to libraries like libibmc++.so and libstdc++.so, for example).  
This is easily resolved when one links with `xlf -qmkshrobj ...`.

It is suggested that this workaround check for compiler version or be 
deprecated.

Resolution is appreciated,


-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    Bill Jones                                       W.T.JONES <at> NASA.GOV
    Mail Stop 128                     Computational AeroSciences Branch
    15 Langley Boulevard                           Research Directorate
    NASA Langley Research Center               Building 1268, Room 1044
    Hampton, VA  23681-2199                       Phone +1 757 864-5318
                                                    Fax +1 757 864-8816
                                             http://fun3d.larc.nasa.gov
Information forwarded to bug-libtool <at> gnu.org:
bug#54817; Package libtool. (Sat, 09 Apr 2022 16:26:02 GMT) Full text and rfc822 format available.

Message #8 received at 54817 <at> debbugs.gnu.org (full text, mbox):

From: Alex Ameen <alex.ameen.tx <at> gmail.com>
To: William T Jones <w.t.jones <at> nasa.gov>
Cc: 54817 <at> debbugs.gnu.org
Subject: Re: bug#54817: Outdated IBM XL Fortran shared library work around
Date: Sat, 9 Apr 2022 11:24:48 -0500

[Message part 1 (text/plain, inline)]
This sounds reasonable to me. Just to clarify, is this workaround still in
2.4.7?

On Sat, Apr 9, 2022, 10:02 AM William T Jones via Bug-libtool via Bug
reports for the GNU libtool shared library maintenance tool <
bug-libtool <at> gnu.org> wrote:

> Hello,
>
> Libtool 2.4.6 has an apparently outdated work around for the IBM XL
> Fortran compiler's inability to link shared libraries (see m4/libtool.m4
> lines 5208, 5237-5248).
>
> As comments in m4/libtool.m4 state, the problem is with IBM XL Fortran
> version 10.1 on PowerPC.  However, we are now using IBM XL Fortran
> version 16.1 on PPC (ORNL summit) and it does allow linking of shared
> objects with xlf via the same "-qmkshrobj" command line option used by
> xlc and xlC on lines 5208-5210 of m4/libtool.m4.
>
> To make matters worse, the workaround of using $LD to link shared
> libraries with Fortran objects does not easily work when linking mixed
> language object code into such a shared library (one needs to know IBM
> XL paths to libraries like libibmc++.so and libstdc++.so, for example).
> This is easily resolved when one links with `xlf -qmkshrobj ...`.
>
> It is suggested that this workaround check for compiler version or be
> deprecated.
>
> Resolution is appreciated,
>
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
>      Bill Jones                                       W.T.JONES <at> NASA.GOV
>      Mail Stop 128                     Computational AeroSciences Branch
>      15 Langley Boulevard                           Research Directorate
>      NASA Langley Research Center               Building 1268, Room 1044
>      Hampton, VA  23681-2199                       Phone +1 757 864-5318
>                                                      Fax +1 757 864-8816
>                                               http://fun3d.larc.nasa.gov
>
>
>
>
> _______________________________________________
> Bug-libtool mailing list
> Bug-libtool <at> gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-libtool
>

[Message part 2 (text/html, inline)]
Information forwarded to bug-libtool <at> gnu.org:
bug#54817; Package libtool. (Mon, 11 Apr 2022 18:19:01 GMT) Full text and rfc822 format available.

Message #11 received at 54817 <at> debbugs.gnu.org (full text, mbox):

From: William T Jones <w.t.jones <at> nasa.gov>
To: Alex Ameen <alex.ameen.tx <at> gmail.com>
Cc: 54817 <at> debbugs.gnu.org
Subject: Re: [EXTERNAL] Re: bug#54817: Outdated IBM XL Fortran shared library
 work around
Date: Mon, 11 Apr 2022 14:17:58 -0400

[Message part 1 (text/plain, inline)]
Alex,

It appears to be in the git repo, so if that is 2.4.7, then yes. 
Attached is a patch that works for me, checking to see if the XL Fortran 
compiler is at least Version 16 or better (maybe a better way of checking).

Thanks for responding so quickly,

Bill


I have more general workaround where I check the IBM XL Fortran 
version.  See example below:

On 4/9/22 12:24 PM, Alex Ameen wrote:
> This sounds reasonable to me. Just to clarify, is this workaround 
> still in 2.4.7?
>
> On Sat, Apr 9, 2022, 10:02 AM William T Jones via Bug-libtool via Bug 
> reports for the GNU libtool shared library maintenance tool 
> <bug-libtool <at> gnu.org> wrote:
>
>     Hello,
>
>     Libtool 2.4.6 has an apparently outdated work around for the IBM XL
>     Fortran compiler's inability to link shared libraries (see
>     m4/libtool.m4
>     lines 5208, 5237-5248).
>
>     As comments in m4/libtool.m4 state, the problem is with IBM XL
>     Fortran
>     version 10.1 on PowerPC.  However, we are now using IBM XL Fortran
>     version 16.1 on PPC (ORNL summit) and it does allow linking of shared
>     objects with xlf via the same "-qmkshrobj" command line option
>     used by
>     xlc and xlC on lines 5208-5210 of m4/libtool.m4.
>
>     To make matters worse, the workaround of using $LD to link shared
>     libraries with Fortran objects does not easily work when linking
>     mixed
>     language object code into such a shared library (one needs to know
>     IBM
>     XL paths to libraries like libibmc++.so and libstdc++.so, for
>     example).
>     This is easily resolved when one links with `xlf -qmkshrobj ...`.
>
>     It is suggested that this workaround check for compiler version or be
>     deprecated.
>
>     Resolution is appreciated,
>
>
>     -- 
>     =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
>          Bill Jones W.T.JONES <at> NASA.GOV
>          Mail Stop 128                     Computational AeroSciences
>     Branch
>          15 Langley Boulevard                           Research
>     Directorate
>          NASA Langley Research Center               Building 1268,
>     Room 1044
>          Hampton, VA  23681-2199                       Phone +1 757
>     864-5318
>                                                          Fax +1 757
>     864-8816
>     http://fun3d.larc.nasa.gov
>
>
>
>
>     _______________________________________________
>     Bug-libtool mailing list
>     Bug-libtool <at> gnu.org
>     https://lists.gnu.org/mailman/listinfo/bug-libtool
>     <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.gnu.org%2Fmailman%2Flistinfo%2Fbug-libtool&data=04%7C01%7Cw.t.jones%40nasa.gov%7C048ad35efb4d49bb2e5108da1a45877d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637851183171355906%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=A3cTh16ONe08vyfeB%2Fe2zNF1EGiGbVwdNfFFBVZp0is%3D&reserved=0>
>
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

    Bill JonesW.T.JONES <at> NASA.GOV
    Mail Stop 128                     Computational AeroSciences Branch
    15 Langley Boulevard                           Research Directorate
    NASA Langley Research Center               Building 1268, Room 1044
    Hampton, VA  23681-2199                       Phone +1 757 864-5318
                                                    Fax +1 757 864-8816
                                             http://fun3d.larc.nasa.gov

[Message part 2 (text/html, inline)]
[libtool-xlf.patch (text/plain, attachment)]
This bug report was last modified 2 years and 227 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.