我觉得不如你作好在编译脚本 把源码包和编辑脚本发给他们 他们一运行脚本就编译了... 2010/10/20 Liu <proljc@xxxxxxxxx>: > 是要给很多人用,所以才麻烦的。自带libc.so可以么? > > 在 2010年10月20日 上午9:37,Hui Zhu <teawater@xxxxxxxxx> 写道: >> 你编译完的东西是不是准备给很多人用?我觉得为了方便你该要求他们都跟你的libc版本不一样 或者比你版本新 我记得这样就OK了 >> >> 2010/10/20 Liu <proljc@xxxxxxxxx>: >>> 我编译好的toolchain在别人机器上提示libc.so版本不一致,不能运行,能不能搞一套静态的啊? >>> 我看了 http://gcc.gnu.org/install/configure.html 关于 static 的相关参数只有 >>> --disable-shared ,一般我们都是用 --enable-shared 的,但是这个 --enable-shared >>> 啥含义也没看明白,这个好像是说libgcc静态动态的,不是gcc本身。 >>> Build shared versions of libraries, if shared libraries are supported >>> on the target platform. Unlike GCC 2.95.x and earlier, shared >>> libraries are enabled by default on all platforms that support shared >>> libraries. >>> If a list of packages is given as an argument, build shared libraries >>> only for the listed packages. For other packages, only static >>> libraries will be built. Package names currently recognized in the GCC >>> tree are `libgcc' (also known as `gcc'), `libstdc++' (not >>> `libstdc++-v3'), `libffi', `zlib', `boehm-gc', `ada', `libada', >>> `libjava' and `libobjc'. Note `libiberty' does not support shared >>> libraries at all. >>> >>> Use --disable-shared to build only static libraries. Note that >>> --disable-shared does not accept a list of package names as argument, >>> only --enable-shared does. >>> >>> >> >