version changed drastically at some point
or has someone gone and ripped out the guts for linux syslib version
(ie: lots of things now missing in various cmake files etc)?
Would appreciate any insight people may have.
--
Kind Regards,
Alex.
___
Policies an
: LLPluginInstance::load: apr_dso_load of
/home/alex/fsivy/bin/llplugin/libmedia_plugin_cef.so failed with error
20019 , additional info string:
/home/alex/fsivy/bin/llplugin/libmedia_plugin_cef.so: undefined symbol:
AtomicOps_Internalx86CPUFeatures
Some Googling reveals that
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting
> privileges
Hi Henri!
Thank you for responding.
This is what I get:
alex@desktop:~/ivyviewer$ LD_LIBRARY_PATH="./lib:$LD_LIBRARY_PATH" ldd
./bin/llp
> Hi Henri!
>
> Thank you for responding.
>
> This is what I get:
> alex@desktop:~/ivyviewer$ LD_LIBRARY_PATH="./lib:$LD_LIBRARY_PATH" ldd
> ./bin/llplugin/libmedia_plugin_cef.so
> linux-vdso.so.1 => (0x7ffcedd68000)
> librt.
t cmake file and that
section was wrong (and missing things). I'll try another rebuild with
that. I have a feeling thats going to fix it! Now how can I send you a
nice bottle of wine? :D
Thank you so much! appreciate it!
--
Kind Regards,
Alex.
_
now.
2018-03-20T11:53:39Z WARNING: LLPluginInstance::load: apr_dso_load of
/home/alex/ivyviewer/bin/llplugin/libmedia_plugin_cef.so failed with
error 20019 , additional info string:
/home/alex/ivyviewer/bin/llplugin/libmedia_plugin_cef.so: undefined
symbol: _ZN8dullahan26setOnStatusMessageCal
On 2018-03-20 22:00, Alex wrote:
> 2018-03-20T11:53:39Z WARNING: LLPluginInstance::load: apr_dso_load of
> /home/alex/ivyviewer/bin/llplugin/libmedia_plugin_cef.so failed with
> error 20019 , additional info string:
> /home/alex/ivyviewer/bin/llplugin/libmedia_plugin_cef.so: undefi
s://pastebin.com/ZhytizN8 (indra/media_plugins/cef/CMakeLists.txt)
--
Kind Regards,
Alex.
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges
On 2018-03-20 23:15, Henri Beauchamp wrote:
> What is your Linux build system ?
Ubuntu 17.10 64 bit
gcc/g++ version 4.9.4
GNU ld (GNU Binutils for Ubuntu) 2.29.1
--
Kind Regards,
Alex.
___
Policies and (un)subscribe information available here:
h
above :)
I'll try the trick with linking libcef twice and see what happens :)
Thank you :)
--
Kind Regards,
Alex.
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the poli
But in the case of boost and dullahan, it was making use of header
only parts of boost right?
Relinking libcef twice didnt help sadly.. I gave up for the night and
went to sleep hehe. Do you have any ideas what else might be causing it?
:)
Interesting that that symbol
On 2018-03-21 07:57, monty wrote:
> On 3/20/2018 17:32, Alex wrote:
>>
>> Interesting that that symbol is defined 3 times in your library.
>>
>
> 'nm' that thing and see what is definition and what is reference.
I pasted the result here:
https://pastebin.c
:0011ecf0 T
_ZN25dullahan_callback_manager26setOnStatusMessageCallbackESt8functionIFvSsEE
libmedia_plugin_cef.so:00114cd0 T
_ZN8dullahan26setOnStatusMessageCallbackEN5boost8functionIFvSsEEE
libmedia_plugin_cef.so: U
_ZN8dullahan26setOnStatusMessageCallbackESt8functionIFvSsEE
--
gin_cef.so: U
dullahan::setOnStatusMessageCallback(std::function)
A lot easier to read.
Would this suggest that the libdullahan.a library itself I am trying to
link against is fine and there is a problem with the viewer build
configuration somewh
)
Just a quick question about the above. In the list for
target_link_libraries, the first two make sense to me, but what is 'cef'
referring to? is it libcef.so?
--
Kind Regards,
Alex.
___
Policies and (un)subscribe information available here:
h
meter is
being sent that obviously is not numeric and throwing the error.
I ran the viewer under strace and observed some interesting behavior:
4589 execve("/home/alex/ivyviewer/bin/SLPlugin",
["/home/alex/ivyviewer/bin/SLPlugin", "38655"], [/ 66 vars /]
4592
t, you are right. I have no idea why the
viewer would be doing that. From what I am aware, the viewer _should_
start one instance of SLPlugin and dullahan_host when its at the login
screen.
Do you have a rough idea (assuming the standard LL viewer behavior)
where these processes get launched fr
On 2018-03-23 02:00, Henri Beauchamp wrote:
> On Fri, 23 Mar 2018 01:48:08 +1000, Alex wrote:
>
>> It does indeed sound like the viewer is subsequently spawning another
>> SLPlugin instead of dullahan_host, you are right. I have no idea why
>> the
>> viewer would
On 2018-03-23 02:00, Henri Beauchamp wrote:
> #elif defined(__linux__)
> CefString(&settings.browser_subprocess_path) = "dullahan_host";
> #endif
>
>
> Henri.
Well that certainly got me further! Thank you! Its' at least _trying_ to
start dullahan_host
iles
> matching as possible.
> ___
I was able to clone the source for this and build the package on linux
with not much effort. Easy enough from there to edit autobuild.xml and
point it at your own package.
-
lting package had correct dependencies. package:
fontconfig-2.11.0-linux64-314281.tar.bz2
--
Kind Regards,
Alex.
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before po
-0.0.1-linux-317266.tar.bz2
to
/var/tmp/alex/install.cache/llappearance_utility-0.0.1-linux-317266.tar.bz2
error: HTTP Error 401: Unauthorized
Is this actually needed? If I grep through the sources, I find only
linux references to llappearanceutility - nothing for windows, mac..
And for
On 2018-08-09 06:25, Cinder Roxley wrote:
> autobuild configure -c ReleaseOS You are building with the proprietary libs.
> You need to build an opensource autobuild target:
> ___
Ty :)
Is there a way to have the viewer use FMOD by default instead of
lab.com | Scott Lawrence [1]
> LINDEN LAB | Create Virtual Experiences [2]
> ___
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting privileges
Hi Guys,
This question is directed at the Lab.
Python 2.7 becomes EOL as of Jan 1st 2020. Which is not far away.
Is there any work underway to make autobuild compatible with Python 3?
--
Kind Regards,
Alex.
___
Policies and (un)subscribe information
Hi!
Regarding FreeBSD..
You will not get this to work on FreeBSD without an absolute buttload of
work.. For starters, autobuild would not recognize FreeBSD as a valid
platform, you would need to hack it to support FreeBSD (or write your
own build system).
Many things would also be missing a
On 2020-02-07 20:52, Henri Beauchamp wrote:
> [rant]
> You can thank LL for not providing support for Linux; while they
> benefit
> for free from all the work done by GNU/Linux developers and while SL
> won't even exist without their work (especially on the server side of
> things, but even the vi
27 matches
Mail list logo
