On Mon, 2019-06-03 at 05:26 +0100, Ken Moffat via blfs-support wrote: > On Mon, Jun 03, 2019 at 04:57:52AM +0200, Christopher Gregory via > blfs-support wrote: > > > > > On Sun, Jun 02, 2019 at 11:16:15AM +0200, Christopher Gregory via > > > blfs-support wrote: > > > > Hello, > > > > Christopher. > > > > > > Hi Christopher, > > > > > > I hit this at the beginning of last month, at that time I was using > > > 6.2.2.2. When I got a little further, in > > > http://lists.linuxfromscratch.org/pipermail/blfs-dev/2019-May/036062.html > > > I discovered that xmlsec1 was the real problem, and has been fixed > > > in xmlsec1-1.2.28. > > > > > > But on a slightly newer build with gcc-9.1 gcc, Bruce did not have a > > > problem and nobody else chimed in. I'm currently on my 'tuning' > > > attempts (packages mostly frozen at versions from April), but when I > > > built a slightly newer system in early May I again needed to use > > > system xmlsec. > > > > > > xmlsec1-1.2.28 > > > ./configure --prefix=/usr --disable-static > > > make ; make install > > > > > > From what I wrote in that thread, there may be tests, but I have > > > not attempted to run them. > > > > > > > > > libreoffice: --with-system-xmlsec > > > > > > > > Hello Ken, > > > > That is odd on a clean build for everyone to not get the issue. This build > > I have been doing for just over a week to get blfs working. It is said by > > the same gentoo bug reporter that xml is > > indeed in part responsible, but by only editing the files as stated in the > > link, they are all icu files, and the patches are on icu's git hub account. > > So in this instance, I find myself tending > > to think that it was, at least in my case and the gentoo persnons icu to be > > the issue. I am wondering, if perhaps it might be an issue with what > > processors we are using, ie amd64. I think I > > recall other packages being prone to this in the past. > > > Not related to processors: my initial testing was on intel > (haswell). But I have no idea how many people have built > libreoffice with icu_64 on fresh systems. If people upgrade > in-place without removing all the old files, that maybe explains it.
I'll put my 2 cents in. I build a fresh system on a weekly basis and I didn't have this issue. However, I do build xmlsec separately. So my current successful clean build has libreoffice-6.2.3.2 icu-64.2 xmlsec-1.2.28 Whoever is interested, this is the configuration I use. Running ./configure with '--prefix=/usr --sysconfdir=/etc --with-vendor=BLFS --with-lang=en-GB en-US --with-help --with-myspell-dicts --without-java --without-system-dicts --disable-odk --enable- release-build=yes --enable-python=system --with-system-apr --with-system-boost --with-system-cairo --with-system-clucene --with-system-curl --with-system-expat --with-system-glm --with-system-graphite --with-system-harfbuzz --with-system-icu --with-system-jpeg --with-system-lcms2 --with-system-libatomic_ops --with-system-libpng --with-system-libxml --with-system-neon --with-system-nss --with- system-openldap --with-system-openssl --with-system-poppler --with-system-postgresql --with-system-redland --with-system-serf --with-system-zlib --with-parallelism=4 --enable-gtk3 --disable-gtk -- with-system-altlinuxhyph --with-system-coinmp --with-system-cppunit --with-system-epoxy --with-system-firebird --with-system-gpgmepp --with-system-hunspell --with-system-libabw --with-system-libcdr -- with-system-libcmis --with-system-libebook --with-system-libepubgen --with-system-libetonyek --with-system-libexttextcat --with-system-libfreehand --with-system-liblangtag --with-system-libmspub -- with-system-libmwaw --with-system-libnumbertext --with-system-libodfgen --with-system-libpagemaker --with-system-orcus --with-system-libqxp --with-system-librevenge --with-system-libstaroffice --with- system-libtommath --with-system-libvisio --with-system-libwpd --with-system-libwpg --with-system-libwps --with-system-libzmf --with-system-lpsolve --with-system-mariadb --with-system-mdds --with- system-mythes --with-system-ucpp --with-system-xmlsec --disable-fetch-external --without-fonts Notice the --disable-fetch-external parameter. Nothing is download/fetched during the build. Currently I only have to download 3 extra files to complete a successful build: pdfium-3550.tar.bz2 lxml-4.1.1.tgz 49a64f3bcf20a7909ba2751349231d6652ded9cd2840e961b5164d09de3ffa63-opens___.ttf From what I read a couple of months ago, people thought that there was a bug introduced with icu 64.x?, but it turn out not to be the case. Something to do with "extern" something or rather. (I couldn't be bothered read up on it) Regards, Wayne. > > And my reading from the eventual comment on the icu bug or pull > request was that the change to icu just papered over the problem, > and that fixing upstream xmlsec was the correct solution. But I > nearly missed that late comment when I was first looking at this. > > -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
