From: 龙海涛 <longhaitao@otsc.com.cn>
To: yantux yantux <yantux@yandex.ru>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc 4.1.1 C++ in Minix3 OS : new and delete problem...
Date: Fri, 07 Dec 2007 08:21:00 -0000 [thread overview]
Message-ID: <1197015664.3694.27.camel@localhost.localdomain> (raw)
In-Reply-To: <215431196955259@webmail19.yandex.ru>
On Thu, 2007-12-06 at 18:34 +0300, yantux yantux wrote:
> I use gcc 4.1.1 in Minix3 OS
>
> I was wrote question about compiling C++ by gcc 4.1.1 in Minix3.
just tell us what options you use *exactly*
>
> What menas this is error?
> /usr/local/gnu/lib/libfltk.a(Fl_Group.o):Fl_Group.o:(.text+0x780):
> undefined reference to `operator delete[](void*)'
> /usr/local/gnu/lib/libfltk.a(Fl_Group.o):Fl_Group.o:(.text+0xa03):
> undefined reference to `operator new[](unsigned long)'
> /usr/local/gnu/lib/libfltk.a(Fl_arg.o):Fl_arg.o:(.text+0x654):
> undefined reference to `operator new[](unsigned long)'
> /usr/local/gnu/lib/libfltk.a(Fl_arg.o):Fl_arg.o:(.text+0x69f):
> undefined reference to `operator delete[](void*)'
i guess in your project there are some .c and .cpp file,this kind of
problem may happen when you combine them togther. Or maybe when you
compiler a cpp project, you use gcc instead of g++.
just guess.
>
> How correct compile C++ programm? What bad settings and flag in make.sh sript?
could you tell us the *exact* context of make.sh?
>
> Sorry for my english.
> Thank you.
>
> Best regards,
> Yantux.
next prev parent reply other threads:[~2007-12-07 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 15:34 yantux yantux
2007-12-07 8:21 ` 龙海涛 [this message]
2007-12-08 23:44 ` yantux yantux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1197015664.3694.27.camel@localhost.localdomain \
--to=longhaitao@otsc.com.cn \
--cc=gcc-help@gcc.gnu.org \
--cc=yantux@yandex.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).