[chromium-discuss] Chromium using libxml from other packages?

Discussion:

a***@iiitd.ac.in

2018-09-16 06:45:20 UTC

I have been using Chromium for a long time now, and I recently installed
Vivado, on Linux. Since then, chromium fails to start, giving an error like
this:

/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/Default/libstdc++.so.6: version
`GLIBCXX_3.4.23' not found (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libavformat.so.58)
/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libavformat.so.58)
/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libavformat.so.58)
/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libbluray.so.2)
/usr/lib/chromium/chromium:
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libbluray.so.2)

It looks like Chromium is trying to use Vivado's libxml, which sounds
strange. Is there a solution to fix this problem?

P.S. This question is ported from here.
<https://www.reddit.com/r/Chromium/comments/9g8lb7/chromium_using_another_packages_libxml/> I
thought I should post this on the official channel, and I am not sure that
the reddit's sub is official.

--
--
Chromium Discussion mailing list: chromium-***@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+***@chromium.org.

Adam Rice

2018-09-17 01:32:22 UTC

Permalink

Sounds like you are using a version of Chromium from your Linux
distribution. Try running

LD_LIBRARY_PATH= /usr/bin/chromium

to locally undo any modifications Vivado may have made to your
LD_LIBRARY_PATH environment variable.

Post by a***@iiitd.ac.in
I have been using Chromium for a long time now, and I recently installed
Vivado, on Linux. Since then, chromium fails to start, giving an error like
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/Default/libstdc++.so.6: version
`GLIBCXX_3.4.23' not found (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libavformat.so.58)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libavformat.so.58)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libavformat.so.58)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libbluray.so.2)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libbluray.so.2)
It looks like Chromium is trying to use Vivado's libxml, which sounds
strange. Is there a solution to fix this problem?
P.S. This question is ported from here.
<https://www.reddit.com/r/Chromium/comments/9g8lb7/chromium_using_another_packages_libxml/> I
thought I should post this on the official channel, and I am not sure that
the reddit's sub is official.
--
--
http://groups.google.com/a/chromium.org/group/chromium-discuss

a***@iiitd.ac.in

2018-09-17 08:21:39 UTC

Permalink

I had installed Chromium from the chromium package, for Arch.

You are right. I was looking over some scripts executed by Vivado, which
involves over-writing the `LD_LIBRARY_PATH` variable.

I reset the `LD_LIBRARY_PATH` variable to `/usr/bin/chromium`, however I
wonder if that will not affect Vivado's functioning. Can I use separate
variables for each of them? Or add multiple paths with using the `:` as a
separator.

Post by Adam Rice
Sounds like you are using a version of Chromium from your Linux
distribution. Try running
LD_LIBRARY_PATH= /usr/bin/chromium
to locally undo any modifications Vivado may have made to your
LD_LIBRARY_PATH environment variable.

a***@iiitd.ac.in

2018-09-17 08:40:26 UTC

Permalink

I looked over Vivado's scripts again, and found that it was appending to
the $LD_LIBRARY_PATH variable, and not over-writing it. Even I tried to
manually over-write it, however Chromium doesn't seem to separate the paths
from the variables.

This may sound weird, but it sounds like a bug. Maybe you can try it on
your machine. Try appending to $LD_LIBRARY_PATH, and try to start chromium
on your system.

Post by a***@iiitd.ac.in
I had installed Chromium from the chromium package, for Arch.
You are right. I was looking over some scripts executed by Vivado, which
involves over-writing the `LD_LIBRARY_PATH` variable.
I reset the `LD_LIBRARY_PATH` variable to `/usr/bin/chromium`, however I
wonder if that will not affect Vivado's functioning. Can I use separate
variables for each of them? Or add multiple paths with using the `:` as a
separator.

Adam Rice

2018-09-19 23:50:57 UTC

Permalink

I think obeying LD_LIBRARY_PATH is the intended behaviour, as that is how
other software behaves and it can be useful in some scenarios.

Instead of changing LD_LIBRARY_PATH globally, you can change it only when
you run Chrome by setting an empty value on the command-line, like this

LD_LIBRARY_PATH="" chromium

Probably if you change LD_LIBRARY_PATH globally, Vivado will stop working.

Post by a***@iiitd.ac.in
I looked over Vivado's scripts again, and found that it was appending to
the $LD_LIBRARY_PATH variable, and not over-writing it. Even I tried to
manually over-write it, however Chromium doesn't seem to separate the paths
from the variables.
This may sound weird, but it sounds like a bug. Maybe you can try it on
your machine. Try appending to $LD_LIBRARY_PATH, and try to start chromium
on your system.

Post by a***@iiitd.ac.in
I have been using Chromium for a long time now, and I recently
installed Vivado, on Linux. Since then, chromium fails to start, giving an
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/Default/libstdc++.so.6: version
`GLIBCXX_3.4.23' not found (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/chromium/chromium)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libavformat.so.58)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libavformat.so.58)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libavformat.so.58)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libbluray.so.2)
/opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information
available (required by /usr/lib/libbluray.so.2)
It looks like Chromium is trying to use Vivado's libxml, which sounds
strange. Is there a solution to fix this problem?
P.S. This question is ported from here.
<https://www.reddit.com/r/Chromium/comments/9g8lb7/chromium_using_another_packages_libxml/> I
thought I should post this on the official channel, and I am not sure that
the reddit's sub is official.
--
--
http://groups.google.com/a/chromium.org/group/chromium-discuss
--

--
http://groups.google.com/a/chromium.org/group/chromium-discuss

a***@iiitd.ac.in

2018-09-20 09:43:56 UTC

Permalink

That's not what I meant, though. I am changing the variable locally, when I
execute chromium.

However, my doubt was that shouldn't chromium look for it's own libxml path
in the LD_LIBRARY_PATH (which is separated by a ':' delimiter)? Just like
the $PATH variable, it should extract the required path from the variable
value.

Please excuse me, if am being buggy (no pun), but I am just curious about
this new thing.

Post by Adam Rice
I think obeying LD_LIBRARY_PATH is the intended behaviour, as that is how
other software behaves and it can be useful in some scenarios.
Instead of changing LD_LIBRARY_PATH globally, you can change it only when
you run Chrome by setting an empty value on the command-line, like this
LD_LIBRARY_PATH="" chromium
Probably if you change LD_LIBRARY_PATH globally, Vivado will stop working.

--
http://groups.google.com/a/chromium.org/group/chromium-discuss

Adam Rice

2018-09-21 07:09:31 UTC

Permalink

Post by a***@iiitd.ac.in
However, my doubt was that shouldn't chromium look for it's own libxml
path in the LD_LIBRARY_PATH (which is separated by a ':' delimiter)?

It will load the first libxml it sees, scanning LD_LIBRARY_PATH from left
to right.

Post by a***@iiitd.ac.in
That's not what I meant, though. I am changing the variable locally, when
I execute chromium.
However, my doubt was that shouldn't chromium look for it's own libxml
path in the LD_LIBRARY_PATH (which is separated by a ':' delimiter)? Just
like the $PATH variable, it should extract the required path from the
variable value.
Please excuse me, if am being buggy (no pun), but I am just curious about
this new thing.

Post by a***@iiitd.ac.in
I had installed Chromium from the chromium package, for Arch.
You are right. I was looking over some scripts executed by Vivado,
which involves over-writing the `LD_LIBRARY_PATH` variable.
I reset the `LD_LIBRARY_PATH` variable to `/usr/bin/chromium`, however
I wonder if that will not affect Vivado's functioning. Can I use separate
variables for each of them? Or add multiple paths with using the `:` as a
separator.

--
http://groups.google.com/a/chromium.org/group/chromium-discuss
--

--
http://groups.google.com/a/chromium.org/group/chromium-discuss