Open ksalerno99 opened 2 months ago
Need to ponder this a bit more, but I don't believe we can accept those changes. If we copy code from GNU, that code is GPL'd and will therefore cause us to become GPL - which is something we are unwilling to do.
Hi, The c library is LGPL, not GPL. Regards,Ken Yahoo Mail: Search, Organize, Conquer
On Tue, Sep 17, 2024 at 3:16 PM, Ralph @.***> wrote:
Need to ponder this a bit more, but I don't believe we can accept those changes. If we copy code from GNU, that code is GPL'd and will therefore cause us to become GPL - which is something we are unwilling to do.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Still, merits some careful consideration. We generally steer a very wide berth around GPL of any type. Might be a different approach required that doesn't in any way come near any GPL variation.
After discussing it here, I believe the consensus (at least for the PMIx portion) is to leave things as they are - the GPL connection is simply unacceptable and it doesn't appear we really gain anything. For example, we have not even attempted to support the Microsoft environment for more than a decade, and while this might allow things to compile on AIX and HP-UX, there is no guarantee that anything would work in those environments - and we have no users (let alone developers) with access to them.
So while I appreciate the input, I think this is something we will just have to leave alone. I'll leave the OMPI portion to that community.
Hi, Ralph. Thank you for you note. I understand, and can also confirm it does not work anyway (segfault, at least when compiled by IBM XL compiler version 17.1). Ken
On Sun, Oct 13, 2024 at 9:25 AM, Ralph @.***> wrote:
After discussing it here, I believe the consensus (at least for the PMIx portion) is to leave things as they are - the GPL connection is simply unacceptable and it doesn't appear we really gain anything. For example, we have not even attempted to support the Microsoft environment for more than a decade, and while this might allow things to compile on AIX and HP-UX, there is no guarantee that anything would work in those environments - and we have no users (let alone developers) with access to them.
So while I appreciate the input, I think this is something we will just have to leave alone. I'll leave the OMPI portion to that community.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Thank you for taking the time to submit an issue!
Background information
Make MPIx and PRRTE more portable for AIX, HP-UX and MSVC - do not include getopt.h (see patches)
Make MPL more portable for AIX, HP-UX, Solaris and MSVC - do not include ifaddrs.h (see patches)
What version of Open MPI are you using? (e.g., v4.1.6, v5.0.1, git branch name and hash, etc.)
5.0.5 stable
Describe how Open MPI was installed (e.g., from a source/distribution tarball, from a git clone, from an operating system distribution package, etc.)
source tarball
If you are building/installing from a git clone, please copy-n-paste the output from
git submodule status
.Please describe the system on which you are running
Details of the problem
Please describe, in detail, the problem that you are having, including the behavior you expect to see, the actual behavior that you are seeing, steps to reproduce the problem, etc. It is most helpful if you can attach a small program that a developer can use to reproduce your problem.
Note: If you include verbatim output (or a code block), please use a GitHub Markdown code block like below:
Patches: