public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: asyropoulos@aol.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: __gnu_cxx error in OpenSolaris
Date: Thu, 19 May 2011 14:54:00 -0000	[thread overview]
Message-ID: <BANLkTinAGVeAZE9AX3Dt93unKfWYsP18vg@mail.gmail.com> (raw)
In-Reply-To: <8CDE444B8B510A6-1354-57FAA@webmail-m062.sysops.aol.com>

On 19 May 2011 15:03,  <asyropoulos@aol.com> wrote:
>
>> ignore that ... you didn't say whether you looked at the libstdc++.so
>> libs in /opt/gcc-4.6.0 and whether any of them use ELF symbol
>> versioning, which might make them incompatible.
>
> I have compiled Qt with gcc 4.5.3 and 4.6.0 and now I am trying again
> with 4.6.0 that has been configured to use GNU ld and GNU as. As about
> the versioning thing I am not sure what you mean, bur I hope the following
> help:
>
> $ elfdump -v /usr/lib/libstdc++.so.6.0.14
>
> Version Needed Section:  .SUNW_version
>    index  file                        version
>      [2]  libm.so.2                   SUNW_1.2
>      [3]  libgcc_s.so.1               GCC_3.0              [ INFO ]
>      [4]                              GCC_3.3              [ INFO ]
>      [5]                              GCC_4.2.0

This shows that /usr/lib/libstdc++.so doesn't use symvers.

> $ elfdump -v /opt/gcc-4.6.0/lib/libstdc++.so.6.0.15
>
> Version Definition Section:  .SUNW_version
>    index  version                     dependency
>      [1]  libstdc++.so.6                                   [ BASE ]
>      [2]  GLIBCXX_3.4
>      [3]  GLIBCXX_3.4.1               GLIBCXX_3.4
>      [4]  GLIBCXX_3.4.2               GLIBCXX_3.4.1
> ...

This shows that /opt/gcc-4.6.0/lib/libstdc++.so does use symvers.

Therefore they are not compatible.

If you compile with gcc 4.6 you must ensure the library in /opt is
found.  I suspect the wrong libstdc++.so is being found at link time.

Another alternative would be to rebuild gcc 4.6 without symbol
versioning enabled so that you get compatibility with the lib from gcc
4.5

  reply	other threads:[~2011-05-19 14:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 21:22 Dennis Clarke
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 [this message]
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=BANLkTinAGVeAZE9AX3Dt93unKfWYsP18vg@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --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).