From: Karel Gardas <kgardas@objectsecurity.com>
To: Geoff Keating <geoffk@geoffk.org>
Cc: gcc@gcc.gnu.org
Subject: Re: [pch-branch] missing binary operator issue.
Date: Thu, 02 Jan 2003 21:26:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.43.0301022219220.7028-100000@thinkpad.c0202001.roe.itnq.net> (raw)
In-Reply-To: <jmd6nfjuuy.fsf@desire.geoffk.org>
On Thu, 2 Jan 2003, Geoff Keating wrote:
> Karel Gardas <kgardas@objectsecurity.com> writes:
>
> > os-unix.cc:194:12: missing binary operator before token "("
>
> > 194 #if defined(HAVE_DLOPEN) && defined(HAVE_DYNAMIC)
>
> This should now be fixed.
>
Great! But now I get:
thinkpad:~/arch/devel/mico-devel/orb$ c++ -I../include -Wall -DFAST_PCH
-fpermissive -DPIC -fPIC -c orb_pch.h
../include/mico/code_set_registry.h:5: warning: `CORBA::Codeset::Info
_osf_cs_reg[193]' defined but not used
thinkpad:~/arch/devel/mico-devel/orb$ make
c++ -I../include -Wall -DFAST_PCH -fpermissive -DPIC -fPIC -c
os-unix.cc -o os-unix.pic.o
../include/mico/code_set_registry.h:5: warning: `CORBA::Codeset::Info
_osf_cs_reg[193]' defined but not used
/tmp/cczg5mr7.s: Assembler messages:
/tmp/cczg5mr7.s:2963: Error: symbol `.LCFI0' is already defined
/tmp/cczg5mr7.s:2965: Error: symbol `.LCFI1' is already defined
/tmp/cczg5mr7.s:2967: Error: symbol `.LCFI2' is already defined
/tmp/cczg5mr7.s:2969: Error: symbol `.LCFI3' is already defined
/tmp/cczg5mr7.s:2973: Error: symbol `.L2' is already defined
/tmp/cczg5mr7.s:2985: Error: symbol `.L4' is already defined
/tmp/cczg5mr7.s:2999: Error: symbol `.L6' is already defined
/tmp/cczg5mr7.s:3033: Error: symbol `.L10' is already defined
/tmp/cczg5mr7.s:3039: Error: symbol `.L11' is already defined
/tmp/cczg5mr7.s:3090: Error: symbol `.L15' is already defined
/tmp/cczg5mr7.s:3104: Error: symbol `.L8' is already defined
/tmp/cczg5mr7.s:3125: Error: symbol `.LCFI4' is already defined
/tmp/cczg5mr7.s:3127: Error: symbol `.LCFI5' is already defined
/tmp/cczg5mr7.s:3129: Error: symbol `.LCFI6' is already defined
/tmp/cczg5mr7.s:3131: Error: symbol `.LCFI7' is already defined
/tmp/cczg5mr7.s:3155: Error: symbol `.LEHB0' is already defined
/tmp/cczg5mr7.s:3157: Error: symbol `.LEHE0' is already defined
/tmp/cczg5mr7.s:3173: Error: symbol `.LEHB1' is already defined
/tmp/cczg5mr7.s:3181: Error: symbol `.LEHE1' is already defined
/tmp/cczg5mr7.s:3214: Error: symbol `.LEHB2' is already defined
/tmp/cczg5mr7.s:3216: Error: symbol `.LEHE2' is already defined
make: *** [os-unix.pic.o] Error 1
thinkpad:~/arch/devel/mico-devel/orb$
BTW: IMHO something strage is with my gcc3.4-pch... the branch compiled
10-20 % slower than version which I tried before, and whole configuration
process seems to be moved to build process. Is this behaviour right, or
have I done something wrong?
I've configured gcc with:
$HOME/cvs/gcc/pch-branch/gcc/configure --prefix=$HOME/usr/local/pch-branch
--enable-shared --enable-threads --enable-languages=c++ --disable-checking
--enable-__cxa_atexit
and build it with:
time make CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2
-fno-implicit-templates' bootstrap-lean
Unfortunately gcc -v said:
thinkpad:~/arch/devel/mico-devel/orb$ gcc -v
Reading specs from /home/karel/usr/local/pch-branch/lib/gcc-lib/i686-pc-linux-gnu/3.4-pch/specs
Configured with:
Thread model: posix
gcc version 3.4-pch 20021218 (experimental)
thinkpad:~/arch/devel/mico-devel/orb$
Anything what should I test?
Thanks,
Karel
--
Karel Gardas kgardas@objectsecurity.com
ObjectSecurity Ltd. http://www.objectsecurity.com
next prev parent reply other threads:[~2003-01-02 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 4:04 Karel Gardas
2003-01-02 17:59 ` Geoff Keating
2003-01-02 21:26 ` Karel Gardas [this message]
2003-01-02 22:21 ` Andrew Pinski
2003-01-07 19:32 ` Geoff Keating
2003-01-08 16:06 ` Karel Gardas
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=Pine.LNX.4.43.0301022219220.7028-100000@thinkpad.c0202001.roe.itnq.net \
--to=kgardas@objectsecurity.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.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).