Re: [blfs-dev] libreoffice-7 wants clang
On Mon, 31 Aug 2020 21:34:06 -0500 Ken Moffat via blfs-dev wrote: > On Tue, Sep 01, 2020 at 02:03:18AM +0100, Ken Moffat via blfs-dev wrote: > > On Tue, Sep 01, 2020 at 12:25:55AM +0200, Uwe Düffert wrote: > > > Hi, > > > > > > On Mon, 31 Aug 2020, Ken Moffat via blfs-dev wrote: > > > > > > > [...] > > > > using make V=1. Unfortunately, that no-longer gives a verbose build > > > > [...] > > > > If anyone knows how to get libreoffice-7 (or late 6) to show the > > > > commands it is running, please speak up! > > > *checkin*... My last build was libreoffice-7.0.0.3 and the log looks > > > rather > > > complete to me. Can't say when I started with that, must be quite some > > > time > > > ago, but I'm using: > > > > > > make verbose=true build-nocheck > > > > > > > > > Uwe > > > > Thanks, I'll start over on trying to work out what changes > > with/without clang. > > > > ĸen > > Decided to run autogen both with and without the --disable-skia. In > libreoffice-7.0.0.3/config_host.mk there are various differences, > and in particular the output for the Skia test - > > configure:36795: checking whether to build Skia > -configure:36804: result: yes > -configure:36855: checking for clang > -configure:36871: found /usr/bin/clang > -configure:36882: result: clang > [snip most of remaining clang/clang++ tests] > -configure:37243: checking whether clang++ can compile FMA intrinsics > -configure:37264: clang++ -c -mfma conftest.cpp >&5 > -configure:37264: $? = 0 > -configure:37277: result: yes > +configure:36813: result: no > > So from that it is clear that the Warning about missing clang is > accompanied by disabling Skia. > > Will work through the builds to see if I can confirm exactly what > differs when Skia is enabled. > > ĸen > -- > I could not live without Champagne. In victory I deserve it, in > defeat I need it. -- Churchill > -- > http://lists.linuxfromscratch.org/listinfo/blfs-dev > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page I think you may find that with clang absent and not --disable-skia, Skia is not disabled but as the build documentation I referenced earlier says, it falls back to unoptimized paths. If you were to force --disable-skia then I would guess it falls back to using Cairo as it did prior to libreoffice 7. The clang test is looking for "FMA intrinsics" which would speed up fused-multiply-add in the clang-present case. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] libreoffice-7 wants clang
On Tue, Sep 01, 2020 at 02:03:18AM +0100, Ken Moffat via blfs-dev wrote: > On Tue, Sep 01, 2020 at 12:25:55AM +0200, Uwe Düffert wrote: > > Hi, > > > > On Mon, 31 Aug 2020, Ken Moffat via blfs-dev wrote: > > > > > [...] > > > using make V=1. Unfortunately, that no-longer gives a verbose build > > > [...] > > > If anyone knows how to get libreoffice-7 (or late 6) to show the > > > commands it is running, please speak up! > > *checkin*... My last build was libreoffice-7.0.0.3 and the log looks rather > > complete to me. Can't say when I started with that, must be quite some time > > ago, but I'm using: > > > > make verbose=true build-nocheck > > > > > > Uwe > > Thanks, I'll start over on trying to work out what changes > with/without clang. > > ĸen Decided to run autogen both with and without the --disable-skia. In libreoffice-7.0.0.3/config_host.mk there are various differences, and in particular the output for the Skia test - configure:36795: checking whether to build Skia -configure:36804: result: yes -configure:36855: checking for clang -configure:36871: found /usr/bin/clang -configure:36882: result: clang [snip most of remaining clang/clang++ tests] -configure:37243: checking whether clang++ can compile FMA intrinsics -configure:37264: clang++ -c -mfma conftest.cpp >&5 -configure:37264: $? = 0 -configure:37277: result: yes +configure:36813: result: no So from that it is clear that the Warning about missing clang is accompanied by disabling Skia. Will work through the builds to see if I can confirm exactly what differs when Skia is enabled. ĸen -- I could not live without Champagne. In victory I deserve it, in defeat I need it. -- Churchill -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] libreoffice-7 wants clang
On Tue, Sep 01, 2020 at 12:25:55AM +0200, Uwe Düffert wrote: > Hi, > > On Mon, 31 Aug 2020, Ken Moffat via blfs-dev wrote: > > > [...] > > using make V=1. Unfortunately, that no-longer gives a verbose build > > [...] > > If anyone knows how to get libreoffice-7 (or late 6) to show the > > commands it is running, please speak up! > *checkin*... My last build was libreoffice-7.0.0.3 and the log looks rather > complete to me. Can't say when I started with that, must be quite some time > ago, but I'm using: > > make verbose=true build-nocheck > > > Uwe Thanks, I'll start over on trying to work out what changes with/without clang. ĸen -- I could not live without Champagne. In victory I deserve it, in defeat I need it. -- Churchill -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] libreoffice-7 wants clang
On Mon, 31 Aug 2020 18:52:35 -0500 Ken Moffat via blfs-dev wrote: > On Mon, Aug 31, 2020 at 10:32:05PM +0100, Ken Moffat via blfs-dev > wrote: > > On Mon, Aug 31, 2020 at 07:17:30PM +0100, Ken Moffat via blfs-dev > > wrote: > > > On Mon, Aug 31, 2020 at 08:04:37AM -0500, Marty Jack via > > > blfs-dev wrote: > > > > > > > > > > > > On Mon, 31 Aug 2020 01:44:03 -0500 Ken Moffat via blfs-dev > > > > wrote: > > > > > On Mon, Aug 31, 2020 at 06:48:47AM +0100, Ken Moffat via > > > > > blfs-dev wrote: > > > > > > > > > > Changing the title ecause this is a separate issue. > > > > > > > > > > > > Oh - tried updating libreoffice on another machine: with > > > > > > the skia code it defaults to using clang (and my CFLAGS, > > > > > > CXXFLAGS have -fstack-clash-protection which clang-10 does > > > > > > not understand). > > > > > > > > > > > > ĸen > > > > > > > > > > Nope, it still uses clang, which eventually fails: > > > > > > > > > > clang-10: error: unknown argument: > > > > > '-fstack-clash-protection' clang-10: error: unsupported > > > > > argument '8' to option 'flto=' > > > > > > > > > > I'm guessing clang generated flto=8 (an 8-thread machine) > > > > > and got confused by the previous unsupproted switch. > > > > > > > > > > https://www.phoronix.com/scan.php?page=news_item=LibreOffice-7.0-Prefers-Clang > > > > > > > > > > Oddly, Arch (libreoffice-fresh) do not seem to list clang or > > > > > even llvm as deps. > > > > > > > > > > Fedora are using --disable-skia which might work around > > > > > this. I'll try that for my own builds, which are a bt less > > > > > than the book (e,g, no java) but I think we'll need to make > > > > > clang required in the book. > > > > > > > [...] > > > > > > > > I build libreoffice 7 with gcc and without clang, which I do > > > > not have installed. I also do not have skia installed. It > > > > generates > > > > > > > > checking whether to build Skia... yes checking for clang... no > > > > configure: WARNING: Clang compiler not found. > > > > > > > > Takes about an hour on my i5-8600 for make build-nocheck. > > > > Clearly they may change this in future but this suggests that > > > > clang need not be required by the book. > > > > > > Hmm. Technically it is 'Recommended'. All my systems do have > > > clang and I don'y have a log from the failed build, all I know > > > for certain is that it tried to use clang when building skia, > > > and failed because clang does not (in current release) support > > > my flags. > > > > > > I'm guessing that your log can be interpreted as should I build > > > skia : yes (default) do you have clang : no ok, cannot build > > > skia, issue a warning. > > > > > > > I've just done a fresh build (omitting e.g. java, openldap, > > gssapi, krb5 which I have not installed) and using make V=1. > > Unfortunately, that no-longer gives a verbose build so I'm none > > the wiser about what actually got compiled. > > > > If anyone knows how to get libreoffice-7 (or late 6) to show the > > commands it is running, please speak up! > > > > Meanwhile, I've just started a build after hiding all the clang* > > files in /usr/bin. Not sure it will show anything. > > Unfortunately, there seems to be a reluctance in some build > > systems (e.g. typical python modules) to provide real verbose > > output. > > > Completed, the only apparent difference in the logs is timings/dates > in downloads, and some items get built at a different place which is > probably just random variation on a machine where I've got a desktop > with various open terms and browsers. > > In the output from autogen, it definitely could not now find clang, > so in that sense my build without clang matched yours: > > --- LO-logs-with-clang/mylog-autogen2020-08-31 19:51:55.335992586 +0100 > +++ LO-logs-no-clang/mylog-autogen 2020-09-01 00:26:15.004670799 +0100 > @@ -386,16 +386,9 @@ > checking cpp/poppler-version.h presence... yes > checking for cpp/poppler-version.h... yes > checking whether to build Skia... yes > -checking for clang... clang > -checking for clang++... clang++ > -checking whether clang++ can compile SSE2 intrinsics... yes > -checking whether clang++ can compile SSSE3 intrinsics... yes > -checking whether clang++ can compile SSE4.1 intrinsics... yes > -checking whether clang++ can compile SSE4.2 intrinsics... yes > -checking whether clang++ can compile AVX intrinsics... yes > -checking whether clang++ can compile AVX2 intrinsics... yes > -checking whether clang++ can compile F16C intrinsics... yes > -checking whether clang++ can compile FMA intrinsics... yes > +checking for clang... no > +checking for clang++... no > +configure: WARNING: Clang compiler not found. > checking which gpgmepp to use... external > checking gpgme++/gpgmepp_version.h usability... yes > checking gpgme++/gpgmepp_version.h presence... yes > > > Based on the report from phoronix, and my own failure because clang > rejected one of my flags, I think that clang is
Re: [blfs-dev] libreoffice-7 wants clang
On Mon, 31 Aug 2020 18:52:35 -0500 Ken Moffat via blfs-dev wrote: > On Mon, Aug 31, 2020 at 10:32:05PM +0100, Ken Moffat via blfs-dev > wrote: > > On Mon, Aug 31, 2020 at 07:17:30PM +0100, Ken Moffat via blfs-dev > > wrote: > > > On Mon, Aug 31, 2020 at 08:04:37AM -0500, Marty Jack via > > > blfs-dev wrote: > > > > > > > > > > > > On Mon, 31 Aug 2020 01:44:03 -0500 Ken Moffat via blfs-dev > > > > wrote: > > > > > On Mon, Aug 31, 2020 at 06:48:47AM +0100, Ken Moffat via > > > > > blfs-dev wrote: > > > > > > > > > > Changing the title ecause this is a separate issue. > > > > > > > > > > > > Oh - tried updating libreoffice on another machine: with > > > > > > the skia code it defaults to using clang (and my CFLAGS, > > > > > > CXXFLAGS have -fstack-clash-protection which clang-10 does > > > > > > not understand). > > > > > > > > > > > > ĸen > > > > > > > > > > Nope, it still uses clang, which eventually fails: > > > > > > > > > > clang-10: error: unknown argument: > > > > > '-fstack-clash-protection' clang-10: error: unsupported > > > > > argument '8' to option 'flto=' > > > > > > > > > > I'm guessing clang generated flto=8 (an 8-thread machine) > > > > > and got confused by the previous unsupproted switch. > > > > > > > > > > https://www.phoronix.com/scan.php?page=news_item=LibreOffice-7.0-Prefers-Clang > > > > > > > > > > Oddly, Arch (libreoffice-fresh) do not seem to list clang or > > > > > even llvm as deps. > > > > > > > > > > Fedora are using --disable-skia which might work around > > > > > this. I'll try that for my own builds, which are a bt less > > > > > than the book (e,g, no java) but I think we'll need to make > > > > > clang required in the book. > > > > > > > [...] > > > > > > > > I build libreoffice 7 with gcc and without clang, which I do > > > > not have installed. I also do not have skia installed. It > > > > generates > > > > > > > > checking whether to build Skia... yes checking for clang... no > > > > configure: WARNING: Clang compiler not found. > > > > > > > > Takes about an hour on my i5-8600 for make build-nocheck. > > > > Clearly they may change this in future but this suggests that > > > > clang need not be required by the book. > > > > > > Hmm. Technically it is 'Recommended'. All my systems do have > > > clang and I don'y have a log from the failed build, all I know > > > for certain is that it tried to use clang when building skia, > > > and failed because clang does not (in current release) support > > > my flags. > > > > > > I'm guessing that your log can be interpreted as should I build > > > skia : yes (default) do you have clang : no ok, cannot build > > > skia, issue a warning. > > > > > > > I've just done a fresh build (omitting e.g. java, openldap, > > gssapi, krb5 which I have not installed) and using make V=1. > > Unfortunately, that no-longer gives a verbose build so I'm none > > the wiser about what actually got compiled. > > > > If anyone knows how to get libreoffice-7 (or late 6) to show the > > commands it is running, please speak up! > > > > Meanwhile, I've just started a build after hiding all the clang* > > files in /usr/bin. Not sure it will show anything. > > Unfortunately, there seems to be a reluctance in some build > > systems (e.g. typical python modules) to provide real verbose > > output. > > > Completed, the only apparent difference in the logs is timings/dates > in downloads, and some items get built at a different place which is > probably just random variation on a machine where I've got a desktop > with various open terms and browsers. > > In the output from autogen, it definitely could not now find clang, > so in that sense my build without clang matched yours: > > --- LO-logs-with-clang/mylog-autogen2020-08-31 19:51:55.335992586 +0100 > +++ LO-logs-no-clang/mylog-autogen 2020-09-01 00:26:15.004670799 +0100 > @@ -386,16 +386,9 @@ > checking cpp/poppler-version.h presence... yes > checking for cpp/poppler-version.h... yes > checking whether to build Skia... yes > -checking for clang... clang > -checking for clang++... clang++ > -checking whether clang++ can compile SSE2 intrinsics... yes > -checking whether clang++ can compile SSSE3 intrinsics... yes > -checking whether clang++ can compile SSE4.1 intrinsics... yes > -checking whether clang++ can compile SSE4.2 intrinsics... yes > -checking whether clang++ can compile AVX intrinsics... yes > -checking whether clang++ can compile AVX2 intrinsics... yes > -checking whether clang++ can compile F16C intrinsics... yes > -checking whether clang++ can compile FMA intrinsics... yes > +checking for clang... no > +checking for clang++... no > +configure: WARNING: Clang compiler not found. > checking which gpgmepp to use... external > checking gpgme++/gpgmepp_version.h usability... yes > checking gpgme++/gpgmepp_version.h presence... yes > > > Based on the report from phoronix, and my own failure because clang > rejected one of my flags, I think that clang is
Re: [blfs-dev] libreoffice-7 wants clang
On Mon, Aug 31, 2020 at 10:32:05PM +0100, Ken Moffat via blfs-dev wrote: > On Mon, Aug 31, 2020 at 07:17:30PM +0100, Ken Moffat via blfs-dev > wrote: > > On Mon, Aug 31, 2020 at 08:04:37AM -0500, Marty Jack via > > blfs-dev wrote: > > > > > > > > > On Mon, 31 Aug 2020 01:44:03 -0500 Ken Moffat via blfs-dev > > > wrote: > > > > On Mon, Aug 31, 2020 at 06:48:47AM +0100, Ken Moffat via > > > > blfs-dev wrote: > > > > > > > > Changing the title ecause this is a separate issue. > > > > > > > > > > Oh - tried updating libreoffice on another machine: with > > > > > the skia code it defaults to using clang (and my CFLAGS, > > > > > CXXFLAGS have -fstack-clash-protection which clang-10 does > > > > > not understand). > > > > > > > > > > ĸen > > > > > > > > Nope, it still uses clang, which eventually fails: > > > > > > > > clang-10: error: unknown argument: > > > > '-fstack-clash-protection' clang-10: error: unsupported > > > > argument '8' to option 'flto=' > > > > > > > > I'm guessing clang generated flto=8 (an 8-thread machine) > > > > and got confused by the previous unsupproted switch. > > > > > > > > https://www.phoronix.com/scan.php?page=news_item=LibreOffice-7.0-Prefers-Clang > > > > > > > > Oddly, Arch (libreoffice-fresh) do not seem to list clang or > > > > even llvm as deps. > > > > > > > > Fedora are using --disable-skia which might work around > > > > this. I'll try that for my own builds, which are a bt less > > > > than the book (e,g, no java) but I think we'll need to make > > > > clang required in the book. > > > > > [...] > > > > > > I build libreoffice 7 with gcc and without clang, which I do > > > not have installed. I also do not have skia installed. It > > > generates > > > > > > checking whether to build Skia... yes checking for clang... no > > > configure: WARNING: Clang compiler not found. > > > > > > Takes about an hour on my i5-8600 for make build-nocheck. > > > Clearly they may change this in future but this suggests that > > > clang need not be required by the book. > > > > Hmm. Technically it is 'Recommended'. All my systems do have > > clang and I don'y have a log from the failed build, all I know > > for certain is that it tried to use clang when building skia, > > and failed because clang does not (in current release) support > > my flags. > > > > I'm guessing that your log can be interpreted as should I build > > skia : yes (default) do you have clang : no ok, cannot build > > skia, issue a warning. > > > > I've just done a fresh build (omitting e.g. java, openldap, > gssapi, krb5 which I have not installed) and using make V=1. > Unfortunately, that no-longer gives a verbose build so I'm none > the wiser about what actually got compiled. > > If anyone knows how to get libreoffice-7 (or late 6) to show the > commands it is running, please speak up! > > Meanwhile, I've just started a build after hiding all the clang* > files in /usr/bin. Not sure it will show anything. > Unfortunately, there seems to be a reluctance in some build > systems (e.g. typical python modules) to provide real verbose > output. > Completed, the only apparent difference in the logs is timings/dates in downloads, and some items get built at a different place which is probably just random variation on a machine where I've got a desktop with various open terms and browsers. In the output from autogen, it definitely could not now find clang, so in that sense my build without clang matched yours: --- LO-logs-with-clang/mylog-autogen2020-08-31 19:51:55.335992586 +0100 +++ LO-logs-no-clang/mylog-autogen 2020-09-01 00:26:15.004670799 +0100 @@ -386,16 +386,9 @@ checking cpp/poppler-version.h presence... yes checking for cpp/poppler-version.h... yes checking whether to build Skia... yes -checking for clang... clang -checking for clang++... clang++ -checking whether clang++ can compile SSE2 intrinsics... yes -checking whether clang++ can compile SSSE3 intrinsics... yes -checking whether clang++ can compile SSE4.1 intrinsics... yes -checking whether clang++ can compile SSE4.2 intrinsics... yes -checking whether clang++ can compile AVX intrinsics... yes -checking whether clang++ can compile AVX2 intrinsics... yes -checking whether clang++ can compile F16C intrinsics... yes -checking whether clang++ can compile FMA intrinsics... yes +checking for clang... no +checking for clang++... no +configure: WARNING: Clang compiler not found. checking which gpgmepp to use... external checking gpgme++/gpgmepp_version.h usability... yes checking gpgme++/gpgmepp_version.h presence... yes Based on the report from phoronix, and my own failure because clang rejected one of my flags, I think that clang is intended to be used (i.e. recommended), but I'm now less clear on the consequences of using --disable-skia. Certainly it prevents clang being used if it is present. ĸen -- I could not live without Champagne. In victory I deserve it, in defeat I need it. -- Churchill --
Re: [blfs-dev] libreoffice-7 wants clang
Hi, On Mon, 31 Aug 2020, Ken Moffat via blfs-dev wrote: [...] using make V=1. Unfortunately, that no-longer gives a verbose build [...] If anyone knows how to get libreoffice-7 (or late 6) to show the commands it is running, please speak up! *checkin*... My last build was libreoffice-7.0.0.3 and the log looks rather complete to me. Can't say when I started with that, must be quite some time ago, but I'm using: make verbose=true build-nocheck Uwe -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Fwd: Plasma-wayland-protocols install path
I've been struggling to get kf5 plasma-framework-5.73.0 to compile and in my troubleshooting I came across the fact that plasma-wayland-protocols is hard coded to use /usr as the install prefix, but the installed directories shows it as $KF5_PREFIX/share/plasma-wayland-protocols. the cmake line needs to be cmake -DCMAKE_INSTALL_PREFIX=$KF5_PREFIX .. This didn't fix the problem I'm having with plasma-framework-5.73.0 though, which turned out to be some libraries in /usr/lib64 instead of /usr/lib. I'm not sure how many of us are using KDE on LFS, but everytime I've tried to use build KDE I've run into tons of issues. xfce and even mate work great, Gnome is a little painful, but KDE is a huge pain to get working, and then it never seems quite right. Has anyone got KDEconnect to work with LFS? Thanks, Tim Russo -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] libreoffice-7 wants clang
On Mon, Aug 31, 2020 at 07:17:30PM +0100, Ken Moffat via blfs-dev wrote: > On Mon, Aug 31, 2020 at 08:04:37AM -0500, Marty Jack via blfs-dev wrote: > > > > > > On Mon, 31 Aug 2020 01:44:03 -0500 Ken Moffat via blfs-dev wrote: > > > On Mon, Aug 31, 2020 at 06:48:47AM +0100, Ken Moffat via blfs-dev wrote: > > > > > > Changing the title ecause this is a separate issue. > > > > > > > > Oh - tried updating libreoffice on another machine: with the skia > > > > code it defaults to using clang (and my CFLAGS, CXXFLAGS have > > > > -fstack-clash-protection which clang-10 does not understand). > > > > > > > > ĸen > > > > > > Nope, it still uses clang, which eventually fails: > > > > > > clang-10: error: unknown argument: '-fstack-clash-protection' > > > clang-10: error: unsupported argument '8' to option 'flto=' > > > > > > I'm guessing clang generated flto=8 (an 8-thread machine) and got > > > confused by the previous unsupproted switch. > > > > > > https://www.phoronix.com/scan.php?page=news_item=LibreOffice-7.0-Prefers-Clang > > > > > > Oddly, Arch (libreoffice-fresh) do not seem to list clang or even > > > llvm as deps. > > > > > > Fedora are using --disable-skia which might work around this. I'll > > > try that for my own builds, which are a bt less than the book (e,g, no > > > java) but I think we'll need to make clang required in the book. > > > [...] > > > > I build libreoffice 7 with gcc and without clang, which I do not have > > installed. I also do not have skia installed. > > It generates > > > > checking whether to build Skia... yes > > checking for clang... no > > configure: WARNING: Clang compiler not found. > > > > Takes about an hour on my i5-8600 for make build-nocheck. > > Clearly they may change this in future but this suggests that clang need > > not be required by the book. > > Hmm. Technically it is 'Recommended'. All my systems do have clang > and I don'y have a log from the failed build, all I know for certain > is that it tried to use clang when building skia, and failed because > clang does not (in current release) support my flags. > > I'm guessing that your log can be interpreted as > should I build skia : yes (default) > do you have clang : no > ok, cannot build skia, issue a warning. > I've just done a fresh build (omitting e.g. java, openldap, gssapi, krb5 which I have not installed) and using make V=1. Unfortunately, that no-longer gives a verbose build so I'm none the wiser about what actually got compiled. If anyone knows how to get libreoffice-7 (or late 6) to show the commands it is running, please speak up! Meanwhile, I've just started a build after hiding all the clang* files in /usr/bin. Not sure it will show anything. Unfortunately, there seems to be a reluctance in some build systems (e.g. typical python modules) to provide real verbose output. ĸen -- Juliet's version of cleanliness was next to godliness, which was to say it was erratic, past all understanding and was seldom seen. -- Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] libreoffice-7 wants clang
On Mon, Aug 31, 2020 at 08:04:37AM -0500, Marty Jack via blfs-dev wrote: > > > On Mon, 31 Aug 2020 01:44:03 -0500 Ken Moffat via blfs-dev wrote: > > On Mon, Aug 31, 2020 at 06:48:47AM +0100, Ken Moffat via blfs-dev wrote: > > > > Changing the title ecause this is a separate issue. > > > > > > Oh - tried updating libreoffice on another machine: with the skia > > > code it defaults to using clang (and my CFLAGS, CXXFLAGS have > > > -fstack-clash-protection which clang-10 does not understand). > > > > > > ĸen > > > > Nope, it still uses clang, which eventually fails: > > > > clang-10: error: unknown argument: '-fstack-clash-protection' > > clang-10: error: unsupported argument '8' to option 'flto=' > > > > I'm guessing clang generated flto=8 (an 8-thread machine) and got > > confused by the previous unsupproted switch. > > > > https://www.phoronix.com/scan.php?page=news_item=LibreOffice-7.0-Prefers-Clang > > > > Oddly, Arch (libreoffice-fresh) do not seem to list clang or even > > llvm as deps. > > > > Fedora are using --disable-skia which might work around this. I'll > > try that for my own builds, which are a bt less than the book (e,g, no > > java) but I think we'll need to make clang required in the book. > > > > ĸen > > -- > > Juliet's version of cleanliness was next to godliness, which was to > > say it was erratic, past all understanding and was seldom seen. > > -- Unseen Academicals > > -- > > http://lists.linuxfromscratch.org/listinfo/blfs-dev > > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > > Unsubscribe: See the above information page > > I build libreoffice 7 with gcc and without clang, which I do not have > installed. I also do not have skia installed. > It generates > > checking whether to build Skia... yes > checking for clang... no > configure: WARNING: Clang compiler not found. > > Takes about an hour on my i5-8600 for make build-nocheck. > Clearly they may change this in future but this suggests that clang need not > be required by the book. Hmm. Technically it is 'Recommended'. All my systems do have clang and I don'y have a log from the failed build, all I know for certain is that it tried to use clang when building skia, and failed because clang does not (in current release) support my flags. I'm guessing that your log can be interpreted as should I build skia : yes (default) do you have clang : no ok, cannot build skia, issue a warning. ĸen -- Juliet's version of cleanliness was next to godliness, which was to say it was erratic, past all understanding and was seldom seen. -- Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] xfce4-pulseaudio-plugin
On 8/31/20 5:07 AM, Ryan Marsaw via blfs-dev wrote: On Mon, 31 Aug 2020, Ken Moffat via blfs-dev wrote: On Mon, Aug 31, 2020 at 03:11:02PM +0800, Xi Ruoyao via blfs-dev wrote: On 2020-08-31 07:49 +0100, Ken Moffat via blfs-dev wrote: > On Mon, Aug 31, 2020 at 01:20:52AM -0500, Bruce Dubbs via blfs-dev > wrote: > > On 8/31/20 1:10 AM, Ken Moffat via blfs-dev wrote: > > > The download link works, but the download is > > > xfce4-pulseaudio-plugin-xfce4-pulseaudio-plugin-0.4.3- > > > 9de2b7865ecb95bdd2cbaae00a17b23ae8455fe5.tar.bz2 > > > > > > I wonder if we should remark on this - in places we remark on > > > directory names which do not match the tarball. This one's > > > direcotry does match the tarball, but hte tarball name is > > > certainly not what I was expecting. > > > > Yes, it's pretty ugly. I did put in a note about it. > > > > -- Bruce > > > Ah, yeah, I see now 'This package extracts to a very non-standard > directory.' but I will argue that the directory, although very ugly, > is standard. That is, it matches the tarball name. It is the > tarball name which does not match what the link claims to download > > (xfce4-pulseaudio-plugin-0.4.3/xfce4-pulseaudio-plugin-0.4.3.tar.bz2) If wget is used to retrieve the file, the tarball name will be correct. But if a browser is used, it will be wrong. Right you are. Thanks. So, the user's options seem to be to use wget, and note that it will unpack to a very long and ugly directory name, or use a browser and get the same name in the tarball. The joys of github. This might seem like an obvious question, or maybe I'm missing something, but why not just use the same directory structure for xfce4-pulseaudio-plugin as the one that's used for the other XFCE packages? For pretty much all of XFCE, download location begins with "http://archive.xfce.org/ ..." For xfce4-pulseaudio-plugin, I use "https://archive.xfce.org/src/panel-plugins/xfce4-pulseaudio-plugin/0.4/xfce4-pulseaudio-plugin-0.4.3.tar.bz2; Also of note is that keybinder-3.0-0.3.2 is an optional download; not required. Secondly, my logs show no mention of xfce4-dev-tools-4.14.0 in the build. I'm not sure why this package is needed at all for XFCE (unless it has something to do with xfce4-pulseaudio-plugin being built with a Github download...) I didn't use that URL because I didn't find it. I'll change to that. Thanks a lot. I'll look at whether xfce4-dev-tools tools is needed or not. At first glance, it looks like the new tarball does no need it. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] libreoffice-7 wants clang
On Mon, 31 Aug 2020 01:44:03 -0500 Ken Moffat via blfs-dev wrote: > On Mon, Aug 31, 2020 at 06:48:47AM +0100, Ken Moffat via blfs-dev wrote: > > Changing the title ecause this is a separate issue. > > > > Oh - tried updating libreoffice on another machine: with the skia > > code it defaults to using clang (and my CFLAGS, CXXFLAGS have > > -fstack-clash-protection which clang-10 does not understand). > > > > ĸen > > Nope, it still uses clang, which eventually fails: > > clang-10: error: unknown argument: '-fstack-clash-protection' > clang-10: error: unsupported argument '8' to option 'flto=' > > I'm guessing clang generated flto=8 (an 8-thread machine) and got > confused by the previous unsupproted switch. > > https://www.phoronix.com/scan.php?page=news_item=LibreOffice-7.0-Prefers-Clang > > Oddly, Arch (libreoffice-fresh) do not seem to list clang or even > llvm as deps. > > Fedora are using --disable-skia which might work around this. I'll > try that for my own builds, which are a bt less than the book (e,g, no > java) but I think we'll need to make clang required in the book. > > ĸen > -- > Juliet's version of cleanliness was next to godliness, which was to > say it was erratic, past all understanding and was seldom seen. > -- Unseen Academicals > -- > http://lists.linuxfromscratch.org/listinfo/blfs-dev > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page I build libreoffice 7 with gcc and without clang, which I do not have installed. I also do not have skia installed. It generates checking whether to build Skia... yes checking for clang... no configure: WARNING: Clang compiler not found. Takes about an hour on my i5-8600 for make build-nocheck. Clearly they may change this in future but this suggests that clang need not be required by the book. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] xfce4-pulseaudio-plugin
On Mon, 31 Aug 2020, Ken Moffat via blfs-dev wrote: On Mon, Aug 31, 2020 at 03:11:02PM +0800, Xi Ruoyao via blfs-dev wrote: On 2020-08-31 07:49 +0100, Ken Moffat via blfs-dev wrote: > On Mon, Aug 31, 2020 at 01:20:52AM -0500, Bruce Dubbs via blfs-dev > wrote: > > On 8/31/20 1:10 AM, Ken Moffat via blfs-dev wrote: > > > The download link works, but the download is > > > xfce4-pulseaudio-plugin-xfce4-pulseaudio-plugin-0.4.3- > > > 9de2b7865ecb95bdd2cbaae00a17b23ae8455fe5.tar.bz2 > > > > > > I wonder if we should remark on this - in places we remark on > > > directory names which do not match the tarball. This one's > > > direcotry does match the tarball, but hte tarball name is > > > certainly not what I was expecting. > > > > Yes, it's pretty ugly. I did put in a note about it. > > > > -- Bruce > > > Ah, yeah, I see now 'This package extracts to a very non-standard > directory.' but I will argue that the directory, although very ugly, > is standard. That is, it matches the tarball name. It is the > tarball name which does not match what the link claims to download > > (xfce4-pulseaudio-plugin-0.4.3/xfce4-pulseaudio-plugin-0.4.3.tar.bz2) If wget is used to retrieve the file, the tarball name will be correct. But if a browser is used, it will be wrong. Right you are. Thanks. So, the user's options seem to be to use wget, and note that it will unpack to a very long and ugly directory name, or use a browser and get the same name in the tarball. The joys of github. This might seem like an obvious question, or maybe I'm missing something, but why not just use the same directory structure for xfce4-pulseaudio-plugin as the one that's used for the other XFCE packages? For pretty much all of XFCE, download location begins with "http://archive.xfce.org/ ..." For xfce4-pulseaudio-plugin, I use "https://archive.xfce.org/src/panel-plugins/xfce4-pulseaudio-plugin/0.4/xfce4-pulseaudio-plugin-0.4.3.tar.bz2; Also of note is that keybinder-3.0-0.3.2 is an optional download; not required. Secondly, my logs show no mention of xfce4-dev-tools-4.14.0 in the build. I'm not sure why this package is needed at all for XFCE (unless it has something to do with xfce4-pulseaudio-plugin being built with a Github download...) Cheers, --Ryan -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] xfce4-pulseaudio-plugin
On Mon, Aug 31, 2020 at 03:11:02PM +0800, Xi Ruoyao via blfs-dev wrote: > On 2020-08-31 07:49 +0100, Ken Moffat via blfs-dev wrote: > > On Mon, Aug 31, 2020 at 01:20:52AM -0500, Bruce Dubbs via blfs-dev > > wrote: > > > On 8/31/20 1:10 AM, Ken Moffat via blfs-dev wrote: > > > > The download link works, but the download is > > > > xfce4-pulseaudio-plugin-xfce4-pulseaudio-plugin-0.4.3- > > > > 9de2b7865ecb95bdd2cbaae00a17b23ae8455fe5.tar.bz2 > > > > > > > > I wonder if we should remark on this - in places we remark on > > > > directory names which do not match the tarball. This one's > > > > direcotry does match the tarball, but hte tarball name is > > > > certainly not what I was expecting. > > > > > > Yes, it's pretty ugly. I did put in a note about it. > > > > > > -- Bruce > > > > > Ah, yeah, I see now 'This package extracts to a very non-standard > > directory.' but I will argue that the directory, although very ugly, > > is standard. That is, it matches the tarball name. It is the > > tarball name which does not match what the link claims to download > > > > (xfce4-pulseaudio-plugin-0.4.3/xfce4-pulseaudio-plugin-0.4.3.tar.bz2) > > If wget is used to retrieve the file, the tarball name will be correct. But > if > a browser is used, it will be wrong. > Right you are. Thanks. So, the user's options seem to be to use wget, and note that it will unpack to a very long and ugly directory name, or use a browser and get the same name in the tarball. The joys of github. I've no idea how best to phrase that, and I'm hoping to go to bed so I don't think I'll have anything to add re phraseology. Meanwhile I've got a weird local problem with my libreoffice script: it claims to have added --disable-skia to the build, but the log from autogen suggests it has instead added my old --enable-lto (had that originally, supposedly replaced it by --disable-skia). Meanwhile, it has been building for something like an hour and a quarter - previous attempts failed quickly when clang hit my -fstack-clash-protection, so I'm hopeful but perplexed. ĸen -- Juliet's version of cleanliness was next to godliness, which was to say it was erratic, past all understanding and was seldom seen. -- Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] xfce4-pulseaudio-plugin
On 2020-08-31 07:49 +0100, Ken Moffat via blfs-dev wrote: > On Mon, Aug 31, 2020 at 01:20:52AM -0500, Bruce Dubbs via blfs-dev > wrote: > > On 8/31/20 1:10 AM, Ken Moffat via blfs-dev wrote: > > > The download link works, but the download is > > > xfce4-pulseaudio-plugin-xfce4-pulseaudio-plugin-0.4.3- > > > 9de2b7865ecb95bdd2cbaae00a17b23ae8455fe5.tar.bz2 > > > > > > I wonder if we should remark on this - in places we remark on > > > directory names which do not match the tarball. This one's > > > direcotry does match the tarball, but hte tarball name is > > > certainly not what I was expecting. > > > > Yes, it's pretty ugly. I did put in a note about it. > > > > -- Bruce > > > Ah, yeah, I see now 'This package extracts to a very non-standard > directory.' but I will argue that the directory, although very ugly, > is standard. That is, it matches the tarball name. It is the > tarball name which does not match what the link claims to download > > (xfce4-pulseaudio-plugin-0.4.3/xfce4-pulseaudio-plugin-0.4.3.tar.bz2) If wget is used to retrieve the file, the tarball name will be correct. But if a browser is used, it will be wrong. > ĸen > -- > Juliet's version of cleanliness was next to godliness, which was to > say it was erratic, past all understanding and was seldom seen. > -- Unseen Academicals -- Xi Ruoyao School of Aerospace Science and Technology, Xidian University -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] xfce4-pulseaudio-plugin
On Mon, Aug 31, 2020 at 01:20:52AM -0500, Bruce Dubbs via blfs-dev wrote: > On 8/31/20 1:10 AM, Ken Moffat via blfs-dev wrote: > > The download link works, but the download is > > xfce4-pulseaudio-plugin-xfce4-pulseaudio-plugin-0.4.3-9de2b7865ecb95bdd2cbaae00a17b23ae8455fe5.tar.bz2 > > > > I wonder if we should remark on this - in places we remark on > > directory names which do not match the tarball. This one's > > direcotry does match the tarball, but hte tarball name is > > certainly not what I was expecting. > > Yes, it's pretty ugly. I did put in a note about it. > > -- Bruce > Ah, yeah, I see now 'This package extracts to a very non-standard directory.' but I will argue that the directory, although very ugly, is standard. That is, it matches the tarball name. It is the tarball name which does not match what the link claims to download (xfce4-pulseaudio-plugin-0.4.3/xfce4-pulseaudio-plugin-0.4.3.tar.bz2) ĸen -- Juliet's version of cleanliness was next to godliness, which was to say it was erratic, past all understanding and was seldom seen. -- Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] libreoffice-7 wants clang
On Mon, Aug 31, 2020 at 06:48:47AM +0100, Ken Moffat via blfs-dev wrote: Changing the title ecause this is a separate issue. > > Oh - tried updating libreoffice on another machine: with the skia > code it defaults to using clang (and my CFLAGS, CXXFLAGS have > -fstack-clash-protection which clang-10 does not understand). > > ĸen Nope, it still uses clang, which eventually fails: clang-10: error: unknown argument: '-fstack-clash-protection' clang-10: error: unsupported argument '8' to option 'flto=' I'm guessing clang generated flto=8 (an 8-thread machine) and got confused by the previous unsupproted switch. https://www.phoronix.com/scan.php?page=news_item=LibreOffice-7.0-Prefers-Clang Oddly, Arch (libreoffice-fresh) do not seem to list clang or even llvm as deps. Fedora are using --disable-skia which might work around this. I'll try that for my own builds, which are a bt less than the book (e,g, no java) but I think we'll need to make clang required in the book. ĸen -- Juliet's version of cleanliness was next to godliness, which was to say it was erratic, past all understanding and was seldom seen. -- Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] xfce4-pulseaudio-plugin
On 8/31/20 1:10 AM, Ken Moffat via blfs-dev wrote: The download link works, but the download is xfce4-pulseaudio-plugin-xfce4-pulseaudio-plugin-0.4.3-9de2b7865ecb95bdd2cbaae00a17b23ae8455fe5.tar.bz2 I wonder if we should remark on this - in places we remark on directory names which do not match the tarball. This one's direcotry does match the tarball, but hte tarball name is certainly not what I was expecting. Yes, it's pretty ugly. I did put in a note about it. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] xfce4-pulseaudio-plugin
The download link works, but the download is xfce4-pulseaudio-plugin-xfce4-pulseaudio-plugin-0.4.3-9de2b7865ecb95bdd2cbaae00a17b23ae8455fe5.tar.bz2 I wonder if we should remark on this - in places we remark on directory names which do not match the tarball. This one's direcotry does match the tarball, but hte tarball name is certainly not what I was expecting. ĸen -- Juliet's version of cleanliness was next to godliness, which was to say it was erratic, past all understanding and was seldom seen. -- Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
