From nickyperian at gmail.com Fri Feb 2 11:33:22 2018 From: nickyperian at gmail.com (Nicky Perian) Date: Fri, 2 Feb 2018 13:33:22 -0600 Subject: [opensource-dev] Linux In-Reply-To: <20180126103149.a116bec1de074070573ea827@free.fr> References: <10c341cb-f350-0200-b270-a2545f29a128@lindenlab.com> <20180126013409.8919a61425a9c83137cef07b@free.fr> <20180126103149.a116bec1de074070573ea827@free.fr> Message-ID: <59A5B8E6-6DEE-4590-B845-CB85B4EA9299@gmail.com> Having read the comments on viewer-release repo and your comment concerning ABI mismatch I want to submit the following: I have put together in a VM Debian / stretch. My past linux builds have been on Ubuntu 14.04 and 16.04 using gcc-4.8 and 4.9. Stretch has neither gcc-4.9 nor libpngl2. Both of these are in wheezy. Adding wheezy to sources.list then apt-get update and apt-get install will place these in stretch then, comment out the lines about wheezy in sources.list and apt-get update again. Don?t apt-get upgrade with the wheezy lines active. Building non Alex Ivy code went fine with this setup. Ubuntu is a good choice also and has the advantage of being able to build a VM quicker. I don?t think repo commit comments is the right place to discuss future development. > On Jan 26, 2018, at 3:31 AM, Henri Beauchamp wrote: > > On Fri, 26 Jan 2018 01:34:09 +0100, Henri Beauchamp wrote: > > >> However, it might be a problem with Dullahan, since CEF is now compiled with >> Ubuntu 16.04 LTS, > > Scratch that ! > > On the CEF build Wiki, they cite 14.04, but the link points to a page that > itself points to 16.04... So, if to believe the Wiki text, Ubuntu 14.04 is > used to build the latest CEF... > > Ubuntu 14.04 uses gcc v4.8 and glibc 2.19, just like Debian Jessie (either > of those two could then be the Linux build system of choice). > > Henri. > _______________________________________________ > 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 From nickyperian at gmail.com Fri Feb 2 11:56:24 2018 From: nickyperian at gmail.com (Nicky Perian) Date: Fri, 2 Feb 2018 13:56:24 -0600 Subject: [opensource-dev] Linux In-Reply-To: <59A5B8E6-6DEE-4590-B845-CB85B4EA9299@gmail.com> References: <10c341cb-f350-0200-b270-a2545f29a128@lindenlab.com> <20180126013409.8919a61425a9c83137cef07b@free.fr> <20180126103149.a116bec1de074070573ea827@free.fr> <59A5B8E6-6DEE-4590-B845-CB85B4EA9299@gmail.com> Message-ID: <84770DBD-F8B6-4C46-B32A-A6970165E2D0@gmail.com> > Stretch has neither gcc-4.9 nor libpngl2. Both of these are in jessie. Adding wheezy to sources.list then apt-get update and apt-get install will place these in stretch then, comment out the lines about jessie in sources.list and apt-get update again. Don?t apt-get upgrade with the wheezy lines active. Building non Alex Ivy code went fine with this setup. Should be Jessie!!! > On Feb 2, 2018, at 1:33 PM, Nicky Perian wrote: > > Having read the comments on viewer-release repo and your comment concerning ABI mismatch I want to submit the following: > > I have put together in a VM Debian / stretch. My past linux builds have been on Ubuntu 14.04 and 16.04 using gcc-4.8 and 4.9. > > Stretch has neither gcc-4.9 nor libpngl2. Both of these are in wheezy. Adding wheezy to sources.list then apt-get update and apt-get install will place these in stretch then, comment out the lines about wheezy in sources.list and apt-get update again. Don?t apt-get upgrade with the wheezy lines active. Building non Alex Ivy code went fine with this setup. > > Ubuntu is a good choice also and has the advantage of being able to build a VM quicker. > > I don?t think repo commit comments is the right place to discuss future development. > > > > > > >> On Jan 26, 2018, at 3:31 AM, Henri Beauchamp wrote: >> >> On Fri, 26 Jan 2018 01:34:09 +0100, Henri Beauchamp wrote: >> >> >>> However, it might be a problem with Dullahan, since CEF is now compiled with >>> Ubuntu 16.04 LTS, >> >> Scratch that ! >> >> On the CEF build Wiki, they cite 14.04, but the link points to a page that >> itself points to 16.04... So, if to believe the Wiki text, Ubuntu 14.04 is >> used to build the latest CEF... >> >> Ubuntu 14.04 uses gcc v4.8 and glibc 2.19, just like Debian Jessie (either >> of those two could then be the Linux build system of choice). >> >> Henri. >> _______________________________________________ >> 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 > From sldev at free.fr Sat Feb 3 01:17:28 2018 From: sldev at free.fr (Henri Beauchamp) Date: Sat, 3 Feb 2018 10:17:28 +0100 Subject: [opensource-dev] Linux In-Reply-To: <59A5B8E6-6DEE-4590-B845-CB85B4EA9299@gmail.com> References: <10c341cb-f350-0200-b270-a2545f29a128@lindenlab.com> <20180126013409.8919a61425a9c83137cef07b@free.fr> <20180126103149.a116bec1de074070573ea827@free.fr> <59A5B8E6-6DEE-4590-B845-CB85B4EA9299@gmail.com> Message-ID: <20180203101728.227bf66b2a912c9b45710c3c@free.fr> On Fri, 2 Feb 2018 13:33:22 -0600, Nicky Perian wrote: > Having read the comments on viewer-release repo and your comment concerning > ABI mismatch I want to submit the following: > > I have put together in a VM Debian / stretch. My past linux builds have > been on Ubuntu 14.04 and 16.04 using gcc-4.8 and 4.9. To ensure compatibility with 4/5 years old systems (which seems to me like quite a reasonnable premise), the problem are: - Most of these systems are still using gcc v4.x (and, most important, its associated libstdc++ library using the old ABI) and all the LL-supplied libraries should therefore be compiled with either gcc v4.x (x = 7 to 9, given, alas, 4.6 is not fully C++11 compliant and cannot compile stuff like CEF), *or* have the _GLIBCXX_USE_CXX11_ABI=0 define set so that the old C++ ABI is used (the same define should then also be set in the viewer sources via the 00-Common.cmake file for gcc v5+ and clang). - The glibc version of the build system must not be too high (v2.19 looks like the newest version found on such systems). In fact, the older the glibc version, the better and the broadest the compatibility (old pre-built libraries were compatible with glibc v2.13+). - The glib v2.0 version should also be the oldest possible, since glib is used by CEF and other pre-built libraries. Using a build system with too recent a glib library would also result in missing symbols or mismatches. In fact, the gcc version matters less (thanks to the_GLIBCXX_USE_CXX11_ABI=0 trick you can use with gcc v5+ versions to retain compatibility) than the versions of *glibc* and *glib2*. Since CEF is now the most demanding library about the build system dependencies (with glibc v2.19 and glib v2.46 on the CEF build system, namely Ubuntu 14.04 LTS), I suggest we stick with those for now. FYI, the current stable release of the Cool VL Viewer builds with gcc v4.6 to v7.3 (probably with gcc v8.0 as well) and clang v3.8 to v6.0RC1 (and probably with v3.6 and 3.7 too) and the builds I release (built on a modified Rosa 2012 distro) run on pretty much any post-2012 distro. I am planning to adopt Rosa 2014.1 for my next build system (I already built Dullahan, both 32 and 64 bits on it) for the experimental Cool VL Viewer release and the next stable one. Henri. From geschaeftsstelle at afd.nrw Mon Feb 12 10:33:39 2018 From: geschaeftsstelle at afd.nrw (geschaeftsstelle at afd.nrw) Date: Mon, 12 Feb 2018 19:33:39 +0100 (CET) Subject: [opensource-dev] =?utf-8?q?=5Bviewer-development-commits=5D_commi?= =?utf-8?q?t/viewer-release=3A_28_new=09changesets?= Message-ID: <20180212183339.413F3118C893@cp.afd-hosting.de> Sehr geehrte Dame, sehr geehrter Herr, liebe Freunde der Alternative f?r Deutschland, wir danken Ihnen herzlich f?r Ihre Kontaktaufnahme und werden uns schnellstm?glich um Ihr Anliegen k?mmern. Aufgrund der hohen Zahl t?glich eingehender Anfragen bitten wir Sie um Verst?ndnis, dass die Beantwortung Ihrer Mail unter Umst?nden etwas Zeit ben?tigt. Wir bitten dies zu entschuldigen. Bei Fragen zum Programm der Alternative f?r Deutschland oder wenn Sie sich f?r aktuelle Pressemitteilungen und Ereignisse interessieren, finden Sie weiterf?hrende Informationen auf unserer Internetseite oder auf Facebook. http://afd.nrw/ und https://www.facebook.com/AfDfuerNRW/ F?r den pers?nlichen Kontakt zur Alternative f?r Deutschland bei Ihnen vor Ort sowie bei Fragen zu regionalen Veranstaltungen, k?nnen Sie sich auch an den jeweiligen Bezirksverband wenden. Kontakte dazu finden Sie auf unserer Webseite ?ber den Men?punkt "Bezirke & Kreise". Vielen herzlichen Dank f?r Ihr Interesse und Ihre Unterst?tzung unserer Arbeit. Mit freundlichen Gr??en Ihre Alternative f?r Deutschland, Landesverband Nordrhein Westfalen Landesgesch?ftsstelle AfD NRW M?nsterstra?e 306 40470 D?sseldorf From nickyperian at gmail.com Thu Feb 22 11:34:45 2018 From: nickyperian at gmail.com (Nicky Perian) Date: Thu, 22 Feb 2018 13:34:45 -0600 Subject: [opensource-dev] Libraries -- Linux Message-ID: I am in process of rebuilding all linux libraries. I had in 2015 broken apart gtk-atk-pango-glib into individual autobuild 3p type repositories. All of those have performed well in Kokua linux and linux64. I have updated and rebuilt for lack of better terminology, feeder libraries: I have an issue with fontconfig. I cannot isolate freetype from the system version and have during configure *********************************** No package 'freetype2' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables FREETYPE_CFLAGS and FREETYPE_LIBS to avoid the need to call pkg-config. ************************************************* If system package libfreetpye6-dev is present it finds it, but the system version is older than what fontconfig wants for minimum required. I have tried the export of FREETYPE_CFLAGS and FREETYPE_LIBS pointing to 3p-fontconfig/stage/packages/freetype and the same error occurs. I need some advice on how to sandbox freetype in the fontconfig build? Fyi, there is an issue for freetype linux section that is corrected by Adding: mkdir -p "$stage/include/freetype2/" cp -a include/ft2build.h "$stage/include/" cp -a include/freetype "$stage/include/freetype2/" Just before make distclean This same change was placed by Nat in the windows section. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.secondlife.com/pipermail/opensource-dev/attachments/20180222/f600d98f/attachment.htm