AppImage / AppImage/AppImageKit

Investigate special linker script instead of a dynamic library for libstdc++.so

未關閉
#1,063 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
沒有語言資料
星號
9.4k
分支
588
PR 合併指標
PR 指標待擷取

描述

Currently, we recommend applications to be built on the oldest still-supported LTS release of Ubuntu. However, some applications need newer C++ compilers, which means that developers usually pull in a PPA that results in binaries being compiled in a way such that they don't work with the original libstdc++ that originally came with the oldest still-supported LTS release of Ubuntu.

Apparently CentOS devtoolset offers a solution for this issue.

We should understand how this magic in CentOS devtoolset works, and how it can be used with Ubuntu LTS...

https://stackoverflow.com/questions/52609269/c-project-compiled-with-modern-compiler-but-linked-against-outdated-libstdc/52611144#52611144

> The `devtoolset-6-gcc-c++` package provides a custom version of GCC that uses a special linker script instead of a dynamic library for libstdc++.so. That means the binaries it produces **do not depend on the newer libstdc++.so.6** and can be run on other CentOS machines that don't have devtoolset installed (i.e. they only have the older `libstdc++` library from GCC 4.8).

We should then document it in docs.appimage.org...

Reference:
https://github.com/wheybags/glibc_version_header/issues/20

cc @TheAssassin

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。