问在一个Linux发行版上使用g++编译的可执行文件在另一个Linux发行版上使用有限制吗？

EN

- This is because most people don't turn on the hardware specific optimizations (but they can).
- Moving binaries across chip sets is highly unlikely to work 
- Moving binaries from older to newer members of a hardware family is likely to work
- Moving binaries from newer to older members of a hardware family is less likely (but will depend on optimization and compiler settings (ir moving from 64 to 32 bit architecture is unlikely to work).

- The version of OS that a binary will work across will depend on the version of the compiler used to build it and the host OS.
- If the compiler has changes in the ABI it generates then all bets are off. But usually a change in the ABI generated by the compiler will be a major issue and thus only happen at major points in the OS road map (not at minor increments).

- Don't specifically go out and update the development environment (use the one that comes with distribution (if you do the default updates they will not break backwards compatibility)).
- Building is easy just read the `README` file. But usually it involves running two commands `./configure` and `make`. If you don't want anything special you usually do not need to do anything else.