Matt Garman wrote:
There are two things that may help:
1. Try compiling your code with g++ instead of gcc. If you are using
new and delete, then you are writing c++ code.
I've *linked* with g++ and that solved the puzzle. With GCC2,
i could also link with gcc and had no trouble at all. However,
On Fri, Dec 05, 2003 at 03:06:05PM +0100, Oliver Lange wrote:
warning: undefined reference to `operator new(unsigned)'
warning: undefined reference to `operator delete(void*)'
warning: undefined reference to `vtable for
__cxxabiv1::__si_class_type_info'
These are calls from a C function
Hello everyone,
I've problems with compiling an own project with GCC 3.2.
Everything compiles well under GCC 2.95.3, but with GCC3,
i get linker errors like this:
warning: undefined reference to `operator new(unsigned)'
warning: undefined reference to `operator delete(void*)'
warning: undefined
, 2003 3:06 PM
Subject: [gentoo-user] gcc 3
Hello everyone,
I've problems with compiling an own project with GCC 3.2.
Everything compiles well under GCC 2.95.3, but with GCC3,
i get linker errors like this:
warning: undefined reference to `operator new(unsigned)'
warning: undefined reference
At least one person on this list reported that this broke qmail.
There could be other packages not unmasked, that could break as well.
Approach with caution.
On Fri, 2003-07-18 at 00:58, blade- wrote:
Hi all,
When I do emerge -Up world it lists the following
[ebuildU ]
Lincoln A. Baxter wrote:
At least one person on this list reported that this broke qmail.
There could be other packages not unmasked, that could break as well.
Approach with caution.
Indeed, mplayer is borked as well ...
if running on X and pressing f key screen become black and freezes.
After
On Friday 18 July 2003 23:39, Norbert Kamenicky wrote:
Lincoln A. Baxter wrote:
At least one person on this list reported that this broke qmail.
There could be other packages not unmasked, that could break as well.
Approach with caution.
Indeed, mplayer is borked as well ...
if running on X
Maybe you were wondering if when you recompile glibc you need to
recompile world?
Answer, in this case, no. Initially when switching from some versions of
glibc you needed to recompile all static libs on the system, but that
only really broke development against them.
Have a nice day.
On Fri,