CURl C-API

Got a curl c api based on a previous curl distro.
Now I'm trying to rebuild using the current miniconda distro but......

IEW2456E 9207 SYMBOL zos_compat_malloc_wrapper UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL
LIBRARY.

and

IEW2456E 9207 SYMBOL gss_release_name UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.

amongst a number of other similar missing symbols.

Are these objects in Rocket code ? If not has anyone got a suggestion ?


------------------------------
hank oerlemans
Senior Software Engineer
HCL America Inc.
North Sydney NSW AU
------------------------------

Hello Hank,

We appreciate your interest in Ported Tools. To use libcurl from the latest build of curl, you need two additional libraries: libunixcompat and Kerberos. The absence of these libraries causes the errors that you mentioned.

We have decided not to include libunixcompat and Kerberos into Rocket Open AppDev for Z portfolio, which means their binaries are not published.

To resolve your current build issues, you can build libunixcompat from the source code (it's a part of the xlc-wrapper package), and port Kerberos to z/OS using the community source code. Please note that Rocket doesn't provide any guidance on the porting process.

Customers on support contract can request full support of additional packages, and in this case the ready-to-use binaries can be made available on our private channel. If you are interested in the support option, please leave your request here:

https://www.rocketsoftware.com/openappdev-for-z

Regards,
Vladimir

------------------------------
Vladimir Ein
Software Engineer
Rocket Software
------------------------------

Hello Hank,

We appreciate your interest in Ported Tools. To use libcurl from the latest build of curl, you need two additional libraries: libunixcompat and Kerberos. The absence of these libraries causes the errors that you mentioned.

We have decided not to include libunixcompat and Kerberos into Rocket Open AppDev for Z portfolio, which means their binaries are not published.

To resolve your current build issues, you can build libunixcompat from the source code (it's a part of the xlc-wrapper package), and port Kerberos to z/OS using the community source code. Please note that Rocket doesn't provide any guidance on the porting process.

Customers on support contract can request full support of additional packages, and in this case the ready-to-use binaries can be made available on our private channel. If you are interested in the support option, please leave your request here:

https://www.rocketsoftware.com/openappdev-for-z

Regards,
Vladimir

------------------------------
Vladimir Ein
Software Engineer
Rocket Software
------------------------------

Thanks for the information

------------------------------
hank oerlemans
Lead Software Engineer
HCL America Inc.
North Sydney NSW AU
------------------------------