chrome - libstc++ vs libestdc++ and other errors

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

chrome - libstc++ vs libestdc++ and other errors

Kenneth R Westerback
It's weird I know, but I run things from the command line. Trying out
chrome, I see a few odd messages:

$ chrome &
[1] 15807
$ /usr/local/bin/chrome[17]: ulimit: bad limit: Invalid argument
/usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
[15807:-600466432:0402/082149:ERROR:user_style_sheet_watcher.cc(167)] Failed to setup watch for /home/krw/.config/chromium/Default/User StyleSheets/Custom.css
/usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
[15807:-691757280:0402/082149:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
[15807:-691757280:0402/082149:ERROR:CONSOLE(1)] "Uncaught ReferenceError: ntp is not defined", source:  (1)
[15807:-691757280:0402/082153:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()

This is on all -current amd64 box (system and compiled ports) as of last night. I can't find any old libraries hanging around.

.... Ken

Reply | Threaded
Open this post in threaded view
|

Re: chrome - libstc++ vs libestdc++ and other errors

Marc Espie-2
On Tue, Apr 02, 2013 at 08:46:05AM -0400, Kenneth R Westerback wrote:

> It's weird I know, but I run things from the command line. Trying out
> chrome, I see a few odd messages:
>
> $ chrome &
> [1] 15807
> $ /usr/local/bin/chrome[17]: ulimit: bad limit: Invalid argument
> /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> [15807:-600466432:0402/082149:ERROR:user_style_sheet_watcher.cc(167)] Failed to setup watch for /home/krw/.config/chromium/Default/User StyleSheets/Custom.css
> /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> [15807:-691757280:0402/082149:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
> [15807:-691757280:0402/082149:ERROR:CONSOLE(1)] "Uncaught ReferenceError: ntp is not defined", source:  (1)
> [15807:-691757280:0402/082153:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
>
> This is on all -current amd64 box (system and compiled ports) as of last night. I can't find any old libraries hanging around.

The warnings are because the new libestdc++ has extra error messages...
A few weeks ago, I proposed that we add some blank placeholder messages to
the libstdc++ in source. That would get rid of that specific problem.

Reply | Threaded
Open this post in threaded view
|

Re: chrome - libstc++ vs libestdc++ and other errors

Stuart Henderson
In reply to this post by Kenneth R Westerback
On 2013/04/02 08:46, Kenneth R Westerback wrote:

> It's weird I know, but I run things from the command line. Trying out
> chrome, I see a few odd messages:
>
> $ chrome &
> [1] 15807
> $ /usr/local/bin/chrome[17]: ulimit: bad limit: Invalid argument
> /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> [15807:-600466432:0402/082149:ERROR:user_style_sheet_watcher.cc(167)] Failed to setup watch for /home/krw/.config/chromium/Default/User StyleSheets/Custom.css
> /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> [15807:-691757280:0402/082149:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
> [15807:-691757280:0402/082149:ERROR:CONSOLE(1)] "Uncaught ReferenceError: ntp is not defined", source:  (1)
> [15807:-691757280:0402/082153:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
>
> This is on all -current amd64 box (system and compiled ports) as of last night. I can't find any old libraries hanging around.
>
> .... Ken
>

The debug_messages size mismatches are because the tables in libstdc++
in base have fewer entries than the equivalent in libestdc++ from
ports/lang/gcc/4.6. We could sync debug_messages with libestdc++ (at
least make the size the same even if we didn't want to copy strings
verbatim from the GPLv3 version) but this would only work for one
version, there are additional entries in 4.7.

Also in this case, the plan is to switch chromium to being built with
CLang/llvm, at which point this goes away anyway.

Not sure whether the other messages are important or not..

Reply | Threaded
Open this post in threaded view
|

Re: chrome - libstc++ vs libestdc++ and other errors

Robert Nagy
On (2013-04-02 14:02), Stuart Henderson wrote:

> On 2013/04/02 08:46, Kenneth R Westerback wrote:
> > It's weird I know, but I run things from the command line. Trying out
> > chrome, I see a few odd messages:
> >
> > $ chrome &
> > [1] 15807
> > $ /usr/local/bin/chrome[17]: ulimit: bad limit: Invalid argument
> > /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> > [15807:-600466432:0402/082149:ERROR:user_style_sheet_watcher.cc(167)] Failed to setup watch for /home/krw/.config/chromium/Default/User StyleSheets/Custom.css
> > /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> > [15807:-691757280:0402/082149:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
> > [15807:-691757280:0402/082149:ERROR:CONSOLE(1)] "Uncaught ReferenceError: ntp is not defined", source:  (1)
> > [15807:-691757280:0402/082153:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
> >
> > This is on all -current amd64 box (system and compiled ports) as of last night. I can't find any old libraries hanging around.
> >
> > .... Ken
> >
>
> The debug_messages size mismatches are because the tables in libstdc++
> in base have fewer entries than the equivalent in libestdc++ from
> ports/lang/gcc/4.6. We could sync debug_messages with libestdc++ (at
> least make the size the same even if we didn't want to copy strings
> verbatim from the GPLv3 version) but this would only work for one
> version, there are additional entries in 4.7.
>
> Also in this case, the plan is to switch chromium to being built with
> CLang/llvm, at which point this goes away anyway.
>
> Not sure whether the other messages are important or not..
>

Yeah we'll switch to clang. Ignore the other messages.

Reply | Threaded
Open this post in threaded view
|

Re: chrome - libstc++ vs libestdc++ and other errors

Brad Smith-14
In reply to this post by Stuart Henderson
On Tue, Apr 02, 2013 at 02:02:59PM +0100, Stuart Henderson wrote:

> On 2013/04/02 08:46, Kenneth R Westerback wrote:
> > It's weird I know, but I run things from the command line. Trying out
> > chrome, I see a few odd messages:
> >
> > $ chrome &
> > [1] 15807
> > $ /usr/local/bin/chrome[17]: ulimit: bad limit: Invalid argument
> > /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> > [15807:-600466432:0402/082149:ERROR:user_style_sheet_watcher.cc(167)] Failed to setup watch for /home/krw/.config/chromium/Default/User StyleSheets/Custom.css
> > /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> > [15807:-691757280:0402/082149:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
> > [15807:-691757280:0402/082149:ERROR:CONSOLE(1)] "Uncaught ReferenceError: ntp is not defined", source:  (1)
> > [15807:-691757280:0402/082153:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
> >
> > This is on all -current amd64 box (system and compiled ports) as of last night. I can't find any old libraries hanging around.
> >
> > .... Ken
> >
>
> The debug_messages size mismatches are because the tables in libstdc++
> in base have fewer entries than the equivalent in libestdc++ from
> ports/lang/gcc/4.6. We could sync debug_messages with libestdc++ (at
> least make the size the same even if we didn't want to copy strings
> verbatim from the GPLv3 version) but this would only work for one
> version, there are additional entries in 4.7.
>
> Also in this case, the plan is to switch chromium to being built with
> CLang/llvm, at which point this goes away anyway.

Only until Clang is fixed to use the proper libstdc++ library.

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Reply | Threaded
Open this post in threaded view
|

Re: chrome - libstc++ vs libestdc++ and other errors

Stuart Henderson
On 2013/04/02 09:27, Brad Smith wrote:

> On Tue, Apr 02, 2013 at 02:02:59PM +0100, Stuart Henderson wrote:
> > On 2013/04/02 08:46, Kenneth R Westerback wrote:
> > > It's weird I know, but I run things from the command line. Trying out
> > > chrome, I see a few odd messages:
> > >
> > > $ chrome &
> > > [1] 15807
> > > $ /usr/local/bin/chrome[17]: ulimit: bad limit: Invalid argument
> > > /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> > > [15807:-600466432:0402/082149:ERROR:user_style_sheet_watcher.cc(167)] Failed to setup watch for /home/krw/.config/chromium/Default/User StyleSheets/Custom.css
> > > /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> > > [15807:-691757280:0402/082149:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
> > > [15807:-691757280:0402/082149:ERROR:CONSOLE(1)] "Uncaught ReferenceError: ntp is not defined", source:  (1)
> > > [15807:-691757280:0402/082153:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
> > >
> > > This is on all -current amd64 box (system and compiled ports) as of last night. I can't find any old libraries hanging around.
> > >
> > > .... Ken
> > >
> >
> > The debug_messages size mismatches are because the tables in libstdc++
> > in base have fewer entries than the equivalent in libestdc++ from
> > ports/lang/gcc/4.6. We could sync debug_messages with libestdc++ (at
> > least make the size the same even if we didn't want to copy strings
> > verbatim from the GPLv3 version) but this would only work for one
> > version, there are additional entries in 4.7.
> >
> > Also in this case, the plan is to switch chromium to being built with
> > CLang/llvm, at which point this goes away anyway.
>
> Only until Clang is fixed to use the proper libstdc++ library.

This particular one with debug_messages won't be a problem with libc++,
though there might be other issues. Although they are trying for a certain
amount of ABI compatibility..

Reply | Threaded
Open this post in threaded view
|

Re: chrome - libstc++ vs libestdc++ and other errors

Brad Smith-14
On Tue, Apr 02, 2013 at 03:03:39PM +0100, Stuart Henderson wrote:

> On 2013/04/02 09:27, Brad Smith wrote:
> > On Tue, Apr 02, 2013 at 02:02:59PM +0100, Stuart Henderson wrote:
> > > On 2013/04/02 08:46, Kenneth R Westerback wrote:
> > > > It's weird I know, but I run things from the command line. Trying out
> > > > chrome, I see a few odd messages:
> > > >
> > > > $ chrome &
> > > > [1] 15807
> > > > $ /usr/local/bin/chrome[17]: ulimit: bad limit: Invalid argument
> > > > /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> > > > [15807:-600466432:0402/082149:ERROR:user_style_sheet_watcher.cc(167)] Failed to setup watch for /home/krw/.config/chromium/Default/User StyleSheets/Custom.css
> > > > /usr/local/chrome/chrome:/usr/lib/libstdc++.so.55.0: /usr/local/lib/libestdc++.so.14.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program
> > > > [15807:-691757280:0402/082149:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
> > > > [15807:-691757280:0402/082149:ERROR:CONSOLE(1)] "Uncaught ReferenceError: ntp is not defined", source:  (1)
> > > > [15807:-691757280:0402/082153:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility()
> > > >
> > > > This is on all -current amd64 box (system and compiled ports) as of last night. I can't find any old libraries hanging around.
> > > >
> > > > .... Ken
> > > >
> > >
> > > The debug_messages size mismatches are because the tables in libstdc++
> > > in base have fewer entries than the equivalent in libestdc++ from
> > > ports/lang/gcc/4.6. We could sync debug_messages with libestdc++ (at
> > > least make the size the same even if we didn't want to copy strings
> > > verbatim from the GPLv3 version) but this would only work for one
> > > version, there are additional entries in 4.7.
> > >
> > > Also in this case, the plan is to switch chromium to being built with
> > > CLang/llvm, at which point this goes away anyway.
> >
> > Only until Clang is fixed to use the proper libstdc++ library.
>
> This particular one with debug_messages won't be a problem with libc++,
> though there might be other issues. Although they are trying for a certain
> amount of ABI compatibility..

AFAIK you can't mix the two libraries so that means then having to build
Mesa with Clang too. Plus libc++ requires xlocale support and that probably
won't happen anytime soon.

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.