public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dennis Clarke <dclarke@blastwave.org>
To: asyropoulos@aol.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: __gnu_cxx error in OpenSolaris
Date: Wed, 18 May 2011 21:22:00 -0000	[thread overview]
Message-ID: <62890.10.0.66.17.1305752970.squirrel@interact.purplecow.org> (raw)


>
>>I have had good results for both Sparc and i386/AMD64 with or without
> gas
>>( GNU as ) however you must always use Sun provided LD=/usr/ccs/bin/ld
> if
>>you want things to work.
>
> Yes but I have forgot to say that I have tried with the Solaris ld and
> the result
> was in essence the same. Also,
>
> $ elfdump -s /usr/lib/libstdc++.so.6.0.14|grep gnu_cxx
>
> shows that the sumbols are included in the library!
>
> BTW, have you compiled the latest Qt with gcc? You know solaris
> studio is not an option as most useful programs do not compile
> with it.

Yeah I have hit that issue myself over and over to a point where I gave up
on Sun Studio. Such is life.

As for QT , well I have not tried in a while.

Stick with GCC and you will be happy.

-- 
Dennis Clarke
dclarke@opensolaris.ca  <- Email related to the open source Solaris
dclarke@blastwave.org   <- Email related to open source for Solaris


             reply	other threads:[~2011-05-18 21:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 21:22 Dennis Clarke [this message]
2011-05-19  8:43 ` Dr. David Kirkby
2011-05-19 13:43   ` Jonathan Wakely
     [not found]     ` <8CDE428B4BB3E2C-1354-53EC9@webmail-m062.sysops.aol.com>
     [not found]       ` <BANLkTikMNaDXY51WiHujQ0jxw3eE64fcFg@mail.gmail.com>
2011-05-19 14:51         ` asyropoulos
2011-05-19 14:54           ` Jonathan Wakely
2011-05-19 16:34             ` Jonathan Wakely
2011-05-19 17:00               ` asyropoulos
2011-05-19 20:09     ` David Kirkby
2011-05-20  1:57       ` Jonathan Wakely
2011-05-20  4:37         ` Ian Lance Taylor
2011-05-20  6:50         ` Dr. David Kirkby
2011-05-20  6:54           ` Jonathan Wakely
2011-05-20 14:29             ` Miles Bader
2011-05-20  6:20   ` Miles Bader
2011-05-20  7:00     ` Dr. David Kirkby
2011-05-20 12:17       ` Jonathan Wakely
2011-05-25 13:22         ` asyropoulos
2011-05-25 13:28           ` Jonathan Wakely
2011-05-25 14:55             ` asyropoulos
2011-05-25 16:20               ` Jonathan Wakely
2011-05-25 17:00               ` Ian Lance Taylor
2011-05-25 17:51                 ` asyropoulos
2011-05-25 18:12                   ` Jonathan Wakely
2011-05-25 18:46                     ` asyropoulos
2011-05-26 11:23                       ` Paul Smith
2011-05-25 18:40                   ` Ian Lance Taylor
  -- strict thread matches above, loose matches on Subject: below --
2011-05-19 17:09 Dennis Clarke
2011-05-19 19:03 ` asyropoulos
2011-05-18 20:32 Dennis Clarke
2011-05-18 21:20 ` asyropoulos
2011-05-18 21:24   ` Jonathan Wakely
2011-05-18 19:58 asyropoulos
2011-05-18 20:48 ` Jonathan Wakely
2011-05-18 20:59   ` asyropoulos
2011-05-19  0:12 ` Marc Glisse
2011-05-19 14:04   ` asyropoulos

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=62890.10.0.66.17.1305752970.squirrel@interact.purplecow.org \
    --to=dclarke@blastwave.org \
    --cc=asyropoulos@aol.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).