Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Jan 2011 21:42:11 +0600
From:      Sender Ghost <lightside@safebox.ru>
To:        pav@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org
Subject:   Re: ports/153969: [PATCH] devel/upp: Update from 2008.1 to 2791
Message-ID:  <4D4040D3.8040400@safebox.ru>
In-Reply-To: <201101261303.p0QD31JN065151@freefall.freebsd.org>
References:  <201101261303.p0QD31JN065151@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
pav@FreeBSD.org wrote:
> Does not link here:
>
> undefined reference to `typeinfo for std::bad_alloc'
> more undefined references to `__cxa_call_unexpected' follow
> [..]
>
> gazzilions of these ..
>
>    
On which devel/upp version and which compiler used? Could you be more 
specific?

If it was for 2791 version and gcc 4.2.1 (from base) compiler (with 
default -O2 optimizations), then all compiles well here.
Looking at errors, I think, it can be related to used compiler and 
differences between STL.

The places with std::bad_alloc are following:
uppsrc/Core/Core.h:201:
inline void *operator new(size_t size) throw(std::bad_alloc) { void *ptr 
= UPP::MemoryAlloc(size); return ptr; }
uppsrc/Core/Core.h:204:
inline void *operator new[](size_t size) throw(std::bad_alloc) { void 
*ptr = UPP::MemoryAlloc(size); return ptr; }

They related to Ultimate++ Framework memory allocator.
I can suggest to define flagUSEMALLOC in this case (with such compiler) 
for MAKE_ARGS, e.g.:
MAKE_ARGS=      Macro="-DflagGUI -DflagGCC -DflagSHARED -DflagPOSIX 
-DflagBSD -DflagFREEBSD -DflagUSEMALLOC"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D4040D3.8040400>