On Friday, October 31, 2003 at 11:39:38 AM,

    Dimitar Zhekov <> wrote:

TCR>>>> the bootdisk target sets LIMITCXX to 1, but other
TCR>>>> targets (like generic) doesn't explicitely set it to
TCR>>>> 0 again. That causes possibly several build errors

DZ>>> That applies to all settings locked for whatever
DZ>>> reason. A global locked-value-restoration is needed...

TCR>> Who speaks about locking? I'm just advocating that
TCR>> this shouldn't be on by default, because that's a
TCR>> really non-standard option...

> It is not _on by default_:
> ./scripts/config.in:
> bool 'Disable exceptions and rtti in C++' ROCKCFG_LIMITCXX 0

It is on by default when going from bootdisk to any other target.
(actually we don't argue about this at all, because it's evident. But
it seems that there have been a lil' bug in our communication.)


> and it is locked to 1 in bootdisk:
> target/bootdisk/config.in:ROCKCFGSET_LIMITCXX=1
> [...]
>
> Basicly, when you choose the 'bootdisk' target and then go
> back to 'generic', nothing will be restored. See 'Binary
> package format' for a really bad example.

Exactly. That's all I reported, but you interpretated "Let's
generally disable (ie. lock) LIMITCXX in general) into my original
message, something which I didn't even intend to think of. And I again
interpretated that as "Well, it's not good as it is, but let's keep it."

Can you see the bug? :-)


So we both agree that "[a] global locked-value-restoration [whatever
that looks like in detail] is needed." -- Let me add "Its lack is a
severe bug that _must_ be fixed for a 2.0-final."


-- tcr () ``Ho chresim'eidos uch ho poll'eidos sophos''

-- 
To unsubscribe from this list: send a mail with the subject "unsubscribe
rock-linux" to <>. For more information about ROCK
Linux have a look at <https://www.rocklinux.org/>.