-
Boqun Feng authored
According to http://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html , the versions of standard libraries have a strong matchup with versions of compilers, so linkage errors occur when using libstdc++ in *external* submodule when using GCC 4.9.0. As there is such a mixup in the build system, the environments of standard libraries in link time should be switchable to support GCC whose version doesn't match up with external's. *_env variables are introduced. To build a image with standard libraries in the host, run `make build_env=host'. For fine-grained settings, use gcc_lib_env and cxx_lib_env. Reviewed-by:
Nadav Har'El <nyh@cloudius-systems.com> Signed-off-by:
Boqun Feng <boqun.feng@linux.vnet.ibm.com> Signed-off-by:
Pekka Enberg <penberg@cloudius-systems.com>
Boqun Feng authoredAccording to http://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html , the versions of standard libraries have a strong matchup with versions of compilers, so linkage errors occur when using libstdc++ in *external* submodule when using GCC 4.9.0. As there is such a mixup in the build system, the environments of standard libraries in link time should be switchable to support GCC whose version doesn't match up with external's. *_env variables are introduced. To build a image with standard libraries in the host, run `make build_env=host'. For fine-grained settings, use gcc_lib_env and cxx_lib_env. Reviewed-by:
Nadav Har'El <nyh@cloudius-systems.com> Signed-off-by:
Boqun Feng <boqun.feng@linux.vnet.ibm.com> Signed-off-by:
Pekka Enberg <penberg@cloudius-systems.com>