glibmm exceptions broken after recent upgrades on CURRENT (debug
bland at FreeBSD.org
Fri Jun 1 06:41:05 UTC 2007
Ted Faber wrote:
> On Fri, Jun 01, 2007 at 10:03:12AM +0900, Alexander Nedotsukov wrote:
>> There is a problem on your side. From you backtrace I can see use of
>> /usr/X11R6/lib/libsigc-2.0.so.0 which is wrong. Most likely this points
>> out to incomplete upgrade.
> First of all, I'm sure you're right; there's something wrong on my end.
> I appreciate you helping me find it.
> I've upgraded to libsigc++-2.0.17_1 under the new compiler, which
> installed /usr/local/lib/libsigc-2.0.so.0 . gdb is reporting the
> library as /usr/X11R6/lib/libsigc-2.0.so.0 because /usr/X11R6 is now a
> symlink to /usr/local (after the upgrade) and the /usr/X11R6/lib prefix
> comes before /usr/local/lib in ldconfig's search path. They're the same
Right. This was fixed only two days ago.
Anyway take a look at kan@'s reply. Then there is a chance that problem
you have due libsigc++ and glibmm are built with gcc 3.4 and you build
main program with gcc 4.2. This true if your ports tree is older than 24
May when explicit gcc 3.4 requirement was relaxed. So my advise is:
cvsup, rebuild libsigc++, glibmm and try again.
> hut:~$ ls -li /usr/local/lib/libsigc-2.0.so.0 /usr/X11R6/lib/libsigc-2.0.so.0
> 4970046 -rwxr-xr-x 1 root wheel 46766 May 30 21:18 /usr/X11R6/lib/libsigc-2.0.so.0
> 4970046 -rwxr-xr-x 1 root wheel 46766 May 30 21:18 /usr/local/lib/libsigc-2.0.so.0
> I believe that the library (sigc) is the most recent one, and I know
> it's been g++ 4.2.0 compiled. I've actually been through every library
> in the ldd listing from my little test program and they've all been
> recompiled from ports using the new compiler.
> Do you have a guess what might be wrong with my libsigc++ that I haven't
> tried looking for?
> Thanks again for the help.
More information about the freebsd-current