Repository navigation
Build provenance and license materials for GCC runtime DLLs in PaddlePaddle 3.3.1 Windows wheel #79904
Unanswered
lamonslurye-lgtm
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello PaddlePaddle maintainers,
Thank you for maintaining PaddlePaddle. We are reviewing the native dependencies distributed in the official Windows x64 wheel
paddlepaddle-3.3.1-cp312-cp312-win_amd64.whl. We verified that these three files inpaddle/libs/match the wheel byte for byte, and that they also match the prebuiltlapack_win_v3.10.0.20210628.zipreferenced by the PaddlePaddle v3.3.1lapack.cmake:libgcc_s_seh-1.dll1C12BBB54F5D2650F94BAA6A0C8BD8DC912CFE2CF62D341211A8813DDDF09570libgfortran-3.dllBE396C5CD0D43194F0D753EF65B4F893F456A4EF8D90F60BB26DF33D7914F964libquadmath-0.dllB1C0B44D48038FAA92A259E0D66F21FBA2EACA294F7AE18CF86CB3B9FEB423E9We distribute the unmodified wheel components with a closed-source paid Windows desktop application. We would like to identify the exact upstream source and notices for these binaries; we are not requesting legal advice. Could you please help with the following technical and publication details?
lapack_win_v3.10.0.20210628.zipavailable? The Paddlelapack.cmakeidentifies the prebuilt archive, but does not appear to describe how its GCC runtime DLLs were built.GCC: (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 4.9.3andGCC: (x86_64-win32-seh-rev1, Built by MinGW-W64 project) 6.2.0strings.libgfortran-3.dllalso contains paths undersrc/gcc-6.2.0/libgfortran/. Do you know why both compiler-version markers appear, and which source objects actually make up each final DLL?libquadmath-0.dll, and should any exception be treated differently fromlibgcc_s_seh-1.dllandlibgfortran-3.dll?libquadmath-0.dll, is there an upstream-recommended way to document users' ability to modify and replace the library? If any GCC runtime code was linked statically into the accompanying LAPACK/BLAS DLLs, is that documented in a component or link manifest?Pointers to existing build records or to the original publisher of the prebuilt archive would be very helpful. We do not need a legal determination from the maintainers. Thank you for your time and help.
All reactions