Hello, I currenty build an arm-elf cross compiler. It is intended to use it together with eCos, a small RTOS. I want to use the C++ compiler and therefore I want to use the libstdc++-v3. Since eCos has no underlying exception support I want to disable all exceptions in the libstdc++-v3. This is possible with the -fno-exceptions flag during compiling the files of this library. However - I was unable to set the enviromental flags and/or configure arguments in such a way, that the libstdc++-v3 library is build with the -fno-exceptions flag. At the moment I use the following enviroment:
CXXFLAGS="-fno-exceptions" CFLAGS="-fno-exceptions" and the following configure call /usr/tmp/gcc-4.6.3/configure --target=arm-elf --prefix=/usr/local/arm-elf \ --enable-interwork --enable-multilib --enable-languages="c,c++" \ --enable-target-optspace --with-float=soft --with-newlib \ --with-gnu-as --with-gnu-ld \ --with-gxx-include-dir=/usr/local/arm-elf/include \ -disable-__cxa_atexit --with-gmp=/usr/local/ \ --disable-nls Can you help me figuring out what to change/configure to disable the exceptions or to enable the -fno-exceptions flag for the libstdc++-v3 part? One way is to modify the Makefile.am in the libstdc++-v3/libsupc++ to hardcode the CXXFLAGS. For my feeling however the configure script should evaluate the CXXFLAGS enviroment variable to do this decision. Thank you, Martin Laabs -- Dipl.-Ing. Martin Laabs Technische Universität Dresden Fakultät für Elektrotechnik und Informationstechnik Institut für Nachrichtentechnik, Lehrstuhl Hochfrequenztechnik Tel.: +49 (0)351 463-31918 Fax: +49 (0)351 463-37163 Email: martin.la...@tu-dresden.de
smime.p7s
Description: S/MIME Cryptographic Signature
