Re: [ECOS] --with-gxx-include-dir option

[Bart Veer <bartv at ecoscentric dot com>]

>>>>> "Jifl" == Jonathan Larmour <jifl at eCosCentric dot com> writes:

    Jifl> Bart Veer wrote:
    >> Now for the not so short answer. This configuration option
    >> controls where the C++ header files like <new> get installed.
    >> The default location is in $(PREFIX)/include. That is fine for
    >> building a native toolchain. For building a cross-compiler it
    >> is not quite right $(PREFIX)/include is for host-side header
    >> files, and <new> is a target-side header file.

    Jifl> We've been through this before elsewhere - I'm afraid I
    Jifl> think you somewhat misunderstand the intention and purpose
    Jifl> of what the GCC C++ guys have arranged.

No, I understand exactly what the g++ guys have done. I just don't
agree with it. Also I don't believe there are any real problems with
--with-gxx-include-dir since I have now built quite a few toolchains
using that option and there has not been a single reported SEGV with
those builds.

Further, I doubt that specifying --with-gxx-include-dir is the real
cause of the SEGV in the build that was originally reported. More
likely there is some other bug in the compiler that is now being
triggered because e.g. the length of some built-in string is different
and hence some other data is now differently aligned.

    >> Hence for the toolchains we build we specify
    >> --with-gxx-include-dir and put the C++ headers somewhere more
    >> appropriate. A useful side effect is that this allows us t)

    Jifl> Hmm... bit late for tea though ;-).

That was not the end of my message.

Bart

-- 
Bart Veer                       eCos Configuration Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss