From: Michael Gatford <michael.gatford@aprsmartlogik.com>
To: gcc help <gcc-help@gcc.gnu.org>
Subject: gcc 4.0.2, Fedora C4 problem
Date: Wed, 12 Jul 2006 16:08:00 -0000 [thread overview]
Message-ID: <44B51E87.4010601@aprsmartlogik.com> (raw)
Hi,
I am getting the following error when compiling some code on a Fedora C4
box and gcc 4.0.2.
I've done some googling but have no idea how to deal with the "throws
different exceptions" errors.
Mike
g++ -Wall -Wunused -Wno-uninitialized -Wno-return-type
-fno-strength-reduce -O2 -DUNIX -DLINUX -DMACHINE=\"Linux-libc6.1\" -w
-Dstrerror=strerror -I. -I/home2/dependencies/Semaphore/JFS/3.2/include
-I/home2/dependencies/Semaphore/PowerQuery/1.5.22/include -c -o
Linux-libc6.1/FmUser.o FmUser.cxx
/usr/include/unistd.h:1026: error: declaration of ‘char* crypt(const
char*, const char*) throw ()Â’ throws different exceptions
crypt.h:104: error: than previous declaration ‘char* crypt(const char*,
const char*)Â’
/usr/include/unistd.h:1030: error: declaration of ‘void encrypt(char*,
int) throw ()Â’ throws different exceptions
crypt.h:111: error: than previous declaration ‘void encrypt(char*, int)’
/usr/include/stdlib.h:917: error: declaration of ‘void setkey(const
char*) throw ()Â’ throws different exceptions
crypt.h:107: error: than previous declaration ‘void setkey(const char*)’
FmUser.cxx: In member function ‘char* FmUser::makeKey() const’:
FmUser.cxx:372: error: no matching function for call to
‘transform(__gnu_cxx::__normal_iterator<char*, std::basic_string<char,
std::char_traits<char>, std::allocator<char> > >,
__gnu_cxx::__normal_iterator<char*, std::basic_string<char,
std::char_traits<char>, std::allocator<char> > >,
__gnu_cxx::__normal_iterator<char*, std::basic_string<char,
std::char_traits<char>, std::allocator<char> > >, <unknown type>)Â’
gmake: *** [Linux-libc6.1/FmUser.o] Error 1
next reply other threads:[~2006-07-12 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 16:08 Michael Gatford [this message]
2006-07-12 16:29 ` Andrew Haley
2006-07-12 16:20 Brian D. McGrew
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=44B51E87.4010601@aprsmartlogik.com \
--to=michael.gatford@aprsmartlogik.com \
--cc=gcc-help@gcc.gnu.org \
/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).