[blfs-support] fcron md5sum BLFS 10.1/development

[rhubarbpieguy--- via blfs-support]

The fcron md5sum I see differs from the documentation.

md5sum fcron-3.2.1.src.tar.gz generates 
489a7f41afdd88f9312b517b8a6c2433, while the documentation shows 
bd4996e941a40327d11efc5e3fd1f839.  I've downloaded the file several 
times and the md5s for all other files hit.  What might I be doing wrong?


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Kernel configuration observations/questions - BLFS 10.0/development

[rhubarbpieguy--- via blfs-support]

On 12/3/20 8:14 PM, Douglas R. Reno via blfs-support wrote:

On 11/26/20 4:58 PM, rhubarbpieguy--- via blfs-support wrote:


Hi rhubarbpieguy,

I looked into the ones that Ken didn't do, and I have some feedback.


BlueZ

-*- Cryptographic API ---> [CONFIG_CRYPTO]
   User-space interface for hash algorithms 
[CONFIG_CRYPTO_USER_API_HASH]
   User-space interface for symmetric key cipher algorithms 
[CONFIG_CRYPTO_USER_API_SKCIPHER]


   I believe Cryptographic API has no options.  Could [CONFIG_CRYPTO] 
be deleted as in cryptsetup?


Cryptographic API does have plenty of options, at least on my 
configuration (5.9.12)
I was unclear, by no options I mean there are no choices for the line as 
it's -*-.  I was questioning whether [CONFIG_CRYPTO] could be deleted on 
the line.  I appreciate [CONFIG_SpecificsHere]'s in the documentation 
but was questioning the need for any line with no entry to be made, such 
as with cryptsetup.  But with that, it was a question, not a statement.  
Just a thought.
-- 


lm-sensors
Device Drivers  --->

  I2C support --->
    <*/M> I2C device interface [CONFIG_I2C_CHARDEV]
    I2C Hardware Bus support  --->
   (configure all of them as modules)
  <*/M> Hardware Monitoring support  ---> [CONFIG_HWMON]

   I believe Hardware Monitoring support has no options.  Should it 
be -*- Hardware Monitoring Support?  If so, could [CONFIG_HWMON] be 
deleted?

It does have many options, at least on my configuration.
Poor wording on my part.  The line -*- Hardware Monitoring Support ---> 
has no options as it's -*- in menuconfig.  I can enter neither Y nor M.
-- 



UPower

General Setup --->
    [*] Namespaces support ---> [CONFIG_NAMESPACES]

   I believe Namespaces support has no options.  Should it be -*- 
Namespaces support?  If so, could [CONFIG_NAMESPACES] be deleted?

Namespaces support does have the following options:
Again, poor wording on my part.  The line -*- Namespaces support ---> 
has no options as it's -*- in menuconfig.  No entry is accepted that I see.
-- 


Cups

Device Drivers  --->
  <*/M> Parallel port support  --->    [CONFIG_PARPORT]
    <*/M> PC-style hardware    [CONFIG_PARPORT_PC]
  Character devices  --->
    <*/M> Parallel printer support [CONFIG_PRINTER]

   I see no CONFIG_PRINTER in .config.  Can the Character devices and 
Parallel printer lines be deleted?  I do see CONFIG_USB_PRINTER.
CONFIG_PRINTER is there. I found it on 5.9.12 by pressing "/" (for 
search) and then typing in CONFIG_PRINTER. It still is under Character 
Devices. I think it does require Parallel Port support as a 
prerequisite though.

My mistake; I see it after enabling Parallel Port support.
-- 

I appreciate your following up on this.  I realize many items were 
minor; my observations are primarily from a proof reading view.  I also 
realize the post was long, but I thought it better to address the area 
in one fell swoop versus bits and pieces.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Kernel configuration observations/questions - BLFS 10.0/development

[rhubarbpieguy--- via blfs-support]

autofs

File systems --->
  <*/M> Kernel automounter version 4 support (also supports v3) 
[CONFIG_AUTOFS4_FS]


   I believe Kernel automounter support has no options.  Should the 
above lines be deleted?


File systems  --->
  [*] Network File Systems ---> [CONFIG_NETWORK_FILESYSTEMS]
    <*/M> NFS client support  
[CONFIG_NFS_FS]
    <*/M> CIFS support (advanced network filesystem, SMBFS successor) 
[CONFIG_CIFS]


   Should CIFS support (advanced network filesystem, SMBFS successor) 
be SMB3 and CIFS support (advanced network filesystem)?
-- 



BlueZ

[*] Networking support --->    [CONFIG_NET]
   Bluetooth subsystem support --->    [CONFIG_BT]

   Is  correct?  Should it be ?  <*/M>?

<*/M> RF switch subsystem support --->   [CONFIG_RFKILL]

   Should RF switch subsystem support ---> be RF switch subsystem 
support ?


[*] Networking support --->    [CONFIG_NET]
-*- Cryptographic API ---> [CONFIG_CRYPTO]
   User-space interface for hash algorithms 
[CONFIG_CRYPTO_USER_API_HASH]
   User-space interface for symmetric key cipher algorithms 
[CONFIG_CRYPTO_USER_API_SKCIPHER]


   I believe Cryptographic API has no options.  Could [CONFIG_CRYPTO] 
be deleted as in cryptsetup?


   As with the above, should the hash algorithms and key cipher lines 
be ?  <*/M>?
-- 



lm-sensors

[*] Enable loadable module support  --->  [CONFIG_MODULES]

Bus options (PCI etc.)  --->
  [*] PCI support [CONFIG_PCI]

   Should Enable loadable module support and Bus options be reversed to 
follow the order displayed with menuconfig?


Device Drivers  --->
  I2C support --->
    <*/M> I2C device interface [CONFIG_I2C_CHARDEV]
    I2C Hardware Bus support  --->
   (configure all of them as modules)
  <*/M> Hardware Monitoring support  ---> [CONFIG_HWMON]

   I believe Hardware Monitoring support has no options.  Should it be 
-*- Hardware Monitoring Support?  If so, could [CONFIG_HWMON] be deleted?
-- 



UPower

General Setup --->
    [*] Namespaces support ---> [CONFIG_NAMESPACES]

   I believe Namespaces support has no options.  Should it be -*- 
Namespaces support?  If so, could [CONFIG_NAMESPACES] be deleted?
-- 



Cheese

Device Drivers  --->
  Multimedia support --->
    <*> Cameras/video grabbers support [CONFIG_MEDIA_CAMERA_SUPPORT]
    <*> Media USB Adapters  ---> [CONFIG_MEDIA_USB_SUPPORT]

  Should the above be:

Device Drivers  --->
   <*> Multimedia support  --->
  Media device types  --->
 <*> Cameras and video grabbers [CONFIG_MEDIA_CAMERA_SUPPORT]
  Media drivers  --->
    <*> Media USB Adapters ---> [CONFIG_MEDIA_USB_SUPPORT]

  The documentation implies nothing is to be built as a module.
-- 



alsa-lib

Device Drivers --->
  <*/m> Sound card support ---> [CONFIG_SOUND]
    <*/m> Advanced Linux Sound Architecture ---> [CONFIG_SND]

   Should the <*/m>'s above be <*/M> for consistency with the 
documentation?
-- 



cryptsetup

Cryptographic API  --->
  <*/M> XTS support [CONFIG_CRYPTO_XTS]
  <*/M> SHA224 and SHA256 digest algorithm [CONFIG_CRYPTO_SHA256]

   Should Cryptographic API  ---> be -*- Cryptographic API --->?

   I believe SHA224 and SHA256 digest algorithm has no options Should 
the line be deleted?
-- 



dosfstools

File systems --->
  

   Should  be DOS/FAT/EXFAT/NT Filesystems 
--->?
-- 



About Firmware

General Setup --->
  [y] Initial RAM filesystem and RAM disk (initramfs/initrd) support 
[CONFIG_BLK_DEV_INITRD]

Processor type and features  --->
  [y] CPU microcode loading support  [CONFIG_MICROCODE]
  [y]  AMD microcode loading support [CONFIG_MICROCODE_AMD]

   Should the [y]'s above be <*> for consistency with the documentation?
-- 



iptables

[*] Networking support --->  
[CONFIG_NET]

  Networking Options  --->
    [*] Network packet filtering framework (Netfilter) --->   
[CONFIG_NETFILTER]
  [*] Advanced netfilter 

[blfs-support] Installation of the kernel systemd documentation - LFS 10.0/development

[rhubarbpieguy--- via blfs-support]

General setup -->

   [*] Control Group support [CONFIG_CGROUPS]
   [ ] Enable deprecated sysfs features to support old userspace tools 
[CONFIG_SYSFS_DEPRECATED]
   [*] Configure standard kernel features (expert users) 
[CONFIG_EXPERT] --->

  [*] open by fhandle syscalls [CONFIG_FHANDLE]
   [ ] Auditing support [CONFIG_AUDIT]

Would it make sense to move [ ] Auditing support [CONFIG_AUDIT] to the 
top of the General setup options?  That appears to be the order shown 
with menuconfig.


- 



File systems  --->
   [*] Inotify support for userspace [CONFIG_INOTIFY_USER]
   <*> Kernel automounter support (supports v3, v4, and v5) 
[CONFIG_AUTOFS_FS]


Kernel automounter support (supports v3, v4, and v5) now appears hard 
coded with no option available.  Could/should the line be deleted?


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

[rhubarbpieguy--- via blfs-support]

On 10/20/20 9:00 AM, Pierre Labastie via blfs-support wrote:

On Tue, 2020-10-20 at 06:50 -0500, rhubarbpieguy--- via blfs-support
wrote:

Sorry, I was sloppy providing output.  The problem occurs with 'make'

and I included the tail end of 'make install.'   The error with
'make'
is:

  ninja: build stopped: subcommand failed.
  make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1
  make[3]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
  make[2]: *** [Makefile:82: sub-gn_run-pro-make_first]
Error 2
  make[2]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
  make[1]: *** [Makefile:80: sub-core-make_first] Error 2
  make[1]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src'
  make: *** [Makefile:49: sub-src-make_first] Error 2

Is there other output I should cite?

Yes, that output is meaningless.  We need a dozen or more lines
before the
subcommand failed line.

-- Bruce


True, but we can already see it is in Makefile.gn.

A wild guess: has /usr/lib/libstdc++.a been hidden or deleted ?
The gn tool needs that.  The only other thing on my systems which
needs it is binutils (in that case, for the testsuite).

More generally, when building in parallel the failure is sometimes
*many* lines before the ' Error ' report.

ĸen

I believe I have /usr/lib/libstdc++.a  I see the following libstdc++
files:

   /usr/lib/libstdc++.a
   /usr/lib/libstdc++fs.a
   /usr/lib/libstdc++.so -> libstdc++.so.6.0.28
   /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.28
   /usr/lib/libstdc++.so.6.0.28
   /usr/lib/libstdc++.so.6.0.28.dbg

I'm attaching more output generated with the '--output-sync' option
suggested in another response.  Perhaps that will show what I've done
wrong.



As pointed out by Christopher Gregory, the error is with some
incompatible changes in system icu. There is a patch in blfs-10.0 to
cure that. Have you applied it? (qtwebengine-everywhere-src-5.15.0-
consolidated_fixes-3.patch)

Pierre

My miscue was the patch.  I saw the patch in the documentation and 
sincerely thought I'd installed it via a bash script. Unfortunately, I 
modified the script I'd used for several releases.  My modification was 
misguided and I didn't see the patch hadn't applied (long story).  My 
lesson is to compile a package manually should it fail using a script.  
Live and learn.




--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

[rhubarbpieguy--- via blfs-support]

Sorry, I was sloppy providing output.  The problem occurs with 'make'

and I included the tail end of 'make install.'   The error with 'make'
is:

     ninja: build stopped: subcommand failed.
     make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1
     make[3]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
     make[2]: *** [Makefile:82: sub-gn_run-pro-make_first] Error 2
     make[2]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
     make[1]: *** [Makefile:80: sub-core-make_first] Error 2
     make[1]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src'
     make: *** [Makefile:49: sub-src-make_first] Error 2

Is there other output I should cite?

Yes, that output is meaningless.  We need a dozen or more lines before the
subcommand failed line.

   -- Bruce


True, but we can already see it is in Makefile.gn.

A wild guess: has /usr/lib/libstdc++.a been hidden or deleted ?
The gn tool needs that.  The only other thing on my systems which
needs it is binutils (in that case, for the testsuite).

More generally, when building in parallel the failure is sometimes
*many* lines before the ' Error ' report.

ĸen


I believe I have /usr/lib/libstdc++.a  I see the following libstdc++ files:

 /usr/lib/libstdc++.a
 /usr/lib/libstdc++fs.a
 /usr/lib/libstdc++.so -> libstdc++.so.6.0.28
 /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.28
 /usr/lib/libstdc++.so.6.0.28
 /usr/lib/libstdc++.so.6.0.28.dbg

I'm attaching more output generated with the '--output-sync' option 
suggested in another response.  Perhaps that will show what I've done wrong.



[10700/18215] /usr/bin/g++ -MMD -MF obj/v8/v8_base_without_compiler/log.o.d 
-DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD 
-DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-DNO_UNWIND_TABLES -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64 -DENABLE_MINOR_MC -DV8_INTL_SUPPORT 
-DV8_CONCURRENT_MARKING -DV8_ENABLE_LAZY_SOURCE_POSITIONS 
-DV8_EMBEDDED_BUILTINS -DV8_WIN64_UNWINDING_INFO 
-DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH -DV8_COMPRESS_POINTERS 
-DV8_31BIT_SMIS_ON_64BIT_ARCH -DV8_DEPRECATION_WARNINGS -DV8_TARGET_ARCH_X64 
-DV8_HAVE_TARGET_OS -DV8_TARGET_OS_LINUX -DDISABLE_UNTRUSTED_CODE_MITIGATIONS 
-DV8_COMPRESS_POINTERS -DV8_31BIT_SMIS_ON_64BIT_ARCH -DV8_DEPRECATION_WARNINGS 
-DUSING_SYSTEM_ICU=1 -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC 
-DUCHAR_TYPE=uint16_t -DV8_COMPRESS_POINTERS -DV8_31BIT_SMIS_ON_64BIT_ARCH 
-DV8_DEPRECATION_WARNINGS -Igen -I../../../../src/3rdparty/chromium 
-I../../../../src/3rdparty/chromium/v8 -Igen/v8 -Igen -Igen 
-I../../../../src/3rdparty/chromium/v8/include 
-I../../../../src/3rdparty/chromium/third_party/zlib -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -fno-unwind-tables 
-fno-asynchronous-unwind-tables -fPIC -pipe -pthread -m64 -Wall 
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs 
-Wno-maybe-uninitialized -Wno-deprecated-declarations 
-fno-delete-null-pointer-checks -Wno-comments -Wno-packed-not-aligned 
-Wno-dangling-else -Wno-missing-field-initializers -Wno-unused-parameter 
-fno-omit-frame-pointer -fvisibility=hidden -Wno-strict-overflow 
-Wno-return-type -O3 -fno-ident -fdata-sections -ffunction-sections -g0 
-std=gnu++14 -Wno-narrowing -Wno-class-memaccess -Wno-attributes 
-Wno-class-memaccess -Wno-subobject-linkage -Wno-invalid-offsetof 
-Wno-return-type -Wno-deprecated-copy -fno-exceptions -fno-rtti 
-fvisibility-inlines-hidden -c 
../../../../src/3rdparty/chromium/v8/src/logging/log.cc -o 
obj/v8/v8_base_without_compiler/log.o
[10701/18215] /usr/bin/g++ -MMD -MF obj/v8/v8_base_without_compiler/strtod.o.d 
-DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD 
-DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-DNO_UNWIND_TABLES -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64 -DENABLE_MINOR_MC -DV8_INTL_SUPPORT 
-DV8_CONCURRENT_MARKING -DV8_ENABLE_LAZY_SOURCE_POSITIONS 
-DV8_EMBEDDED_BUILTINS -DV8_WIN64_UNWINDING_INFO 
-DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH -DV8_COMPRESS_POINTERS 
-DV8_31BIT_SMIS_ON_64BIT_ARCH -DV8_DEPRECATION_WARNINGS -DV8_TARGET_ARCH_X64 
-DV8_HAVE_TARGET_OS -DV8_TARGET_OS_LINUX -DDISABLE_UNTRUSTED_CODE_MITIGATIONS 
-DV8_COMPRESS_POINTERS -DV8_31BIT_SMIS_ON_64BIT_ARCH -DV8_DEPRECATION_WARNINGS 
-DUSING_SYSTEM_ICU=1 -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC 
-DUCHAR_TYPE=uint16_t -DV8_COMPRESS_POINTERS -DV8_31BIT_SMIS_ON_64BIT_ARCH 
-DV8_DEPRECATION_WARNINGS -Igen -I../../../../src/3rdparty/chromium 
-I../../../../src/3rdparty/chromium/v8 -Igen/v8 -Igen -Igen 
-I../../../../src/3rdparty/chromium/v8/include 
-I../../../../src/3rdparty/chromium/third_party/zlib -fno-strict-aliasing 

Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

[rhubarbpieguy--- via blfs-support]

On 10/17/20 9:14 PM, Ken Moffat via blfs-support wrote:

On Sat, Oct 17, 2020 at 04:11:07PM -0500, rhubarbpieguy--- via blfs-support 
wrote:

Compiling QtWebEngine fails with the following end output:

    make[3]: *** No rule to make target 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core/release/QtWebEngineCore.stamp',
needed by '../../lib/libQt5WebEngineCore.so.5.15.0'.  Stop.
    make[3]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
    make[2]: *** [Makefile:132: sub-core_module-pro-install_subtargets] Error
2
    make[2]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
    make[1]: *** [Makefile:92: sub-core-install_subtargets] Error 2
    make[1]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src'
    make: *** [Makefile:61: sub-src-install_subtargets] Error 2

However, the problem appears to start with 'make: *** [Makefile:49:
sub-src-make_first] Error 2.'

Qt5 appears to have compiled without error and I believe I'm following the
documentation.  I tried 'NINJA_JOBS=4 make' without success?


I can recall that at times building qtwebengine with NINJA_JOBS has
been a right PITA, and my notes suggest that passing VERBOSE=1 to
make definitely stopped it using NINJA_JOBS.

I think that on one occasion I was able to find the error by
rerunning make in the broken build (and writing to a file, but I
also recall that there is no output until the build ends).

If you need to restrict the number of cores (e.g. insufficient
DRAM), taking cores offline (not core 0!) by echoing 0 to
/sys/devices/system/cpu/cpu/online etc for the cores you wish to
disable (on intel, probably the highest numbered if SMT, on zen the
"slow" cores might vary).  But that's just a workaround.

However, looking at your output I'm puzzled (unless the error was
during the install) - Output from 'make' (e.g. at start of line,
there are a lot of filenames which include make in them) doesn't
really appear in my log from the main build except in

make[3]: Nothing to be done for 'first'.
[1/185] CXX base/files/file_path_constants.o

  (running make Makefile.gn to put things together, the part that
  needs a static lib, which ends at

[185/185] LINK gn
make[3]: Nothing to be done for 'first'.

  and then a little later

make[3]: Entering directory 
'/scratch/working/qtwebengine-everywhere-src-5.15.0/build/src/core'
ninja -v  -C 
/scratch/working/qtwebengine-everywhere-src-5.15.0/build/src/core/release 
QtWebEngineCore
ninja: Entering directory 
`/scratch/working/qtwebengine-everywhere-src-5.15.0/build/src/core/release'
[1/18172] touch obj/base/allocator/allocator.stamp

  and nothing more until

[18172/18172] touch QtWebEngineCore.stamp
make[3]: Leaving directory 
'/scratch/working/qtwebengine-everywhere-src-5.15.0/build/src/core'

and then after that I see 'make' bouncing around directories,
removing files, (re) creating .so libs - I assumed that was part of
the install, but perhaps it is the end of 'make' itself.  If so, did
all the ninja targets complete ?

ĸen


Sorry, I was sloppy providing output.  The problem occurs with 'make' 
and I included the tail end of 'make install.'   The error with 'make' is:


   ninja: build stopped: subcommand failed.
   make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1
   make[3]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'

   make[2]: *** [Makefile:82: sub-gn_run-pro-make_first] Error 2
   make[2]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'

   make[1]: *** [Makefile:80: sub-core-make_first] Error 2
   make[1]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src'

   make: *** [Makefile:49: sub-src-make_first] Error 2

Is there other output I should cite?


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

[rhubarbpieguy--- via blfs-support]

Compiling QtWebEngine fails with the following end output:

   make[3]: *** No rule to make target 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core/release/QtWebEngineCore.stamp', 
needed by '../../lib/libQt5WebEngineCore.so.5.15.0'.  Stop.
   make[3]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
   make[2]: *** [Makefile:132: sub-core_module-pro-install_subtargets] 
Error 2
   make[2]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'

   make[1]: *** [Makefile:92: sub-core-install_subtargets] Error 2
   make[1]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src'

   make: *** [Makefile:61: sub-src-install_subtargets] Error 2

However, the problem appears to start with 'make: *** [Makefile:49: 
sub-src-make_first] Error 2.'


Qt5 appears to have compiled without error and I believe I'm following 
the documentation.  I tried 'NINJA_JOBS=4 make' without success?


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] 'systemctl enable bluetooth' failure - BLFS 9.1 (systemd)

[rhubarbpieguy--- via blfs-support]

Executing 'systemctl enable bluetooth' responds with the following:

   Failed to execute /lib/systemd/systemd-sysv-install: No such file or 
directory


I believe I compiled systemd in LFS and BLFS according to instructions 
and don't see /lib/systemd/systemd-sysv-install in the LFS 9.1 
Systemd-244 documentation.  But what did I miss?

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Compiling systemd and dbus in chroot? - BLFS 9.1 systemd

[rhubarbpieguy--- via blfs-support]

Can/should systemd and dbus be compiled in chroot?  I assume so, partly 
due to the following in the dbus documentation:


   "If not in chroot, at this point, you should reload the systemd 
daemon, and reenter multi-user mode with the following commands (as the 
root user):"


   systemctl daemon-reload
   systemctl start multi-user.target

However, should a "If not in chroot" note also be applied to the Warning 
block "systemctl start rescue.target" command of the dbus documentation?


And should a chroot note be in the Warning block of the systemd 
documentation?  The Note block seems to indicate chroot isn't 
appropriate for the tests.  I didn't run the systemd tests when 
compiling systemd in chroot.


The last section I question in the systemd documentation is as follows:

   "At this point, you should reload the systemd daemon, and reenter 
multi-user mode with the following commands (as the root user):"


   systemctl daemon-reload
   systemctl start multi-user.target

Should a chroot note be added?

Another option might be a comprehensive note at the beginning of both 
packages stating something like "If in chroot, omit all systemctl 
commands for this package."


I built BLFS 9.1 systemd in chroot and it appears to be working well but 
I'm new to systemd.  The above are questions, not statements.




--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] libusb kernel configuration - BLFS 9.1

[rhubarbpieguy--- via blfs-support]

A minor point, but I think the following is inaccurate:

   Device Drivers --->
        [*] USB support ---> [CONFIG_USB_SUPPORT]
          <*/M> Support for Host-side USB  [CONFIG_USB]
      (Select any USB hardware device drivers you may need on the 
same page)


The 'Support for Host-side USB' line offers no <*/M> choice in the 
configuration menu that I see.  It's listed as:


   -*-   Support for Host-side devices

So should the documentation be:

   Device Drivers --->
        [*] USB support ---> [CONFIG_USB_SUPPORT]
          (Select any USB hardware device drivers you may need)


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Firefox 'gold linker' mozconfig documentation - BLFS 9.1/development

[rhubarbpieguy--- via blfs-support]

I'm a touch confused about the following in the Firefox mozconfig 
documentation:


   # Do not specify the gold linker which is not the default. It will take
   # longer and use more disk space when debug symbols are disabled.

There seems to be no action to be taken.  Most other lines specify a 
line to comment/uncomment.  What's a gold linker?


Two other areas:

   # From firefox-61 system cairo is not supported

   ac_add_options --enable-system-ffi
   ac_add_options --enable-system-pixman

Again, there seems no action to be taken.  Are the two ac_add_options 
lines related to the cairo statement.?


---

   # From firefox-62 --with-pthreads is not recognized

   ac_add_options --with-system-bz2
   ac_add_options --with-system-jpeg
   ac_add_options --with-system-png
   ac_add_options --with-system-zlib

The same as above.  Are the four ac_add_options lines related to the 
pthreads statement?


To be clear, the mozconfig file works well, I'm just curious.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Bluez/bluetooth keyboard timeout and no reconnection at reboot. BLFS 9.0

[rhubarbpieguy--- via blfs-support]

I've compiled Bluez and can connect to my ThinkPad bluetooth keyboard 
which works well.  However, the keyboard times out.  And, before timing 
out, if I reboot or return from hibernation the keyboard doesn't reconnect.


To eliminate the keyboard as a problem I tested with a binary 
distribution.  I can connect and the keyboard does not time out. The 
keyboard also reconnects after a reboot or return from hibernation.


What might I have done wrong?


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] BlueZ documentation duplication. BLFS 9.0/development

[rhubarbpieguy--- via blfs-support]

The following is listed in the Kernel Configuration and testsuite 
sections of the Bluez documentation.


   [*] Networking support ---> 
[CONFIG_NET]


Could/should it be removed from the testsuite section?  A small matter, 
but it would remove duplication.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] BlueZ documentation duplication. BLFS 9.0/development

[rhubarbpieguy--- via blfs-support]

The following is listed in the Kernel Configuration and testsuite 
sections of the Bluez documentation.


   [*] Networking support ---> 
[CONFIG_NET]


Could/should it be removed from the testsuite section?  A small matter, 
but it would remove duplication.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Bluez test failure? BLFS 9.0

[rhubarbpieguy--- via blfs-support]

Compiling Bluez with 'make test' fails with:

   ./test-driver line 107:   8971 Aborted   
"$@" > log_file 2>&1


   FAIL: unit/test-sdp

The process then locks.  What does the failure mean?  To that point the 
following pass:


   PASS: unit/test-eir
   PASS: unit/test-uuid
   PASS: unit/test-textfile
   PASS: unit/test-crc
   PASS: unit/test-crypto
   PASS: unit/test-ecc
   PASS: unit/test-ringbuf
   PASS: unit/test-queue
   PASS: unit/test-mgmt
   PASS: unit/test-uhid


Hello,

Please make sure you have the following enabled in your kernel - I 
encountered that with the last update that I did to that package:


CONFIG_CRYPTO_USER_API=y
CONFIG_CRYPTO_USER_API_HASH=y
CONFIG_CRYPTO_USER_API_SKCIPHER=y
CONFIG_CRYPTO_USER_API_RNG=y
CONFIG_CRYPTO_USER_API_AEAD=y


That should allow it to surpass the test suite hangup

I compiled the following into my kernel:

   Cryptographic API  --->

  User-space interface for hash algorithms
  User-space interface for symmetric key cipher algorithms
  User-space interface for random number generator algorithms
  User-space interface for AEAD cipher algorithms

Unfortunately I have the same error.  I should mention bluez seems to 
compile without error.  I'm looking into the test results as I'm having 
problems connecting to my bluetooth keyboard.  It may simply be that I'm 
not using bluetoothctl correctly, but I thought I should run the tests 
as a first step.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Bluez test failure? BLFS 9.0

[rhubarbpieguy--- via blfs-support]

Compiling Bluez with 'make test' fails with:

   ./test-driver line 107:   8971 Aborted   
"$@" > log_file 2>&1


   FAIL: unit/test-sdp

The process then locks.  What does the failure mean?  To that point the 
following pass:


   PASS: unit/test-eir
   PASS: unit/test-uuid
   PASS: unit/test-textfile
   PASS: unit/test-crc
   PASS: unit/test-crypto
   PASS: unit/test-ecc
   PASS: unit/test-ringbuf
   PASS: unit/test-queue
   PASS: unit/test-mgmt
   PASS: unit/test-uhid


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] For the tests? elogind-241.3 - BLFS 9.0/development

[rhubarbpieguy--- via blfs-support]

The Optional section of the elogind documentation refers to packages 
required for the tests.  However, the installation section states 
elogind does not come with a test suite.  So what tests?


And I receive the following when compiling elogind:

   meson.build:63:8: ERROR: Program or command 'test' not found or not 
executable


I'm confused by the documentation.  And although perhaps unrelated, I 
don't understand the error.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Autoconf2.13 documentation - BLFS 9.0/development

[rhubarbpieguy--- via blfs-support]

For consistency, should the title in the autoconf documentation be 
Autoconf-2.13?


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Glib -Dselinux=false Command Explanation - BLFS 9.0/development

[rhubarbpieguy--- via blfs-support]

-Dselinux=false is a Command Explanation in the Glib documentation.  
Should it be -Dselinux=disabled?  I don't see disabled as a valid 
configuration option.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] UnZip - 6.0/ Zip - 3.0 BLFS 9.0/development

[rhubarbpieguy--- via blfs-support]

A minor point, but should 'UnZip - 6.0' and 'Zip - 3.0' in the 
documentation be 'UnZip - 60' and 'Zip - 30' or perhaps UnZip60 and


Zip30?  All other packages reference the file name.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Installing Python modules in BLFS - BLFS 9.0/development

[rhubarbpieguy--- via blfs-support]

On 9/21/19 9:37 AM, Bruce Dubbs via blfs-support wrote:

On 9/21/19 7:46 AM, rhubarbpieguy--- via blfs-support wrote:


Although Python 3 is now installed in LFS, it appears necessary to 
reinstall Python 3 in BLFS to install Python modules.  From the 
Python 3 documentation:


    "Python 3 was installed in LFS.  The only reason to install it 
here is if optional modules are needed."


I understand the note, but a user following dependency links doesn't 
see it.  For instance, Mako is required for Mesa, but the Mako link 
references the Mako page, which makes no mention of reinstalling 
Python 3.  As Python 3 was installed in LFS, a user would have no 
reason to suspect Python 3 must be reinstalled.


Would it make sense to add a note to Python modules using python3 
indicating Python 3 must be reinstalled?


Is it practical to amend the Python 3 LFS procedures to eliminate 
reinstalling Python 3 in BLFS?  That would eliminate the need for 
notes in BLFS and the Python 3 documentation.


I'm pretty sure the additional modules that section refers to are for 
berkeleydb, sqlite, and tk.  It is not needed for any of the modules 
in the blfs python modules section.


  -- Bruce

Thank you for the clarification. But I've apparently done something 
wrong, as when installing MarkupSafe I receive:


   ModuleNotFoundError: No module named 'html'

The entire message complains about setuptools and if I then compile 
Python 3, MarkupSafe compiles without error.


I first installed X and assumed the problem was related to the note in 
the Python 3 documentation as reinstalling Python 3 fixes the problem.  
Everything else installed flawlessly and I've run BLFS 9.0 since the day 
of release.  So this is not a problem, but I would be interested in 
knowing what I've done wrong to receive the error.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Installing Python modules in BLFS - BLFS 9.0/development

[rhubarbpieguy--- via blfs-support]

Although Python 3 is now installed in LFS, it appears necessary to 
reinstall Python 3 in BLFS to install Python modules.  From the Python 3 
documentation:


   "Python 3 was installed in LFS.  The only reason to install it here 
is if optional modules are needed."


I understand the note, but a user following dependency links doesn't see 
it.  For instance, Mako is required for Mesa, but the Mako link 
references the Mako page, which makes no mention of reinstalling Python 
3.  As Python 3 was installed in LFS, a user would have no reason to 
suspect Python 3 must be reinstalled.


Would it make sense to add a note to Python modules using python3 
indicating Python 3 must be reinstalled?


Is it practical to amend the Python 3 LFS procedures to eliminate 
reinstalling Python 3 in BLFS?  That would eliminate the need for notes 
in BLFS and the Python 3 documentation.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Minor documentation typo -D=LLVM_ENABLE_RTTI=ON - BLFS 9.0/development

[rhubarbpieguy--- via blfs-support]

The LLVM-8.0.1 documentation lists -D=LLVM_ENABLE_RTTI=ON in the Command 
Explanations section.  I believe it should be -DLLVM_ENABLE_RTTI=ON.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Bluetooth keyboard bluez configuration. AutoEnable, timeouts? - BLFS 8.4

[rhubarbpieguy via blfs-support]

I'm attempting to use a ThinkPad bluetooth external keyboard with my 
BLFS 8.4 build.  I can access it using bluetoothctl with the following:


   power on

   agent KeyboardOnly

   default-agent

   pairable on

   scan on

   pair 90:7F:61:2A:CD:42

   trust 90:7F:61:2A:CD:42

   connect 90:7F:61:2A:CD:42

   quit

Unfortunately, I find the keyboard tends to time out.  I've set 
DiscoverableTimeout and PairableTimeout to 0 in /etc/bluetooth/main.conf.


I also find the keyboard isn't automatically enabled after rebooting or 
recovering from pm-hibernate.  I've set AutoEnable to true in 
/etc/bluetooth/main.conf.


Are there other settings I'm missing?  Is the problem perhaps with dbus 
and not bluez?


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Rustc documentation - "Unusually, a DESTDIR-style method is being used to install this package."

[rhubarbpieguy via blfs-support]

On 5/27/19 10:29 AM, Eric via blfs-support wrote:

On Mon, 27 May 2019 14:42:26 +0200, Pierre Labastie via blfs-support 
 wrote:

On 27/05/2019 13:58, rhubarbpieguy via blfs-support wrote:

The BLFS and development Rustc documentation states the following:

    Unusually, a DESTDIR-style method is being used to install this
i   package.

A small matter perhaps, but should it be:

    Usually, a DESTDIR-style method is used to install this package.


Not sure about English, but the intended meaning is that the use of a
DESTDIR-style method is rather unusual in the BLFS book.

That's what I took it to mean (I am a native English speaker). The OP's
suggestion does not seem correct to me. If you want to change it, I
think

  Unusually for BLFS, we use a DESTDIR-style method to install this
  package.

Though I would be interested to know why.

Eric



After I reread the passage I understand and agree with you and Pierre.  
As I mentioned, it's a minor point but I might suggest:


   We use a DESTDIR-stype method to install this, which is unusual for 
BLFS.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Rustc documentation - "Unusually, a DESTDIR-style method is being used to install this package."

[rhubarbpieguy via blfs-support]

The BLFS and development Rustc documentation states the following:

   Unusually, a DESTDIR-style method is being used to install this package.

A small matter perhaps, but should it be:

   Usually, a DESTDIR-style method is used to install this package.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] D-bus error with bluetoothctl

[rhubarbpieguy via blfs-support]

When attempting to run bluetoothctl I receive the following:

Waiting to connect to bluetoothd...dbus[11864]: arguments to 
dbus_connection_get_object_path_data() were incorrect, assertion "connection != 
NULL" failed in file dbus-connection.c line 5905.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace

I've compiled D-Bus but see no rdynamic configure option.  What should I check?

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] BlueZ with bluetooth keyboard

[rhubarbpieguy via blfs-support]

I'm attempting to use a bluetooth keyboard and assume I need BlueZ.  
I've compiled it and see no errors but have problems/questions.


Most step-by-step instructions I've found use hcitool, hciconfig and 
such, but it appears those no longer exist.  Correct?


I'm confused by bluemoon and bluetoothctl.  Typing bluemoon returns 
"Bluemoon configuration utility ver 5.50" but I don't know the 
keyboard's MAC address.  Bluetoothctl returns "D-Bus not built with 
'rdynamic so unable to print a backtrace" and things are aborted.  But 
if I missed something with D-Bus I'm not seeing it.


It seems this should be pretty simple but I'm making a royal mess of 
it.  Have I done something wrong to receive the backtrace message?


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] BLFS 8.4 - Firefox 65.0.1 showing up as Nightly on my system

[rhubarbpieguy via blfs-support]

On 3/9/19 11:17 AM, Douglas R. Reno via blfs-support wrote:

Good morning (or afternoon),

I setup a build of Firefox to run overnight on one of my 8.4 systems. 
Using my pre-existing script and mozconfig, which worked for 8.4's 
release testing to give me a Firefox Quantum install, gave me a 
Firefox Nightly install, in which the commands after ./mach install 
don't work because /usr/lib/firefox/ doesn't exist.


Grepping my log somehow shows that it picked up that it was supposed 
to be part of the nightly channel, so I'll rebuild Firefox without a 
script and see what happens. My question is though...


Has anyone ever encountered this, and how does it happen? Does Firefox 
assume that it's nightly if it has a problem with the mozconfig or 
something of that nature?


Have you commented out "ac_add_options --enable-official-branding" in 
your mozconfig file?  I should mention I've not compiled Firefox for 
BLFS 8.4.  However, if memory serves, I once played with that option and 
received "Nightly."



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Xorg Intel Driver documentation - BLFS 8.3/development

[rhubarbpieguy via blfs-support]

In November of 2018 a thread addressed the Intel I810 driver in the Intel 
Driver documentation.  I810 references were removed from the menu configuration 
section but the following remains:

   "Enable the following options in the kernel configuration.  Only one
   of the lines "Intel I810" or "Intel 8xx/9xx..." needs to be
   selected.  If you select the latter, "Enable modesetting..." is
   needed too.  Recompile the kernel if necessary:"

It was suggested everything after the first sentence above should be deleted, 
which makes sense to me, perhaps also the first sentence.  However, I just 
checked the development documentation and it remains.  Shouldn't the above line 
be modified?

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Thin vertical line with X.

[rhubarbpieguy via blfs-support]

I've developed a thin vertical line about three quarters to the right of 
my screen.  Frankly, I'm uncertain this is a BLFS question as I 
considered it a hardware problem but ...


My old box ran BLFS 8.2 and developed an identical problem.  As a 
result, I replaced it with my current box (BLFS 8.3) , which just 
developed the same line.  It seems highly unlikely I'd develop the same 
hardware problem on two entirely different boxes.  My old box was a 
laptop while my current is a desktop with an external monitor.


Might the Intel driver be the problem?  What should I check?


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Xorg Intel Driver-20180223 Kernal Configuration. - BLFS 8.3/development

[rhubarbpieguy via blfs-support]

I honestly think it'd be smart to pull up the Kernel Configuration 
section in the Index and verify that every package that has special 
kernel configuration hasn't had it's options moved.


We need a volunteer for that.  The current editors' plates are 
pretty full.


  -- Bruce



I realize you're probably looking for something more sophisticated, 
but I compared the documentation against the kernel menu.  I believe 
I found the following:



                 documentation                 kernel menu


autofs

                 Kernel automounter version 4 support (also 
supports v3)                        Kernel automounter support 
(supports v3, v4 and v5)


                 CIFS support (advanced network filesystem, SMBFS 
successor)          non-existent?



bluez          Should RFCOMM TTV support, Multicast Filter support, 
and Protocol filter support be indented for consistency?



sane - The documentation mentions Kernel Configuration but none seems 
to exist.  Should that be stricken from the documentation?


The kernel menu does list several modules as (NEW), which the 
documentation does not.  I ignored that and the modules in brackets 
in the documentation, which I consider a nice touch.


That's helpful.  Did you find any discrepancies in the CONFIG_* 
listings?  Those cna be useful in menuconfig if you are searching for 
an item or want to find out more info about an option.


  -- Bruce



I hope I understand your question.  Using the 4.19.6 kernel and 12/03/18 
development documentation I checked all occurences of [CONFIG_*]'s not 
listed in the .config file generated by 'make menuconfig' and found only 
the following:


CONFIG_INCOMP_PAR_MOD - introduction/conventions.html
CONFIG_OPT_PAR - introduction/conventions.html
CONFIG_REQU_PAR_MOD - introduction/conventions.html
CONFIG_REQU_PAR_NMOD - introduction/conventions.html

But as those are illustrative only they're probably not a big deal.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Xorg Intel Driver-20180223 Kernal Configuration. - BLFS 8.3/development

[rhubarbpieguy via blfs-support]

On 11/24/18 10:14 PM, Bruce Dubbs via blfs-support wrote:

On 11/24/2018 10:04 PM, renodr via blfs-support wrote:

On 2018-11-24 20:49, Bruce Dubbs via blfs-support wrote:

On 11/24/2018 06:25 PM, Ken Moffat via blfs-support wrote:
On Sat, Nov 24, 2018 at 11:33:35AM -0600, rhubarbpieguy via 
blfs-support wrote:


The Xorg Intel Driver-20180223 documentation states the following 
regarding

kernel configuration:

    Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs 
to be

    selected.

I see no "Intel i810" option with make menuconfig.

Also, "If you select the latter, “Enable modesetting...” is needed 
too."
confuses me.  I assume that refers to "Intel 8xx/9xx..." However, 
I don't
see that specific option, does it refer to 'Kernel modesetting 
driver for

MGA G200 server engines?'  I don't see another KMS option.



I'm not sure what happened to the I810, and not really interested -
it predated modern intel CPUs.


Agree.  We can probably just delete everything in that paragraph after
the first sentence.



I honestly think it'd be smart to pull up the Kernel Configuration 
section in the Index and verify that every package that has special 
kernel configuration hasn't had it's options moved.


We need a volunteer for that.  The current editors' plates are pretty 
full.


  -- Bruce



I realize you're probably looking for something more sophisticated, but 
I compared the documentation against the kernel menu.  I believe I found 
the following:



                    documentation                 kernel menu


autofs

                    Kernel automounter version 4 support (also supports 
v3)                        Kernel automounter support (supports v3, v4 
and v5)


                    CIFS support (advanced network filesystem, SMBFS 
successor)          non-existent?



bluez          Should RFCOMM TTV support, Multicast Filter support, and 
Protocol filter support be indented for consistency?



sane - The documentation mentions Kernel Configuration but none seems to 
exist.  Should that be stricken from the documentation?


The kernel menu does list several modules as (NEW), which the 
documentation does not.  I ignored that and the modules in brackets in 
the documentation, which I consider a nice touch.




--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Xorg Intel Driver-20180223 Kernal Configuration. - BLFS 8.3/development

[rhubarbpieguy via blfs-support]

The Xorg Intel Driver-20180223 documentation states the following 
regarding kernel configuration:


   Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs to be
   selected.

I see no "Intel i810" option with make menuconfig.

Also, "If you select the latter, “Enable modesetting...” is needed too." 
confuses me.  I assume that refers to "Intel 8xx/9xx..."  However, I 
don't see that specific option, does it refer to 'Kernel modesetting 
driver for MGA G200 server engines?'  I don't see another KMS option.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] JS-52.2.1gnome1 "If installing in the chroot environment, be sure to export the SHELL environment variable or configuration of the package will fail" - BLFS 8.3

[rhubarbpieguy via blfs-support]

The JS-52.2.1gnome1 documentation states the following.

   "If installing in the chroot environment, be sure to export the
   |SHELL| environment variable or configuration of the package will fail"

That's good, but would it make sense to change it to:

   "If you are compiling JS in chroot, make sure you have |$SHELL|
   environment variable set or prepend |SHELL=/bin/sh"|

|A minor point, but the change would put it in line with Firefox and 
Thunderbird and is more explicit.  Just a thought.

|
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3 [solved]

[rhubarbpieguy via blfs-support]

My problem was caused by incorrectly configuring xorgproto.  I typed 
'meson --prefix=/$XORG_PREFIX ..' instead of 'meson 
--prefix=$XORG_PREFIX ..'  The slash caused //usr when compiling. 
Unfortunately, it didn't seem to cause an error message but caused 
problems when compiling Poppler.


When I successfully compiled poppler-0.67.0 on my BLFS 8.2 system it was 
apparent I'd made a mistake on my BLFS 8.3 system.  The problem was 
right in front of me but I was blind to it.  Ah well ...  Perhaps 
posting the solution will help someone down the line.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

[rhubarbpieguy via blfs-support]

On 10/15/18 7:45 PM, Michael Shell via blfs-support wrote:

In the meantime, Bruce and rhubarbpieguy, what version of cmake are
each of you running?

cmake --version


rhubarbpieguy, can you try a 0.67 build with the two patches:

patch -p1 -i ../poppler_fix_cmake_gtk3_include_dir.patch
patch -p1 -i ../poppler_gtk-test_force_build_fail.patch

mkdir build
cdbuild
cmake  -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr 
-DTESTDATADIR=$PWD/testfiles -DENABLE_XPDF_HEADERS=ON ..
make VERBOSE=1

and show me the c++ line that fails? This way, I can see how gcc is
being called on your system after the poppler GTK cmake code bug is
fixed.

Also, please verify for me again that none of the include variables
are being set:

echo $CPLUS_INCLUDE_PATH
echo $C_INCLUDE_PATH
echo $CPATH
echo $GTK3_INCLUDE_DIRS
echo $GTK3_INCLUDE_DIR

rhubarbpieguy, do your recall doing/setting anything else with regard to
/usr/include in your /etc/profile, bashrc, anything in /etc/profile.d
including xorg.sh, or your .bashrc, .bash_profile, etc. ?

You can scan your entire /etc for all mentions of /usr/include by
running

find /etc -type f -print|sort|xargs grep /usr/include

as root. What does it show?


   Mike



Wowsers,  I remain impressed by your thoroughness!

--

My cmake version is 3.12.1.

--

[ 89%] Building CXX object test/CMakeFiles/gtk-test.dir/gtk-test.cc.o
cd /sources/poppler-0.62.0/build/test && /usr/bin/c++
-DUSE_OPENJPEG2 -I/sources/poppler-0.62.0
-I/sources/poppler-0.62.0/fof
-I/sources/poppler-0.62.0/goo
-I/sources/poppler-0.62.0/poppler
-I/sources/poppler-0.62.0/build
-I/sources/poppler-0.62.0/build/poppler
-I/sources/poppler-0.62.0/glib
-I/sources/poppler-0.62.0/build/glib
-I/usr/include/freetype2
-I/usr/include/openjpeg-2.3
-Wall -Wextra -Wpedantic
-Wno-unused-parameter
-Wno-missing-field-initializers
-Wcast-align -Wformat-security
-Wframe-larger-than=65536
-Wlogical-op
-Wmissing-format-attribute
-Wnon-virtual-dtor
-Woverloaded-virtual
-Wmissing-declarations
-Wundef
-Wsuggest-override
-fno-exceptions
-fno-check-new
-fno-common
-D_DEFAULT_SOURCE -O2 -DNDEBUG
-I/usr/include/nss
-I/usr/include/nspr
-pthread
-I/usr/include/gtk-3.0
-I/usr/include/at-spi2-atk/2.0
-I/usr/include/at-spi-2.0
-I/usr/include/dbus-1.0
-I/usr/lib/dbus-1.0/include
-I/usr/include/gtk-3.0
-I/usr/include/gio-unix-2.0/
-I/usr/include/cairo
-I/usr/include/libdrm
-I/usr/include/pango-1.0
-I/usr/include/fribidi
-I/usr/include/atk-1.0
-I/usr/include/cairo
-I/usr/include/pixman-1
-I/usr/include/uuid
-I/usr/include/freetype2
-I/usr/include/harfbuzz
-I/usr/include/libpng16
-I/usr/include/gdk-pixbuf-2.0
-I/usr/include/libpng16
-I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include
-I//usr/include
-pthread
-std=c++11 -o CMakeFiles/gtk-test.dir/gtk-test.cc.o -c 
/sources/poppler-0.62.0/test/gtk-test.cc
/sources/poppler-0.62.0/test/gtk-test.cc:24:10: fatal error: 
thisdoesnotexist.h: No such file or directory
 #include 
  ^~~~
compilation terminated.
make[2]: *** [test/CMakeFiles/gtk-test.dir/build.make:63: 
test/CMakeFiles/gtk-test.dir/gtk-test.cc.o] Error 1
make[2]: Leaving directory '/sources/poppler-0.62.0/build'
make[1]: *** [CMakeFiles/Makefile2:803: test/CMakeFiles/gtk-test.dir/all] Error 
2
make[1]: Leaving directory '/sources/poppler-0.62.0/build'
make: *** [Makefile:141: all] Error 2

-

None of the variables you questioned are set.  All come back blank.

--

find /etc -type f -print|sort|xargs grep /usr/include reports:

/etc/udev/hwdb.d/60-keyboard.hwdb:# is the bus-id (see 
/usr/include/linux/input.h BUS_*), ,  and
/etc/udev/hwdb.d/70-pointingstick.hwdb:# is the bus-id (see 
/usr/include/linux/input.h BUS_*), ,  and




--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

[rhubarbpieguy via blfs-support]

On 10/11/18 9:57 PM, Michael Shell via blfs-support wrote:

On Thu, 11 Oct 2018 17:58:44 -0500
rhubarbpieguy via blfs-support  
wrote:



I see two batches of Error 2 errors.  I hope this is what you want:

We want to see not just the error message, but the actual g++ command
line that caused the error.

When you build via:

make VERBOSE=1

you should be able to see all the gcc/g++ commands as they are being
executed, long lines like:

/usr/bin/c++  -DUSE_OPENJPEG2 -Dpoppler_EXPORTS -I

Do you see all that? The one that tries to compile gtk-test.cc
just before the error message is the one we are interested in.


   Cheers,

   Mike


That's clearer; I hope this is what you want.  I earlier referred to two 
batches of Error 2 errors, but I included the make install output by 
accident.



[ 89%] Building CXX object test/CMakeFiles/gtk-test.dir/gtk-test.cc.o
cd /sources/poppler-0.67.0/build/test && /usr/bin/c++ -DUSE_OPENJPEG2 
-I/sources/poppler-0.67.0 -I/sources/poppler-0.67.0/fofi 
-I/sources/poppler-0.67.0/goo -I/sources/poppler-0.67.0/poppler 
-I/sources/poppler-0.67.0/build -I/sources/poppler-0.67.0/build/poppler 
-I/sources/poppler-0.67.0/glib -I/sources/poppler-0.67.0/build/glib 
-I/usr/include/openjpeg-2.3 -isystem /usr/include/freetype2 -isystem 
/usr/include/gtk-3.0 -isystem /usr/include/at-spi2-atk/2.0 -isystem 
/usr/include/at-spi-2.0 -isystem /usr/include/dbus-1.0 -isystem 
/usr/lib/dbus-1.0/include -isystem /usr/include/gio-unix-2.0 -isystem 
/usr/include/cairo -isystem /usr/include/libdrm -isystem 
/usr/include/pango-1.0 -isystem /usr/include/fribidi -isystem 
/usr/include/atk-1.0 -isystem /usr/include/pixman-1 -isystem 
/usr/include/uuid -isystem /usr/include/harfbuzz -isystem 
/usr/include/libpng16 -isystem /usr/include/gdk-pixbuf-2.0 -isystem 
/usr/include/glib-2.0 -isystem /usr/lib/glib-2.0/include -isystem 
//usr/include  -Wall -Wextra -Wpedantic -Wno-unused-parameter 
-Wcast-align -Wformat-security -Wframe-larger-than=65536 -Wlogical-op 
-Wmissing-format-attribute -Wnon-virtual-dtor -Woverloaded-virtual 
-Wmissing-declarations -Wundef -Wzero-as-null-pointer-constant 
-Wsuggest-override -fno-exceptions -fno-check-new -fno-common 
-D_DEFAULT_SOURCE -O2 -DNDEBUG -I/usr/include/nss -I/usr/include/nspr 
-pthread -std=c++11 -o CMakeFiles/gtk-test.dir/gtk-test.cc.o -c 
/sources/poppler-0.67.0/test/gtk-test.cc

In file included from /usr/include/c++/8.2.0/ext/string_conversions.h:41,
 from /usr/include/c++/8.2.0/bits/basic_string.h:6391,
 from /usr/include/c++/8.2.0/string:52,
 from /sources/poppler-0.67.0/goo/GooString.h:42,
 from /sources/poppler-0.67.0/poppler/Object.h:45,
 from /sources/poppler-0.67.0/poppler/GfxState.h:43,
 from /sources/poppler-0.67.0/splash/SplashBitmap.h:39,
 from /sources/poppler-0.67.0/test/gtk-test.cc:9:
/usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such 
file or directory

 #include_next 
   ^~
compilation terminated.
make[2]: *** [test/CMakeFiles/gtk-test.dir/build.make:63: 
test/CMakeFiles/gtk-test.dir/gtk-test.cc.o] Error 1

make[2]: Leaving directory '/sources/poppler-0.67.0/build'
make[1]: *** [CMakeFiles/Makefile2:803: 
test/CMakeFiles/gtk-test.dir/all] Error 2

make[1]: Leaving directory '/sources/poppler-0.67.0/build'
make: *** [Makefile:141: all] Error 2


The first occurrence I see of Dpoppler prior to the error is as follows:

[ 79%] Building CXX object 
glib/CMakeFiles/poppler-glib.dir/__/poppler/CairoRescaleBox.cc.o
cd /sources/poppler-0.67.0/build/glib && /usr/bin/c++ 
-DG_LOG_DOMAIN=\"Poppler\" -DUSE_OPENJPEG2 -Dpoppler_glib_EXPORTS 
-I/sources/poppler-0.67.0 -I/sources/poppler-0.67.0/fofi 
-I/sources/poppler-0.67.0/goo -I/sources/poppler-0.67.0/poppler 
-I/sources/poppler-0.67.0/build -I/sources/poppler-0.67.0/build/poppler 
-I/sources/poppler-0.67.0/glib -I/sources/poppler-0.67.0/build/glib 
-I/usr/include/freetype2 -I/usr/include/openjpeg-2.3 -isystem 
/usr/include/glib-2.0 -isystem /usr/lib/glib-2.0/include -isystem 
/usr/include/cairo -Wall -Wextra -Wpedantic -Wno-unused-parameter 
-Wcast-align -Wformat-security -Wframe-larger-than=65536 -Wlogical-op 
-Wmissing-format-attribute -Wnon-virtual-dtor -Woverloaded-virtual 
-Wmissing-declarations -Wundef -Wzero-as-null-pointer-constant 
-Wsuggest-override -fno-exceptions -fno-check-new -fno-common 
-D_DEFAULT_SOURCE -O2 -DNDEBUG  -fPIC   -I/usr/include/nss 
-I/usr/include/nspr -pthread  -DG_DISABLE_DEPRECATED 
-DG_DISABLE_SINGLE_INCLUDES -pthread -std=c++11 -o 
CMakeFiles/poppler-glib.dir/__/poppler/CairoRescaleBox.cc.o -c 
/sources/poppler-0.67.0/poppler/CairoRescaleBox.cc


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

[rhubarbpieguy via blfs-support]

On 10/10/18 11:55 PM, Michael Shell via blfs-support wrote:


Could you paste the gcc/g++ commands just before and after the
build failure occurred so we can see what command line options
gcc/g++ was invoked with when attempting to build gtk-test.cc?




I see two batches of Error 2 errors.  I hope this is what you want:



In file included from /usr/include/c++/8.2.0/ext/string_conversions.h:41,
 from /usr/include/c++/8.2.0/bits/basic_string.h:6391,
 from /usr/include/c++/8.2.0/string:52,
 from /sources/poppler-0.67.0/goo/GooString.h:42,
 from /sources/poppler-0.67.0/poppler/Object.h:45,
 from /sources/poppler-0.67.0/poppler/GfxState.h:43,
 from /sources/poppler-0.67.0/splash/SplashBitmap.h:39,
 from /sources/poppler-0.67.0/test/gtk-test.cc:9:
/usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such file or 
directory
 #include_next 
   ^~
compilation terminated.
make[2]: *** [test/CMakeFiles/gtk-test.dir/build.make:63: 
test/CMakeFiles/gtk-test.dir/gtk-test.cc.o] Error 1
make[2]: Leaving directory '/sources/poppler-0.67.0/build'
make[1]: *** [CMakeFiles/Makefile2:803: test/CMakeFiles/gtk-test.dir/all] Error 
2
make[1]: Leaving directory '/sources/poppler-0.67.0/build'
make: *** [Makefile:141: all] Error 2

--

[ 89%] Building CXX object test/CMakeFiles/gtk-test.dir/gtk-test.cc.o
In file included from /usr/include/c++/8.2.0/ext/string_conversions.h:41,
 from /usr/include/c++/8.2.0/bits/basic_string.h:6391,
 from /usr/include/c++/8.2.0/string:52,
 from /sources/poppler-0.67.0/goo/GooString.h:42,
 from /sources/poppler-0.67.0/poppler/Object.h:45,
 from /sources/poppler-0.67.0/poppler/GfxState.h:43,
 from /sources/poppler-0.67.0/splash/SplashBitmap.h:39,
 from /sources/poppler-0.67.0/test/gtk-test.cc:9:
/usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such file or 
directory
 #include_next 
   ^~
compilation terminated.
make[2]: *** [test/CMakeFiles/gtk-test.dir/build.make:63: 
test/CMakeFiles/gtk-test.dir/gtk-test.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:803: test/CMakeFiles/gtk-test.dir/all] Error 
2
make: *** [Makefile:141: all] Error 2

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

[rhubarbpieguy via blfs-support]

The attached patch reverts what I think is your trouble maker. Apply
it to 0.63.0 and later (it should work with 0.69.0 as well) using:

patch -p1 -i ../poppler_revert_gtk3_include_dirs.patch

And let us know if you can build 0.63.0 and later after applying
the patch.


   Cheers,

   Mike



Good news.  I applied the patch to poppler-0.63.0 and poppler-0.67.0.  
Both compiled successfully.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

[rhubarbpieguy via blfs-support]

On 10/9/18 4:21 AM, Michael Shell via blfs-support wrote:


Can you compile Poppler-0.67.0 on your gcc 8.2.0 system *if*
$CPLUS_INCLUDE_PATH and/or $C_INCLUDE_PATH are *not* set (don't have
any pathappend lines in /etc/profile.d/xorg.sh, unset/clear
C_INCLUDE_PATH CPLUS_INCLUDE_PATH, and restart x) and thus your gcc's search
paths are as you stated (quoted at the end of this post)?

If yes, then I sure don't think you should be setting $CPLUS_INCLUDE_PATH
et al. Note that in the Xorg-7 instructions:





I think I may have been unclear through my numerous posts.  I've never 
set $CPLUS_INCLUDE_PATH and/or $C_INCLUDE_PATH as I compile X in /usr.  
My original (and current) problem is Poppler-0.67.0 won't compile and 
those variables are not set.  I only set them as I thought you wanted 
that as a test.


Unfortunately, Poppler-0.63.0 fails the same as Poppler-0.67.0. 
Poppler-0.62.0 compiles successfully on my BLFS 8.3 build but any 
version above that fails.  I'm still surprised Poppler-0.67.0 compiles 
successfully on my BLFS 8.2 build, 'pdfdetach --version' shows 0.67.0.


If you've other thoughts I'm happy to test.  However, again, I'm by no 
means dead in the water.  EpdfView works quite well with poppler-0.62.0 
and nothing else seems affected by whatever I've done to affect 
Poppler.  Your help is always appreciated but don't knock yourself out.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

[rhubarbpieguy via blfs-support]

On 10/7/18 10:31 PM, Ken Moffat via blfs-support wrote:

On Sat, Oct 06, 2018 at 08:52:26AM -0500, rhubarbpieguy via blfs-support wrote:

  Again, I should mention Poppler
was the only problem package and the older version works well, but it would
be nice to know what I've done wrong.


(replying to this particular post because I could not see anywhere
obvious to put this) -

I'm starting to wonder if you built extra (qt) packages before
poppler in 8.3.  One of google's matches for the include_next problem
noted that a .pro file from something had a line

  INCLUDEPATH += /usr/include

and removing that line allowed the affected package (not poppler) to
build.

So, find what '*.pro' files you have, and edit any INCLUDEPATH lines
like that (or, better, copy the file(s) to something.pro.bak and
then change the .pro).

ĸen



I've compiled no qt packages to my knowledge.  I have no *.pro files if 
I understand the question correctly.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

[rhubarbpieguy via blfs-support]

"Without any CPLUS_INCLUDE_PATH etc. variables set, can you build 
poppler 0.62 on the gcc 8.2.0 system?"


-

I misread your above question as I saw 8.2 and thought you meant BLFS 
8.2.  I reported running Poppler 0.62 on my BLFS 8.3/gcc 8.2.0 system 
previously.  I'm using EpdfView with Poppler 0.62 currently.


However, (what the heck), I thought I'd attempt compiling Poppler 0.67 
(BLFS 8.3 version) on my BLFS 8.2 build.  To my surprise, It compiled 
successfully.  So, I can compile Poppler 0.67 on BLFS 8.2/gcc 7.3 but 
not on BLFS 8.3/gcc 8.2.  I've apparently done something wrong with BLFS 
8.3 but am a loss as why it affects only Poppler.


I also ran your commands on my BLFS 8.2/gcc 7.3 build.

-
`gcc -print-prog-name=cc1plus` -v

ignoring nonexistent directory 
"/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../include/c++/7.3.0
 
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../include/c++/7.3.0/x86_64-pc-linux-gnu
 /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../include/c++/7.3.0/backward
 /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include
 /usr/local/include
 /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include-fixed
 /usr/include

ignoring nonexistent directory 
"/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0
 
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0/x86_64-pc-linux-gnu
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0/backward
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include
 /usr/local/include
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include-fixed
 /usr/include

-
`gcc -print-prog-name=cc1` -v

ignoring nonexistent directory 
"/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include
 /usr/local/include
 /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include-fixed
 /usr/include

ignoring nonexistent directory 
"/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include
 /usr/local/include
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include-fixed
 /usr/include

--

Ken raised the cmake question earlier.  I used the cmake commands from 
the documentation and OpenJPEG (which compiled successfully) uses 
cmake.  I know little of cmake but want to make certain there's not 
something in his post I didn't understand.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] MarkupSafe/Beaker/Mako ModuleNotFoundError: No module named 'html' - BLFS 8.3

[rhubarbpieguy via blfs-support]

I remember receiving "ModuleNotFoundError: No module named 'html' for 
the MarkupSafe, Beaker, and Mako Python 3 modules when compiling X.  I 
put the problem on the back burner as those modules compiled for Python 
2 without error so Mesa subsequently compiled.


However, now that I've finished BLFS 8.3 to my satisfaction, I find I 
can compile all three without error.  Assuming a faulty memory, I 
restored my LFS 8.3 image and again compiled X.  I received the same errors.


So did I make an error compiling X?  X seems to be working well. I also 
tested the modules after compiling my post-X optional packages.  I 
assumed I could isolate the package that fixed the problem, but haven't 
caught it.


In summary, I don't know why I receive the error when compiling X and 
don't know why they compile without error now.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

[rhubarbpieguy via blfs-support]

On 10/5/18 1:55 AM, Michael Shell via blfs-support wrote:

On Thu, 4 Oct 2018 22:03:45 -0400
Michael Shell via blfs-support  wrote:


On your system, run these commands:

After helping Alex some more, these commands reveal info we need from
your system:


echo $CPLUS_INCLUDE_PATH
echo $C_INCLUDE_PATH
echo $CPATH
`gcc -print-prog-name=cc1plus` -v
`gcc -print-prog-name=cc1` -v
find /usr -name "stdlib.h"


You will have to press ctrl-C after the gcc lines to regain the
command prompt.


   Cheers,

   Mike



It appears setting the new variables didn't fix the problem.  I hope 
I've followed your and Ken's guidance correctly. Again, I should mention 
Poppler was the only problem package and the older version works well, 
but it would be nice to know what I've done wrong.  So ...


echo $CPLUS_INCLUDE_PATH - /usr/include
echo $C_INCLUDE_PATH - /usr/include
echo $CPATH - nothing returned

--

`gcc -print-prog-name-cc1plus` -v

ignoring nonexistent directory 
"/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/include"
ignoring duplicate directory "/usr/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/include
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0
 
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0/x86_64-pc-linux-gnu
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0/backward
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include
 /usr/local/include
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include-fixed
-

`gcc -print-prog-name=cc1` -v

ignoring nonexistent directory 
"/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/include"
ignoring duplicate directory "/usr/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/include
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include
 /usr/local/include
 /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include-fixed
-

find /usr -name "stdlib.h

/usr/include/bits/stdlib.h
/usr/include/c++/8.2.0/stdlib.h
/usr/include/c++/8.2.0/tr1/stdlib.h
/usr/include/stdlib.h
-  





	  


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

[rhubarbpieguy via blfs-support]

On 10/3/18 7:17 PM, Michael Shell via blfs-support wrote:

It seems another BLFS user has encountered this issue (but with
applications other than poppler):

http://lists.linuxfromscratch.org/pipermail/blfs-support/2018-October/080407.html

I also found this:

https://www.linuxquestions.org/questions/slackware-14/on-current-qt-include-directory-appears-2x-4175636463/

Check what the environment variable CPLUS_INCLUDE_PATH is being
set to and where it is being set:

echo $CPLUS_INCLUDE_PATH
grep -s CPLUS_INCLUDE_PATH /etc/*

Problems can occur here if a path is duplicated within $CPLUS_INCLUDE_PATH


  Cheers,

  Mike



Perhaps CPLUS_INCLUDE_PATH is the problem as I have no such variable.  
However, I'm confused, as the only reference I see in the documentation 
refers to installing X outside the standard prefix.  I install X using 
/usr, which I understood as the standard prefix.


What have I missed?  Is there another area where I'm to set 
CPLUS_INCLUDE_PATH?



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

[rhubarbpieguy via blfs-support]

On 9/25/18 4:08 PM, rhubarbpieguy wrote:


I receive the following error with the make and 'make install' Poppler 
commands.  Poppler-data installs without error.


/usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such 
file or directory

 #include_next 
   ^~
compilation terminated.
make[2]: *** [test/CMakeFiles/gtk-test.dir/build.make:63: 
test/CMakeFiles/gtk-test.dir/gtk-test.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:803: 
test/CMakeFiles/gtk-test.dir/all] Error 2

make: *** [Makefile:141: all] Error 2

I have an ASCII text /usr/include/c++/8.2.0/cstdlib (-rw-r--r-- 6325).




I tried other Poppler versions and found poppler-0.62.0 from BLFS 8.2 
compiled without error.  I first tried poppler-0.69.0, thinking a newer 
version might work, but it produced the same error as poppler-0.62.0.


Perhaps I made an error compiling LFS 8.3, but gcc compiled without 
error and I ran the tests.  In addition, LFS/BLFS 8.3 seems to be 
running quite well and Poppler is the only package that has given me grief.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

[rhubarbpieguy via blfs-support]

I receive the following error with the make and 'make install' Poppler 
commands.  Poppler-data installs without error.


/usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such 
file or directory

 #include_next 
   ^~
compilation terminated.
make[2]: *** [test/CMakeFiles/gtk-test.dir/build.make:63: 
test/CMakeFiles/gtk-test.dir/gtk-test.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:803: 
test/CMakeFiles/gtk-test.dir/all] Error 2

make: *** [Makefile:141: all] Error 2

I have an ASCII text /usr/include/c++/8.2.0/cstdlib (-rw-r--r-- 6325).


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Falkon?

[rhubarbpieguy]

As Qupzilla is now Falkon and part of KDE, will Falkon be in BLFS? I see 
only QupZilla in the development documentation.


I ask this mostly from curiosity.  I realize things take time.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] xdg-utils - config.status: WARNING: 'scripts/Makefile.in' seems to ignore the --datarootdir setting - BLFS 8.2

[rhubarbpieguy]

I receive "config.status: WARNING: 'scripts/Makefile.in' seems to ignore 
the --datarootdir setting" when compiling xdg-utils.  Can this error be 
ignored?


I also receive:

   xmlto: 
/compiler/xdg-utils-1.1.2/scripts/html/../desc/xdg-desktop-menu.xml does 
not validate (status 3)

   xmlto: Fix document syntax or use --skip-validation option

I don't understand what's causing the error and I see no 
'--skip-validation' configuration option in xdg-utils or xmlto. 
Where/how do I skip validation?  And if I do so, am I simply ignoring a 
problem?


I mistakenly though I fixed my xdg-utils problems but I'm struggling 
with the package.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] xdg-utils validation error? - BLFS 8.2

[rhubarbpieguy]

On 06/06/2018 10:33 PM, rhubarbpie...@gmail.com wrote:


I receive the following when compiling xdg-utils.  I've compiled xmlto 
and w3m.


checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for xmlto... /usr/bin/xmlto
configure: creating ./config.status
config.status: creating Makefile
config.status: creating scripts/Makefile
config.status: WARNING:  'scripts/Makefile.in' seems to ignore the 
--datarootdir setting

config.status: creating tests/Makefile
config.status: WARNING:  'tests/Makefile.in' seems to ignore the 
--datarootdir setting

config.status: creating autotests/Makefile
make[1]: Entering directory '/sources/xdg-utils-1.1.2/scripts'
(cd html;/usr/bin/xmlto html-nochunks ../desc/xdg-desktop-menu.xml)
xmlto: 
/sources/xdg-utils-1.1.2/scripts/html/../desc/xdg-desktop-menu.xml 
does not validate (status 3)

xmlto: Fix document syntax or use --skip-validation option
I/O error : Attempt to load network 
entityhttp://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
/sources/xdg-utils-1.1.2/scripts/html/../desc/xdg-desktop-menu.xml:6: 
warning: failed to load external 
entity"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd;

]>
  ^
I/O error : Attempt to load network 
entityhttp://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
warning: failed to load external 
entity"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd;
validity error : Could not load the external 
subset"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd;
Document 
/sources/xdg-utils-1.1.2/scripts/html/../desc/xdg-desktop-menu.xml 
does not validate

make[1]: *** [Makefile:111: html/xdg-desktop-menu.html] Error 13
make[1]: Leaving directory '/sources/xdg-utils-1.1.2/scripts'
make: *** [Makefile:25: scripts] Error 2
cd `dirname scripts/__install__` && make install
make[1]: Entering directory '/sources/xdg-utils-1.1.2/scripts'
mkdir -p /usr/bin
for x in xdg-desktop-menu xdg-desktop-icon xdg-mime xdg-icon-resource 
xdg-open xdg-email xdg-screensaver xdg-settings ; do \

    /usr/bin/install -c   $x /usr/bin ; \
done
/usr/bin/install: cannot stat 'xdg-desktop-menu': No such file or 
directory
/usr/bin/install: cannot stat 'xdg-desktop-icon': No such file or 
directory

/usr/bin/install: cannot stat 'xdg-mime': No such file or directory
/usr/bin/install: cannot stat 'xdg-icon-resource': No such file or 
directory

/usr/bin/install: cannot stat 'xdg-open': No such file or directory
/usr/bin/install: cannot stat 'xdg-email': No such file or directory
/usr/bin/install: cannot stat 'xdg-screensaver': No such file or 
directory

/usr/bin/install: cannot stat 'xdg-settings': No such file or directory
make[1]: *** [Makefile:62: install] Error 1
make[1]: Leaving directory '/sources/xdg-utils-1.1.2/scripts'
make: *** [Makefile:31: scripts/__install__] Error 2



It appears my problem was with docbook-xml, for after recompiling such 
xdg-utils compiled successfully.  Perhaps my error can help someone down 
the line.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Python module libxml2 needed by itstool? - BLFS 8.2

[rhubarbpieguy]

When compiling itstool in BLFS 8.2 I receive:

   checking for Python module libxml2... not found
   configure error: Python module libxml2 is needed to run this package

I'm confused as I don't see the Python module listed as a requirement.  
I see docbook (installed), which requires libxml2 (installed).  However, 
that libxml2 doesn't seem to be the Python module of the same name.


But after compiling the libxml2 Python module I still receive the errors 
listed above, although the module appeared to compile properly and I see 
the Installed Programs listed in Contents.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] xdg-utils validation error? - BLFS 8.2

[rhubarbpieguy]

I receive the following when compiling xdg-utils.  I've compiled xmlto 
and w3m.


checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for xmlto... /usr/bin/xmlto
configure: creating ./config.status
config.status: creating Makefile
config.status: creating scripts/Makefile
config.status: WARNING:  'scripts/Makefile.in' seems to ignore the 
--datarootdir setting
config.status: creating tests/Makefile
config.status: WARNING:  'tests/Makefile.in' seems to ignore the --datarootdir 
setting
config.status: creating autotests/Makefile
make[1]: Entering directory '/sources/xdg-utils-1.1.2/scripts'
(cd html;/usr/bin/xmlto html-nochunks ../desc/xdg-desktop-menu.xml)
xmlto: /sources/xdg-utils-1.1.2/scripts/html/../desc/xdg-desktop-menu.xml does 
not validate (status 3)
xmlto: Fix document syntax or use --skip-validation option
I/O error : Attempt to load network 
entityhttp://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
/sources/xdg-utils-1.1.2/scripts/html/../desc/xdg-desktop-menu.xml:6: warning: failed to 
load external entity"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd;
]>
  ^
I/O error : Attempt to load network 
entityhttp://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
warning: failed to load external 
entity"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd;
validity error : Could not load the external 
subset"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd;
Document /sources/xdg-utils-1.1.2/scripts/html/../desc/xdg-desktop-menu.xml 
does not validate
make[1]: *** [Makefile:111: html/xdg-desktop-menu.html] Error 13
make[1]: Leaving directory '/sources/xdg-utils-1.1.2/scripts'
make: *** [Makefile:25: scripts] Error 2
cd `dirname scripts/__install__` && make install
make[1]: Entering directory '/sources/xdg-utils-1.1.2/scripts'
mkdir -p /usr/bin
for x in xdg-desktop-menu xdg-desktop-icon xdg-mime xdg-icon-resource xdg-open 
xdg-email xdg-screensaver xdg-settings ; do \
/usr/bin/install -c   $x /usr/bin ; \
done
/usr/bin/install: cannot stat 'xdg-desktop-menu': No such file or directory
/usr/bin/install: cannot stat 'xdg-desktop-icon': No such file or directory
/usr/bin/install: cannot stat 'xdg-mime': No such file or directory
/usr/bin/install: cannot stat 'xdg-icon-resource': No such file or directory
/usr/bin/install: cannot stat 'xdg-open': No such file or directory
/usr/bin/install: cannot stat 'xdg-email': No such file or directory
/usr/bin/install: cannot stat 'xdg-screensaver': No such file or directory
/usr/bin/install: cannot stat 'xdg-settings': No such file or directory
make[1]: *** [Makefile:62: install] Error 1
make[1]: Leaving directory '/sources/xdg-utils-1.1.2/scripts'
make: *** [Makefile:31: scripts/__install__] Error 2

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] gtk+-2 required to compile Thunderbird? - BLFS 8.2/development

[rhubarbpieguy]

Compiling Thunderbird without gtk+-2 installed produces the following:

- 



DEBUG: configure:12485: checking for gtk+-2.0 >= 2.18.0 
gtk+-unix-print-2.0 glib-2.0 >= 2.22 gobject-2.0 gdk-x11-2.0
DEBUG: configure: error: Library requirements (gtk+-2.0 >= 2.18.0 
gtk+-unix-print-2.0 glib-2.0 >= 2.22 gobject-2.0 gdk-x11-2.0) not met; 
consider adjusting the PKG_CONFIG_PATH environment variable if your 
libraries are in a nonstandard prefix so pkg-config can find them.

ERROR: old-configure failed *** Fix above errors and then restart with\
"make -f client.mk build"
make[1]: *** [/sources/thunderbird-52.6.0/client.mk:362: configure] Error 1
make[1]: Leaving directory '/sources/thunderbird-52.6.0'
make: *** [client.mk:374: 
/sources/thunderbird-52.6.0/obj-x86_64-pc-linux-gnu/Makefile] Error 2


- 



Thunderbird compiles successfully after installing gtk+-2.  Firefox 
lists gtk+-2 as a requirement, should Thunderbird?  If not, is there 
something I've missed?



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] libxshmfence-1.2.tar.bz2 - BLFS 8.2

[rhubarbpieguy]

Compiling |libxshmfence-1.2.tar.bz2 fails during make.

|---
|

make  all-recursive
make[1]: Entering directory '/sources/libxshmfence-1.2'
Making all in src
make[2]: Entering directory '/sources/libxshmfence-1.2/src'
  CC   xshmfence_alloc.lo
xshmfence_alloc.c: In function 'xshmfence_alloc_shm':
xshmfence_alloc.c:73:7: error: implicit declaration of function 'memfd_create'; 
did you mean 'SYS_memfd_create'? [-Werror=implicit-function-declaration]
  fd = memfd_create("xshmfence", MFD_CLOEXEC|MFD_ALLOW_SEALING);
   ^~~~
   SYS_memfd_create
xshmfence_alloc.c:73:7: warning: nested extern declaration of 'memfd_create' 
[-Wnested-externs]
cc1: some warnings being treated as errors
make[2]: *** [Makefile:458: xshmfence_alloc.lo] Error 1
make[2]: Leaving directory '/sources/libxshmfence-1.2/src'
make[1]: *** [Makefile:486: all-recursive] Error 1
make[1]: Leaving directory '/sources/libxshmfence-1.2'
make: *** [Makefile:394: all] Error 2

-

This is new to me.  I have /usr/include/linux/memfd.h on both my working 8.1 
partition and my work-in-progress 8.2 attempt.  What might I have done wrong?

|
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Fluxbox "File format not recognized" - BLFS 8.1

[rhubarbpieguy]

I receive the following error when compiling Fluxbox-1.3.7:

make[2]: Entering directory '/sources/fluxbox-1.3.7'
g++  -g -O2-o fluxbox src/fluxbox-AlphaMenu.o src/fluxbox-ArrowButton.o 
src/fluxbox-AttentionNoticeHandler.o src/fluxbox-CascadePlacement.o 
src/fluxbox-ClientMenu.o src/fluxbox-ClientPattern.o 
src/fluxbox-ColSmartPlacement.o src/fluxbox-CommandDialog.o 
src/fluxbox-ConfigMenu.o src/fluxbox-CurrentWindowCmd.o src/fluxbox-FbAtoms.o 
src/fluxbox-FbCommands.o src/fluxbox-FbMenu.o src/fluxbox-FbMenuParser.o 
src/fluxbox-FbRootWindow.o src/fluxbox-FbWinFrame.o 
src/fluxbox-FbWinFrameTheme.o src/fluxbox-FocusControl.o 
src/fluxbox-FocusableList.o src/fluxbox-HeadArea.o src/fluxbox-IconButton.o 
src/fluxbox-IconbarTheme.o src/fluxbox-Keys.o src/fluxbox-LayerMenu.o 
src/fluxbox-MenuCreator.o src/fluxbox-MinOverlapPlacement.o 
src/fluxbox-OSDWindow.o src/fluxbox-Resources.o src/fluxbox-RootCmdMenuItem.o 
src/fluxbox-RootTheme.o src/fluxbox-RowSmartPlacement.o src/fluxbox-Screen.o 
src/fluxbox-ScreenPlacement.o src/fluxbox-ScreenResource.o 
src/fluxbox-SendToMenu.o src/fluxbox-StyleMenuItem.o src/fluxbox-TextDialog.o 
src/fluxbox-TooltipWindow.o src/fluxbox-UnderMousePlacement.o 
src/fluxbox-WinButton.o src/fluxbox-WinButtonTheme.o src/fluxbox-WinClient.o 
src/fluxbox-Window.o src/fluxbox-WindowCmd.o src/fluxbox-WindowState.o 
src/fluxbox-Workspace.o src/fluxbox-WorkspaceCmd.o src/fluxbox-WorkspaceMenu.o 
src/fluxbox-Xutil.o src/fluxbox-fluxbox.o src/fluxbox-main.o 
src/fluxbox-cli_cfiles.o src/fluxbox-cli_options.o src/fluxbox-cli_info.o 
src/fluxbox-Ewmh.o src/fluxbox-Remember.o src/fluxbox-Slit.o 
src/fluxbox-SlitClient.o src/fluxbox-SlitTheme.o src/fluxbox-ButtonTheme.o 
src/fluxbox-ButtonTool.o src/fluxbox-ClockTool.o src/fluxbox-GenericTool.o 
src/fluxbox-IconbarTool.o src/fluxbox-ToolFactory.o src/fluxbox-ToolTheme.o 
src/fluxbox-Toolbar.o src/fluxbox-ToolbarItem.o src/fluxbox-ToolbarTheme.o 
src/fluxbox-WorkspaceNameTool.o src/fluxbox-SystemTray.o libFbTk.a 
src/defaults.o -lfontconfig -lfreetype -lfreetype   -lXrandr -lXext -lXft 
-lXinerama -lXpm -lX11 -lXrender -lX11 -lX11  -lrt  -lm
src/defaults.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:2001: fluxbox] Error 1
make[2]: Leaving directory '/sources/fluxbox-1.3.7'
make[1]: *** [Makefile:4701: install-recursive] Error 1
make[1]: Leaving directory '/sources/fluxbox-1.3.7'
make: *** [Makefile:4999: install] Error 2

I'm running Fluxbox on a 64-bit machine but am receiving this error when 
compiling on an older 32-bit computer.  The configuration steps appear simple 
with the only requirement being X, which runs well with TWM.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Firefox 57 File/File Open screen placement. BLFS development

[rhubarbpieguy]

On 12/17/2017 06:03 PM, rhubarbpie...@gmail.com wrote:


When opening a file in Firefox 57 (File/File Open) the Open window isn't
positioned properly.  It's too high and the top of the window is cut off.

Firefox also won't open maximized.  I assume the problems are related.




Good news/bad news ...

I believe I fixed the problem of Firefox 57 not opening as maximized by 
nuking, then rebuilding ./mozilla/firefox.  It seems now to be 
consistently opening as maximized.


Unfortunately, the problems are probably not related as "File/File Open" 
still opens too high.  I doubt that's a BLFS problem and perhaps Firefox 
will fix it in a new release.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Firefox 57 File/File Open screen placement. BLFS development

[rhubarbpieguy]

When opening a file in Firefox 57 (File/File Open) the Open window isn't 
positioned properly.  It's too high and the top of the window is cut off.


Firefox also won't open maximized.  I assume the problems are related.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Firefox 57 undefined errors. - BLFS 8.1

[rhubarbpieguy]

I receive the following errors when compiling Firefox 57 with BLFS 8.1:

/sources/firefox-57.0/js/src/jsstr.cpp:1525: error: undefined reference 
to 'unorm2_normalizeSecondAndAppend_59'
/sources/firefox-57.0/js/src/jsstr.cpp:1534: error: undefined reference 
to 'unorm2_normalizeSecondAndAppend_59'
/sources/firefox-57.0/js/src/vm/Initialization.cpp:124: error: undefined 
reference to 'u_init_59'
/sources/firefox-57.0/js/src/vm/Initialization.cpp:189: error: undefined 
reference to 'u_cleanup_59'
/sources/firefox-57.0/js/src/vm/Initialization.cpp:215: error: undefined 
reference to 'u_setMemoryFunctions_59'

collect2: error: ld returned 1 exit status
make[5]: *** [/sources/firefox-57.0/config/rules.mk:722: libxul.so] Error 1
make[5]: Leaving directory 
'/sources/firefox-57.0/firefox-build-dir/toolkit/library'
make[4]: *** [/sources/firefox-57.0/config/recurse.mk:73: 
toolkit/library/target] Error 2

make[4]: Leaving directory '/sources/firefox-57.0/firefox-build-dir'
make[3]: *** [/sources/firefox-57.0/config/recurse.mk:33: compile] Error 2
make[3]: Leaving directory '/sources/firefox-57.0/firefox-build-dir'
make[2]: *** [/sources/firefox-57.0/config/rules.mk:452: default] Error 2
make[2]: Leaving directory '/sources/firefox-57.0/firefox-build-dir'
make[1]: *** [/sources/firefox-57.0/client.mk:424: realbuild] Error 2
make[1]: Leaving directory '/sources/firefox-57.0'
make: *** [client.mk:175: build] Error 2

The errors occur after 'make -f client.mk' and the undefined reference 
errors are rampant.


I'm currently running compiled Firefox-55.0.3 using BLFS 8.1 
documentation.  I updated libevent, nspr, nss, and sqlite but don't see 
what I'm doing wrong in compiling 57.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Flash Player-26.0.0.151 downloads. BLFS 8.1/Development

[rhubarbpieguy]

The NPAPI plugin for Gecko (Mozilla) and WebKit 64-bit download link 
produces the following:


   The requested URL
   /pub/flashplayer/pdc/26.0.0.151/flash_player_npapi_linux.x86_64.tar.gz
   was not found on this server.


In fact, all links but for Chromium Launcher seem unresponsive.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Midori keyboard shortcuts - BLFS 8.0

[rhubarbpieguy]

My shortcut key for the url bar doesn't work in Midori.  I'm uncertain 
whether Midori considers the Navigationbar or Location the url bar but 
I've tried both unsuccessfully.  And regardless of which I program, 
focus is first on the search bar and then the url bar if I press the key 
twice.  Focus should go directly to the url bar. Plus, the programmed 
key produces action only after Midori has started.  Once I've cycled 
through the two bars, pressing the programmed key produces nothing.


I believe I could assign a shortcut in BLFS 7.10.  Can others assign 
such in 8.0 and what does Midori consider the url bar in Shortcuts?

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] PyCairo-1.13.2 Python Modules development documentation.

[rhubarbpieguy]

The PyCairo development documentation in Python Modules section contains 
the following:


Cairo-1.14.8 
, *python* 
, 
and/or Python-3.6.1 



Should python be Python-2.7.13 for consistency? It does link to 
Python-2.7.13 but is it mislabeled?  And the link also moves to the body 
of the Python-2.7.13 documentation while all other links link to the 
beginning.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Occasional loss of sound. BLFS 8.0

[rhubarbpieguy]

I occasionally lose sound.  Alsamixer shows routine volume levels and 
nothing's muted.  The problem is infrequent and sound returns after an 
hour or so.


It's a minor problem, but I'd be interested in the cause and what I can 
do to correct the situation.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9

[rhubarbpieguy]

I have a correction to my 04/07/17 post.  /etc/fonts/local.conf with 
hintstyle set to hintfull can exist.  In fact, on my box it must exist 
for crisper fonts if /etc/fonts/conf.d/10-hinting-slight.conf is present.


However, the gist of the post was correct.  On my box, with or without 
10-hinting-slight.conf, $FREETYPE_PROPERTIES must be set, which was 
unnecessary with the 7.10 freetype version.  There may be different 
methods, but for me it's easiest to simply rename 10-hinting-slight.conf 
and set $FREETYPE_PROPERTIES without a local.conf file.




--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9

[rhubarbpieguy]

This problem returned in BLFS 8.0 but with a twist as neither method I 
used in 7.10 works.  But deleting/renaming 
/etc/fonts/conf.d/10-hinting-slight.conf plus adding the following to 
/etc/profile works:


   export FREETYPE_PROPERTIES="truetype:interpreter-version=35 
cff:no-stem-darkening=1 autofitter:warping=1"


The above works only without /etc/fonts/local.conf.

Again, this is not a BLFS problem.  It may be a freetype problem as the 
freetype version changed between 7.10 and 8.0.  It's posslble the 
interpreter line added to /etc/profile will be unnecessary with the next 
version.  I hope.


I'm probably in the minority but I greatly prefer the lighter, crisper, 
pre-10-hinting-slight.conf fonts.  There may be other ways to achieve 
them but the above method works well on my box.






--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] ACPI errors and 4.9.9 kernel. LFS 8.0

[rhubarbpieguy]

On 04/05/2017 05:44 PM, Bruce Dubbs wrote:

rhubarbpie...@gmail.com wrote:

On 04/04/2017 11:04 PM, Michael Shell wrote:

On Tue, 4 Apr 2017 10:43:29 -0500
Bruce Dubbs  wrote:


This is what I found via google:

https://access.redhat.com/articles/65378
https://forum.manjaro.org/t/acpi-error-on-boot-after-updating-to-4-9/12894 



And for me, this one:
https://bugzilla.kernel.org/show_bug.cgi?id=43229

It seems it is a BIOS problem, but OEMS are reluctant to fix things
like this, especially if MS Windows "works".

On the off chance it could get percolated up to the powers-that-be,
I would make sure that it still happens when running the latest BIOS
and then file a report with the motherboard maker.

In bugzilla URL above, there is a kernel patch:
https://bugzilla.kernel.org/attachment.cgi?id=99271=diff==1=raw 



that (re)enables support for the

libata.noacpi=1

kernel option (older kernels supported this option). Invoking that
option on boot will tell the kernel to ignore ACPI for the ATA devices.

Some people report that invoking that option improves drive performance
on boot (i.e., eliminating drive timeouts and reducing boot times) and
on wakeup:

https://bugzilla.redhat.com/show_bug.cgi?id=629315

I would invoke it on any system that is so improved.



Applying the patch with 'patch -p0 < ACPI.patch' produces: "can't find
file to patch at line 7"  Using 'patch -p1 < ACPI.patch" displays 
several

Hunk failures.

Can the patch not be used with 4.9.9 or am I doing something wrong?


Just go to linux-4.10.8.  The libata-acpi.c file looks quite a bit 
different and at least some of the patch is applied there.


  -- Bruce



I should have mentioned I'd tried 4.10.8 prior to posting without success.

I was unaware a patch can be partially applied.  Two of 6 Hunks succeed 
but the patched kernel also displays the errors.  Ah well.



-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] ACPI errors and 4.9.9 kernel. LFS 8.0

[rhubarbpieguy]

On 04/04/2017 11:04 PM, Michael Shell wrote:

On Tue, 4 Apr 2017 10:43:29 -0500
Bruce Dubbs  wrote:


This is what I found via google:

https://access.redhat.com/articles/65378
https://forum.manjaro.org/t/acpi-error-on-boot-after-updating-to-4-9/12894


And for me, this one:
https://bugzilla.kernel.org/show_bug.cgi?id=43229

It seems it is a BIOS problem, but OEMS are reluctant to fix things
like this, especially if MS Windows "works".

On the off chance it could get percolated up to the powers-that-be,
I would make sure that it still happens when running the latest BIOS
and then file a report with the motherboard maker.

In bugzilla URL above, there is a kernel patch:
https://bugzilla.kernel.org/attachment.cgi?id=99271=diff==1=raw
that (re)enables support for the

libata.noacpi=1

kernel option (older kernels supported this option). Invoking that
option on boot will tell the kernel to ignore ACPI for the ATA devices.

Some people report that invoking that option improves drive performance
on boot (i.e., eliminating drive timeouts and reducing boot times) and
on wakeup:

https://bugzilla.redhat.com/show_bug.cgi?id=629315

I would invoke it on any system that is so improved.


   Cheers,

   Mike Shell

Applying the patch with 'patch -p0 < ACPI.patch' produces: "can't find 
file to patch at line 7"  Using 'patch -p1 < ACPI.patch" displays 
several Hunk failures.


Can the patch not be used with 4.9.9 or am I doing something wrong?

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] ACPI errors and 4.9.9 kernel. LFS 8.0

[rhubarbpieguy]

On 04/03/2017 09:15 PM, Bruce Dubbs wrote:

rhubarbpie...@gmail.com wrote:

On 04/03/2017 05:01 PM, Bruce Dubbs wrote:

rhubarbpie...@gmail.com wrote:


Through LFS 7.10 I've suppressed ACPI errors with a 
/etc/sysctl.conf file

containing 'kernel.printk = 4.'

However, with LFS 8.0 and the 4.9.9 kernel the errors aren't 
suppressed.
Is this a kernel issue?  I see the following in Kernal 
Hacking/printk and

dmesg options  --->:

Default message log level (1-7) (NEW)

The default value is 4.  It seems that should make /etc/sysctl.conf
unnecessary.  But building the kernel with that value displays
never-ending ACPI errors, with or without /etc/sysctl.conf. This 
isn't a

significant problem as it occurs only in command line mode but it is
annoying.

If I boot my 8.0 build with the 7.10 kernel and /etc/sysctl.conf 
the ACPI

errors are suppressed.  That suggests there's not an error with my 8.0
build.  Logical?


You don't say if you are building sysv or systemd.  If sysv, edit
/etc/sysconfig/rc.site and change the line:

#LOGLEVEL=7

to

LOGLEVEL=4

The actual command is in /etc/init.d/rc

 dmesg -n "${LOGLEVEL:-7}"

If you prefer, you can also set LOGLEVEL in /etc/sysconfig/console.



I've built sysv and tried both methods but still receive the errors.  I
assume /etc/sysctl.conf is no longer needed and deleted it.


I don't ever recall seeing ACPI errors anyplace other than 
/var/log/Xorg.0.log.


However I do install ACPI and do not get any errors at all there.

What errors are you seeing?

  -- Bruce




I receive errors in kern.log, sys.log, and Xorg.o.log.

kern.log

ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.LGPA] (Node 
88017b06b168), AE_NOT_FOUND (20160831/psparse-543)
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.LEVN] (Node 
88017b06c7f8), AE_NOT_FOUND (20160831/psparse-543)
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECLV] (Node 
88017b06c758), AE_NOT_FOUND (20160831/psparse-543)
ACPI Error: Method parse/execution failed [\_GPE._L10] (Node 88017b06c820), 
AE_NOT_FOUND (20160831/psparse-543)
ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L10] 
(20160831/evgpe-646)
ACPI Error: [\_TZ_.THRM] Namespace lookup failure,

sys.log

ACPI Error: [\_TZ_.THRM] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.LGPA] (Node 
88017b06b168), AE_NOT_FOUND (20160831/psparse-543)
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.LEVN] (Node 
88017b06c7f8), AE_NOT_FOUND (20160831/psparse-543)

Xorg.0.log

[32.157] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or 
directory)

I believe they are box related as I'd also never had such errors.  I went from zero errors on my old box to numerous such - same release.  But they are suppressed with the older kernel.  


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] ACPI errors and 4.9.9 kernel. LFS 8.0

[rhubarbpieguy]

On 04/03/2017 05:01 PM, Bruce Dubbs wrote:

rhubarbpie...@gmail.com wrote:


Through LFS 7.10 I've suppressed ACPI errors with a /etc/sysctl.conf 
file

containing 'kernel.printk = 4.'

However, with LFS 8.0 and the 4.9.9 kernel the errors aren't suppressed.
Is this a kernel issue?  I see the following in Kernal Hacking/printk 
and

dmesg options  --->:

Default message log level (1-7) (NEW)

The default value is 4.  It seems that should make /etc/sysctl.conf
unnecessary.  But building the kernel with that value displays
never-ending ACPI errors, with or without /etc/sysctl.conf. This isn't a
significant problem as it occurs only in command line mode but it is
annoying.

If I boot my 8.0 build with the 7.10 kernel and /etc/sysctl.conf the 
ACPI

errors are suppressed.  That suggests there's not an error with my 8.0
build.  Logical?


You don't say if you are building sysv or systemd.  If sysv, edit 
/etc/sysconfig/rc.site and change the line:


#LOGLEVEL=7

to

LOGLEVEL=4

The actual command is in /etc/init.d/rc

 dmesg -n "${LOGLEVEL:-7}"

If you prefer, you can also set LOGLEVEL in /etc/sysconfig/console.

  -- Bruce

I've built sysv and tried both methods but still receive the errors.  I 
assume /etc/sysctl.conf is no longer needed and deleted it.



-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] ACPI errors and 4.9.9 kernel. LFS 8.0

[rhubarbpieguy]

Through LFS 7.10 I've suppressed ACPI errors with a /etc/sysctl.conf 
file containing 'kernel.printk = 4.'


However, with LFS 8.0 and the 4.9.9 kernel the errors aren't 
suppressed.  Is this a kernel issue?  I see the following in Kernal 
Hacking/printk and dmesg options  --->:


   Default message log level (1-7) (NEW)

The default value is 4.  It seems that should make /etc/sysctl.conf 
unnecessary.  But building the kernel with that value displays 
never-ending ACPI errors, with or without /etc/sysctl.conf.  This isn't 
a significant problem as it occurs only in command line mode but it is 
annoying.


If I boot my 8.0 build with the 7.10 kernel and /etc/sysctl.conf the 
ACPI errors are suppressed.  That suggests there's not an error with my 
8.0 build.  Logical?


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Qtwebkit - bash: qmake: command not found. BLFS 7.10/development

[rhubarbpieguy]

On the qt5 page:


cat > /etc/profile.d/qt5.sh << "EOF"
# Begin /etc/profile.d/qt5.sh

QT5DIR=/opt/qt5

pathappend $QT5DIR/bin   PATH
pathappend $QT5DIR/lib/pkgconfig PKG_CONFIG_PATH

export QT5DIR

# End /etc/profile.d/qt5.sh
EOF

You probably need to source that before building qtwebkit.

  -- Bruce


That certainly works, as does rebooting or a new login.  However, all 
three methods rely on a file generated when compiling qt. There's no 
mention of executing that file in the qt or QtWebKit documentation that 
I see.


It seems the documentation is missing a step like 
'PATH=$PATH:/usr/bin/qt5' or the opt equivalent if that option was 
chosen.  QtWebKit compiles for me with that step.  Without, qmake isn't 
found, even though I use 'SAVEPATH=$PATH' and 'export PATH=$PWD/bin:$PATH.'


What am I missing?
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Qtwebkit - bash: qmake: command not found. BLFS 7.10/development

[rhubarbpieguy]

On 01/28/2017 06:17 PM, Bruce Dubbs wrote:

rhubarbpie...@gmail.com wrote:


I receive 'bash: qmake: command not found' when compiling qtwebkit. I
compiled qt in /usr and /usr/bin/qt5/qmake exists.  Qtwebkit compiles 
if I

enter /usr/bin/qt5/qmake.

Also, I receive 'find: '/lib/pkgconfig': No such file or directory.'  My
$QT5PREFIX variable exists from compiling qt, but I have no $QT5DIR
variable and am confused where $QT5DIR is set. Setting QT5DIR to /usr
eliminates the pkgconfig error.

So, by using /usr/bin/qt5/qmake and setting QT5DIR to /usr qtwebkit
compiles successfully.  Where have I made a wrong turn?


Add /usr/bin/qt5 to your PATH.  I suspect you may also need to add 
/usr/lib/qt5 to /etc/ld/so.conf, but I'm not sure.


Note that I have no experience building qt in /usr.

  -- Bruce


I reinstalled qt from scratch in the recommended /opt/qt5 and received 
the same results.


I still don't see where QT5DIR is being set.  I wonder if that's meant 
to be QT5PREFIX, which is set in the qt documentation. Install 
Directories in the QtWebKit documentation refer to QT5PREFIX, not 
QT5DIR.  Regardless, should the variable be set in the QtWebKit 
documentation?


Again, I've successfully compiled qt under both methods but just don't 
understand my errors in qtwebkit.  I've successfully compiled qtwebkit 
under both methods using the minor adjustments I mentioned.  I did set 
QT5DIR to /opt/qt-5.7.0 with the /opt/qt5-5.7.0 method.


I realize /opt/qt5 is recommended, but /usr installation instructions 
are presented.  I chose /usr as the program I'm compiling complains with 
the /opt/qt5 option.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Qtwebkit - bash: qmake: command not found. BLFS 7.10/development

[rhubarbpieguy]

I receive 'bash: qmake: command not found' when compiling qtwebkit. I 
compiled qt in /usr and /usr/bin/qt5/qmake exists.  Qtwebkit compiles if 
I enter /usr/bin/qt5/qmake.


Also, I receive 'find: '/lib/pkgconfig': No such file or directory.'  My 
$QT5PREFIX variable exists from compiling qt, but I have no $QT5DIR 
variable and am confused where $QT5DIR is set. Setting QT5DIR to /usr 
eliminates the pkgconfig error.


So, by using /usr/bin/qt5/qmake and setting QT5DIR to /usr qtwebkit 
compiles successfully.  Where have I made a wrong turn?

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] BLFS 7.10 fonts less clear than in 7.9

[rhubarbpieguy]

I found simply deleting or renaming 
/etc/fonts/conf.d/10-hinting-slight.conf restores the less bold fonts I 
had in BLFS 7.9.  I believe another solution is to use the following 
code in /etc/fonts/local.conf:


 
  
   true
  
 
 
  
   hintfull
  
 

 
  
   false
  
 

This is not a BLFS problem and probably not a fontconfig-2.12.1 
problem.  But I prefer the clearer, less bold fonts of 
fontconfig-2.11.1.  There may be other ways but if this helps someone 
who also prefers the previous fonts - great.




--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Midori - opening images and reading html documentents locally. BLFS 7.10

[rhubarbpieguy]

On 10/02/2016 03:14 AM, Pierre Labastie wrote:

On 01/10/2016 21:46, rhubarbpie...@gmail.com wrote:


If I open a local jpg in Midori the image doesn't appear.  Instead, it looks
as if it opens in a text editor.  I've read Midori uses GIO and I have
compiled GConf.  I don't see a solution in Edit/Preferences/File Types.

Local html documents also appear as if opened in a text editor. However, html
documents opened at a url appear fine.  For instance, BLFS documentation read
online is fine, but downloaded documentation doesn't render properly.

Midori seems to compile and run well but I've apparently done something
wrong.  Are the problems related?

ISTR seeing this too. I do not remember exactly what it was, and I fear I have
not written what I did to fix it. Something to do with midori's or DM's file
associations. Or maybe just "update-mime-database"...

Pierre

Thank you, compiling shared-mime-info-1.6 and executing 
update-mime-database fixed the problem.


It's listed as a run time dependency for glib, which is required for 
gcr, which is required for Midori.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Midori - opening images and reading html documentents locally. BLFS 7.10

[rhubarbpieguy]

If I open a local jpg in Midori the image doesn't appear.  Instead, it 
looks as if it opens in a text editor.  I've read Midori uses GIO and I 
have compiled GConf.  I don't see a solution in Edit/Preferences/File Types.


Local html documents also appear as if opened in a text editor. However, 
html documents opened at a url appear fine.  For instance, BLFS 
documentation read online is fine, but downloaded documentation doesn't 
render properly.


Midori seems to compile and run well but I've apparently done something 
wrong.  Are the problems related?

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9.

[rhubarbpieguy]

True, a quick diff didn't highlight that.  My 7.10 desktop is
powered off at the moment, and those symlinks actually point to
/usr/share/fontconfig/conf.avail in my case - I looked at my
first-stage backups, in /staging on my server, but of course the
links are broken when I do that.

A (very) quick look yesterday suggested the symlinks on my 7.9 and
7.10 were the same, but I won't swear that they are (more than a
screenful using ls -l).

But - assuming all the 10-hinting* symlinks are present, the
contents of those files DID change between BLFS-7.9 and 7.10.

ĸen
The difference in /etc/fonts/conf.d between 7.9 and 7.10 builds on my 
box is 10-hinting-slight.conf.  7.10 includes it but 7.9 does not.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9.

[rhubarbpieguy]

On 09/23/2016 07:41 PM, Ken Moffat wrote:

On Thu, Sep 22, 2016 at 02:26:02PM -0500, rhubarbpie...@gmail.com wrote:

I thought fontconfig creates /etc/fonts/fonts.conf and the files differ
between 7.9 and 7.10.  In fact they differ significantly in size.  It seems
compiling fontconfig is pretty straightforward but I guess there could have
been an error I missed.  Replacing my BadFonts_7.10 /etc/fonts with my 7.9
version does fix the problem.


I've just had the opportunity to compare /etc/fonts/fonts.conf in
7.9 and 7.10.  Yes, they do differ in size by about 3.5K.  The
reason is that the table of valid blank characters almost at the end
of the file has been removed.

Previously I came across a reference to this table in the context
(some years and versions ago) of one of the Source Sans fonts being
treated by fontconfig as not usable for English (in that case, I
think it was missing both the caret and the back-tick, which I
interpreted to mean they were ostensibly present, but blank).

I'm puzzled why the absence of that table would alter things for an
English speaker running LFS - unless you are trying to use some
uncommon font (e.g. in your browser's preferences, if the browser is
where you noticed this) which used to be ignored because some other
characters were blank, but is now in use.

But diagnosing what happens in fontconfig seems to be painful.  The
link I found was, I think, in
https://eev.ee/blog/2015/05/20/i-stared-into-the-fontconfig-and-the-fontconfig-stared-back-at-me/
which also talks of using fc-match and pango-view to see which font
will be used for a particular codepoint, based on the font name you
pass and what is installed.  Unfortunately, I think the examples
used a smiley or other graphic character.  But perhaps the process
may be useful if you have both the 7.9 and 7.10 systems available.

ĸen
Thank you, your confirmation is helpful.  I probably should have been 
specific in the change in size (7.9/5464 / 7.10/2306) but assumed it was 
simply due to an error on my part.


I have nothing but serif, sans-serif, or monospace in my browser 
preferences.  I first noticed the font difference in my Fluxbox menu.  
That's what I've used as a reference when testing.


I still assume the problem is something I've done wrong in compiling X 
but just don't see it.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9.

[rhubarbpieguy]

On 09/21/2016 09:09 PM, Michael Shell wrote:

On Wed, 21 Sep 2016 16:30:57 -0500
rhubarbpie...@gmail.com  wrote:
  

antialias - Changing the antialias setting from 'true' to 'false' helped
significantly.  The fonts are just a touch 'blotchy' but the bold
problem is eliminated.  However, if I change /etc/fonts/local.conf to
include only an antialias setting the fonts are acceptable.

I'm surprised that a change in fontconfig is causing this. Most of the
time problems in this regard are caused by changes in freetype:

https://www.freetype.org/

Mote the changes they are doing all the time (e.g., 2.6.5 versus 2.7).

I've encountered a lot of freetype woes like what you are seeing
over the years.


Do you see any differences in /etc/fonts/fonts.conf, which is the system
default, for fontconfig? Are you running any of the /etc/fonts/conf.d
stuff in your startup files?

You can try creating copies of the fontconfig files:

cp -a /etc/fonts /etc/fonts-blfs7.9
or
cp -a /etc/fonts /etc/fonts-blfs7.10

and then overwriting a 7.10 /etc/fonts with that of 7.9 and see if that
corrects the problem with everything else being the same. If so, then
fontconfig did indeed change some of its defaults.

What are the two different versions of fontconfig you are using under
7.9 and 7.10?

Looking at the changelogs:

https://www.freedesktop.org/software/fontconfig/release/

The only thing that catches my eye for 2.12.1

https://www.freedesktop.org/software/fontconfig/release/ChangeLog-2.12.1

is at the end:

"Add --with-default-hinting to configure"


Are you sure that you are not running different versions of freetype
as opposed to fontconfig between your 7.9 and 7.10 systems?


   Cheers and thanks,

   Mike


I can't disagree with your logic.  I first suspected fontconfig as I 
deleted /etc/fonts/fonts.conf while wildly troubleshooting prior to 
posting and noticed the bold problem disappeared.  Unfortunately, 
deleting that causes other problems.


I thought fontconfig creates /etc/fonts/fonts.conf and the files differ 
between 7.9 and 7.10.  In fact they differ significantly in size.  It 
seems compiling fontconfig is pretty straightforward but I guess there 
could have been an error I missed.  Replacing my BadFonts_7.10 
/etc/fonts with my 7.9 version does fix the problem.


I also suspected freetype, but using the old fontconfig worked.  I don't 
understand how to get the freetype version, I see only freetype-config 
as the installed freetype program.


But if I understand your question, the versions for freetype and 
fontconfig in my 7.9, BadFonts7.9, and GoodFonts7.9 are:


7.9BadFonts_7.10 
GoodFonts_7.10

- --- -

freetype-config 18.3.12freetype-config 
18.5.12freetype-config 18.5.12
fontconfig   2.11.1fontconfig 
2.12.1fontconfig 2.11.1


I've not kept my 7.9 tarballs, but believe I used Freetype 2.63 and 
Freetype 2.65 with BLFS 7.10.  So, yes, I'm using different freetype 
versions between 7.9 and 7.10.  But I'm using the same Freetype between 
the good and bad fonts versions of 7.10.


I should probably clarify one thing.  While my spartan 
/etc/fonts/local.conf with only an antialias setting fixes the bold 
problem, my fonts with that fix are very slightly less clear than with 
my older fontconfig solution.


From checking your suggestions, the question to me is why my 
/etc/fonts/font.conf files differ so wildly between 7.9 and 7.10. I'll 
redo X tonight with special attention to my freetype and fontconfig 
compilations.  I must have made an error in one or both. Would an error 
with freetype affect fontconfig?






--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] LibreOffice-5.2.1 external/tarballs link commands. BLFS Development

[rhubarbpieguy]

Perhaps I'm reading this wrong, but it seems we have two too many ../'s 
in the following: install -dm755 external/tarballs && ln -sv 
../../../libreoffice-dictionaries-5.2.1.2.tar.xz external/tarballs/ && 
ln -sv ../../../libreoffice-help-5.2.1.2.tar.xz external/tarballs/


The documentation mentions the libreoffice-5.2.1.2 directory.  Should the lines 
be:

ln -sv ../libreoffice-dictionaries-5.2.1.2.tar.xz external/tarballs/ && 
ln -sv ../libreoffice-help-5.2.1.2.tar.xz external/tarballs/


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9.

[rhubarbpieguy]

For the lcdfilter, try lcdlight or lcdnone in place of lcddefault and see
what happens.

Please do let us know if you learn anything in this regard because
in the future others will probably run into the same problem.


Cheers,

Mike Shell
  
I admire your dedication to this and your concern to help those in the 
future.  My abilities are perhaps somewhat limited, but this is what 
I've found.


lcdfilter - Changing lcdfilter to lcdlight or lcdnone had no effect.

antialias - Changing the antialias setting from 'true' to 'false' helped 
significantly.  The fonts are just a touch 'blotchy' but the bold 
problem is eliminated.  However, if I change /etc/fonts/local.conf to 
include only an antialias setting the fonts are acceptable.






/usr/share/fonts


  
   false
  


My guess is my preference in fonts is less sophisticated than most, but 
I do like things simple.  It's good to know that if the next version of 
fontconfig again gives me excessive bold I can fix the problem with a 
simple /etc/fonts/local.conf.  I'll probably run with the old fontconfig 
and see what happens with the next release.  If there's something 
further you'd like me to test I'd be happy to do so.


-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Installing dejavu fonts - Xorg-7.7 Testing and Configuration. BLFS 7.10/BLFS Development

[rhubarbpieguy]

On 09/21/2016 12:50 PM, Paul J. Hentschel wrote:

rhubarbpie...@gmail.com wrote:

The documentation to install dejavu fonts states:



As a font installation example, consider the installation of the DejaVu
fonts. From the unpacked source directory, run the following commands as
the |root| user

install -v -d -m755 /usr/share/fonts/dejavu && install -v -m644 *.ttf
/usr/share/fonts/dejavu && fc-cache -v /usr/share/fonts/dejavu
---

The second line seems to imply the unpacked source directory is
dejavu-fonts-ttf-2.37/ttf.  Perhaps I don't understand, but isn't it
dejavu-fonts-ttf-2.37?

If so, should the line be 'install -v -m644 ttf/*.ttf
/usr/share/fonts/dejavu &&'?


No.

tar -xf dejavu-fonts-ttf-2.34.tar.bz2
cd dejavu-fonts-ttf-2.37<--   Just like every other package.
...

-- Bruce


I think the issue rhubarbpieguy  is pointing out is that the *.ttf files are
in a sub-directory (dejavu-fonts-ttf-2.37/ttf), but the install command in the
book is trying to copy them from the current directory (*.ttf instead of
ttf/*.ttf).

Paul



That's correct.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Installing dejavu fonts - Xorg-7.7 Testing and Configuration. BLFS 7.10/BLFS Development

[rhubarbpieguy]

The documentation to install dejavu fonts states:



As a font installation example, consider the installation of the DejaVu 
fonts. From the unpacked source directory, run the following commands as 
the |root| user


install -v -d -m755 /usr/share/fonts/dejavu && install -v -m644 *.ttf 
/usr/share/fonts/dejavu && fc-cache -v /usr/share/fonts/dejavu 
---


The second line seems to imply the unpacked source directory is 
dejavu-fonts-ttf-2.37/ttf.  Perhaps I don't understand, but isn't it 
dejavu-fonts-ttf-2.37?

If so, should the line be 'install -v -m644 ttf/*.ttf /usr/share/fonts/dejavu 
&&'?

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9.

[rhubarbpieguy]

On 09/19/2016 02:53 PM, Michael Shell wrote:

On Mon, 19 Sep 2016 19:29:19 +0100
Ken Moffat  wrote:


The internet has a plethora of suggestions for tweaking what happens
in fontconfig.

The quality of on-screen font rendering under Linux has long irked me.
It seems that after I finally get things the way I like, some upgrade
to Freetype or GTK comes along that breaks something. There have been
some really bad releases of Freetype in the past, IMHO.

Anyway, below is my /etc/fonts/local.conf receipe (I'm running Freetype
2.6.3 with Fontconfig-2.11.1) that I like best on my system (so far).
Note that I am unusual in that I use the venerable Type 1 Nimbus fonts
for default on screen rendering. Try my font config, rhubarb pie guy,
and let us know if you like it or if it helps at all. Be sure and
adjust the paths for your case as needed.

   Cheers,

   Mike Shell


Thank you for responding and I appreciate the config.conf.  Perhaps 
things differ by box, but your file accentuates what I got with the 
standard 7.10 fontconfig.  It produces fonts bolder than I like. That 
was the main problem with 7.10 and the new fontconfig; bold became 
bolder and less crisp.


I'll study your file as I've not used /etc/fonts/local.conf.  I've not 
noticed fontconfig messing up my fonts but perhaps it's been less severe 
than with the 7.10 fontconfig.  It's good to know I can fight back 
should the problem worsen with future versions of fontconfig.



--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] BLFS 7.10 fonts less clear than in 7.9.

[rhubarbpieguy]

I've run BLFS 7.10 for several days and noticed less clear fonts than 
with 7.9.  I reinstalled from square one without success and don't see 
my error.


As a test, I reinstalled BLFS 7.10, but with BLFS 7.9 dejavu and 
fontconfig packages (dejavu-fonts-ttf-2.35 and fontconfig-2.11.1) and my 
fonts are fine.  So I have a workable solution, but my fix is a 
workaround.  I've kept my bad fonts 7.10 build.  How can I pinpoint the 
problem?


I should mention my BLFS 7.10 fonts weren't terrible, but definitely 
less clear.  And again, my only deviation from the BLFS 7.10 
documentation was using 7.9 dejavu and fontconfig packages. It appears 
the procedures to compile each are unchanged from 7.9.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] libpng-1.6.24-apng.patch.gz problem - Development BLFS 2016-08-07

[rhubarbpieguy]

Attempting to apply libpng-1.6.24-apng.patch.gz with "gzip -cd 
../libpng-1.6.24.patch.gz | patch -p1" yields the following:


   can't find file to patch at input line 5
   Perhaps you used the wrong -p or --strip option?

I've also unzipped it manually and patched separately using "patch -Np1 
-i" with the same result.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Midori startup errors.

[rhubarbpieguy]

On 07/25/2016 03:55 PM, Douglas R. Reno wrote:

rhubarbpie...@gmail.com wrote:

On 07/25/2016 03:44 PM, Douglas R. Reno wrote:

rhubarbpie...@gmail.com wrote:

On 07/22/2016 05:38 PM, Douglas R. Reno wrote:

Bruce Dubbs wrote:

rhubarbpie...@gmail.com wrote:


I've recently compiled Midori and receive the following upon 
starting with

"midori":

GLib-GIO-Message: Using the 'memory GSettings backend. Your 
settings

will not be saved or shared with other applications.

(midori4:15329): Gtk-CRITICAL **: gtk_action_set_action_group:
assertion 'action_group == NULL' failed

I've compiled:

shared-mime-info
desktop-file-utils
gsettings-desktop-schemas

Other than the startup errors Midori seems to be performing 
well. Is DConf

necessary?


I think these messages show up from libraries if you are not 
running Gnome.  Douglas?


  -- Bruce

I'd try building DConf and try launching it again. That looks like 
it can't get to the backend to actually store the settings, 
therefore it runs it in memory instead of saving it.


I tried compiling DConf before posting and received the following 
during the make command:


I/O error : Attempt to load network 
entityhttp://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
warning: failed to load external 
entity"http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl;
cannot 
parsehttp://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl

Makefile:906: recipe for target 'dconf-service.1' failed
make[2]: *** [dconf-service.1] Error 4
make[2]: Leaving directory '/sources/dconf-0.24.0/docs'
Makefile:380: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/sources/dconf-0.24.0'
Makefile:319: recipe for target 'all' failed
make: *** [all] Error 2

I have D-BUS, Glib, libxslt, and Vala compiled and am compiling 
neither the editor nor gtk-doc.








Hello,

You need docbook-xml and docbook-xsl in order for it to load the 
entities for the XML files that DConf uses.


The book has libxslt and libxml2 as dependencies already. I can make 
libxml2 required for both the editor and the base package itself at 
my next commit.


Thank you,


I also had those compiled which is the first two lines throw me.


Check and see if you have these ran:

for DTDVERSION in 4.1.2 4.2 4.3 4.4
do
  xmlcatalog --noout --add "public" \
"-//OASIS//DTD DocBook XML V$DTDVERSION//EN" \
"http://www.oasis-open.org/docbook/xml/$DTDVERSION/docbookx.dtd; \
/etc/xml/docbook
  xmlcatalog --noout --add "rewriteSystem" \
"http://www.oasis-open.org/docbook/xml/$DTDVERSION; \
"file:///usr/share/xml/docbook/xml-dtd-4.5" \
/etc/xml/docbook
  xmlcatalog --noout --add "rewriteURI" \
"http://www.oasis-open.org/docbook/xml/$DTDVERSION; \
"file:///usr/share/xml/docbook/xml-dtd-4.5" \
/etc/xml/docbook
  xmlcatalog --noout --add "delegateSystem" \
"http://www.oasis-open.org/docbook/xml/$DTDVERSION/; \
"file:///etc/xml/docbook" \
/etc/xml/catalog
  xmlcatalog --noout --add "delegateURI" \
"http://www.oasis-open.org/docbook/xml/$DTDVERSION/; \
"file:///etc/xml/docbook" \
/etc/xml/catalog
done

That is in the Configuration Information section of the docbook-xml page.

Also check and see if you have a /etc/xml/catalog file. If you don't, 
recreate the /etc/xml/catalog file using the instructions in the 
docbook-xml and docbook-xsl pages.


Success!  I recompiled docbook-xml with special attention to your 
reference and then successfully compiled dconf.  With dconf compiled I 
can start Midori without errors and save configuration files.


Should DConf be listed as a requirement for Midori?  I use Fluxbox so I 
hadn't gnome when I compiled Midori.  And while the documentation does 
provide a working Midori, it's rather important to save configuration files.


Perhaps I simply missed it as there are numerous dependencies.





--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Midori startup errors.

[rhubarbpieguy]

On 07/22/2016 05:38 PM, Douglas R. Reno wrote:

Bruce Dubbs wrote:

rhubarbpie...@gmail.com wrote:


I've recently compiled Midori and receive the following upon 
starting with

"midori":

GLib-GIO-Message: Using the 'memory GSettings backend. Your 
settings

will not be saved or shared with other applications.

(midori4:15329): Gtk-CRITICAL **: gtk_action_set_action_group:
assertion 'action_group == NULL' failed

I've compiled:

shared-mime-info
desktop-file-utils
gsettings-desktop-schemas

Other than the startup errors Midori seems to be performing well. Is 
DConf

necessary?


I think these messages show up from libraries if you are not running 
Gnome.  Douglas?


  -- Bruce

I'd try building DConf and try launching it again. That looks like it 
can't get to the backend to actually store the settings, therefore it 
runs it in memory instead of saving it.


I tried compiling DConf before posting and received the following during 
the make command:


   I/O error : Attempt to load network 
entityhttp://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
   warning: failed to load external 
entity"http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl;
   cannot 
parsehttp://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
   Makefile:906: recipe for target 'dconf-service.1' failed
   make[2]: *** [dconf-service.1] Error 4
   make[2]: Leaving directory '/sources/dconf-0.24.0/docs'
   Makefile:380: recipe for target 'all-recursive' failed
   make[1]: *** [all-recursive] Error 1
   make[1]: Leaving directory '/sources/dconf-0.24.0'
   Makefile:319: recipe for target 'all' failed
   make: *** [all] Error 2

I have D-BUS, Glib, libxslt, and Vala compiled and am compiling neither the 
editor nor gtk-doc.




-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Midori startup errors.

[rhubarbpieguy]

I've recently compiled Midori and receive the following upon starting 
with "midori":


   GLib-GIO-Message: Using the 'memory GSettings backend.  Your 
settings will not be saved or shared with other applications.


   (midori4:15329): Gtk-CRITICAL **: gtk_action_set_action_group: 
assertion 'action_group == NULL' failed


I've compiled:

   shared-mime-info
   desktop-file-utils
   gsettings-desktop-schemas

Other than the startup errors Midori seems to be performing well. Is 
DConf necessary?

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Adwaita errors.

[rhubarbpieguy]

Adwaita lists no dependencies in the documentation.  But if I compile Adwaita 
prior to compiling librsvg I receive the following:

   Can't load file: Unrecognized image file format
   Makefile:441: recipe for target 'install-data-local' failed
   make[3]: *** [install-data-local] Error 1
   make[3]: Leaving directory '/sources/adwaita-icon-theme-3.18.0/src/symbolic'
   Makefile:317: recipe for target 'install-am' failed
   make[2]: *** [install-am] Error 2
   make[2]: Leaving directory '/sources/adwaita-icon-theme-3.18.0/src/symbolic'
   Makefile:330: recipe for target 'install-recursive' failed
   make[1]: *** [install-recursive] Error 1
   make[1]: Leaving directory '/sources/adwaita-icon-theme-3.18.0/src'
   Makefile:539: recipe for target 'install-recursive' failed
   make: *** [install-recursive] Error 1

The errors may be inconsequential as the programs requiring Adwaita load 
without error.  However, compiling Adwaita after librsvg produces no errors.  
Does that make sense?  Should librsvg be mentioned as a requirement for Adwaita?

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Missing libgiognomeproxy.so after glib-networking installation.

[rhubarbpieguy]

I'm missing libgiognomeproxy.so after compiling glib-networking. The 
documentation indicates libgiognomeproxy.so and libgiognutls.so should 
be installed libraries.  I do have the following:


   /usr/lib/gio/modules/libgiognutls.la
   /usr/lib/gio/modules/libgiognutls.so

I see no errors in the log file.  What have I done wrong?  I see 
libproxy listed as an optional package which I did not compile.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] android on qemu/KVM?

[rhubarbpieguy]

Is anyone running android using qemu/KVM?  I receive a never-ending 
android splash screen with:


   qemu -enable-kvm -hda vdisk.img  \
-cdrom android-x86-4.4-r5.iso   \
-boot d  \
-m 384

I have less success with the alternate installation method as it never 
displays a splash screen but immediately returns to the installation menu:


I can boot and run android installed on another partition so assume the 
problem isn't box related.  However, I can successfully run Mint as a VM 
using the alternate installation method so perhaps the problem is simply 
android.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] "make PREFIX=/usr i \" - pciutils-3.4.1 BLFS 7.9 (downloadable documentation only)

[rhubarbpieguy]

On 03/20/2016 03:22 PM, Bruce Dubbs wrote:

. . wrote:

On 3/13/16, Bruce Dubbs  wrote:

rhubarbpie...@gmail.com wrote:

The downloadable pciutils-3.4.1 BLFS documentation
http://linuxfromscratch.org/blfs/downloads/stable/blfs-book-7.9-html.tar.bz2 

seems to differ from the online versions.  The second make block 
displays

an unnecessary "i."

 make PREFIX=/usr  i \

The online BLFS and development versions have no "i."  If the
documentation isn't changed after a release, should there be a BLFS 
Errata

in the download section?


I fixed the typo in the on-line versions but not the compressed 
versions.



I wonder if this fell through the cracks as the downloadable version
still contains the error.


Which downloadable version?

BLFS-BOOK-7.9-nochunks.html
BLFS-BOOK-7.9-nochunks.html.bz2
blfs-book-7.9-html.tar.bz2

I said I didn't fix the compressed versions, but I regenerated the 
nochunks version just for you.  The compressed tarball still has the 
extra character.


  -- Bruce

blfs-book-7.9-html.tar.bz2  I'm at a loss as I'm just trying to report 
incorrect documentation here.  And am I the only one who thinks BLFS 
Errata belongs also on the Download page?  Jjust making a suggestion ...

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] "make PREFIX=/usr i \" - pciutils-3.4.1 BLFS 7.9 (downloadable documentation only)

[rhubarbpieguy]

The downloadable pciutils-3.4.1 BLFS documentation 
http://linuxfromscratch.org/blfs/downloads/stable/blfs-book-7.9-html.tar.bz2 
seems to differ from the online versions.  The second make block 
displays an unnecessary "i."


   make PREFIX=/usr  i \

The online BLFS and development versions have no "i."  If the 
documentation isn't changed after a release, should there be a BLFS 
Errata in the download section?

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Qt 5 "-demosdir: invalid command-line switch" - BLFS 7.8/Development

[rhubarbpieguy]

Qt-5 documentation for the /usr option includes "-demosdir 
/usr/share/doc/qt5/demos" in the configuration.


However, running .configure produces "-demosdir: invalid command-line 
switch" and ".configure --help" shows no -demosdir option.


Should the line be removed?
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] GConf-3.2.6 - No package 'libxml-2.0' found. BLFS 7.8

[rhubarbpieguy]

On 12/22/2015 06:23 PM, Ken Moffat wrote:

On Tue, Dec 22, 2015 at 05:12:20PM -0600, rhubarbpie...@gmail.com wrote:

On 12/22/2015 02:59 PM, Ken Moffat wrote:

On Tue, Dec 22, 2015 at 01:36:49PM -0600, rhubarbpie...@gmail.com wrote:

I receive "No package 'libxml-2.0' found" when compiling GConf-3.2.6.  I
assume the problem lies with libxml2-2.9.2 but see neither errors during
compiling nor libxml-2.0 in the documentation.  Is libxml-development
necessary?

No, -development packages are provided by distros which do not
always install full packages, and typically contain headers.  We do
not split packages like that.

It looks like libxml2 is referenced in DEPENDENT_WITH_XML by GConf,
and that is a pkgconfig call for "DEPENDENT" (glib, gio, etc, etc)
and libxml-2.0.  Is libxml-2.0.pc not installed, or installed in an
unusual place (i.e. not /usr/lib/pkgconfig and not
/usr/share/pkgconfig) ?

ĸen

I have no libxml-2.0.pc.  I have glib-2.0.pc, gio-2.0.pc, gthread-2.0.pc,
gmodule-2.0.pc, and gobject-2.0.pc, all in /usr/lib/pkgconfig.

Your post implies, at least to me, that you have installed
libxml-2.  If that is the case, you should have the pc file.  If you
have logs, check the libxml-2 build for any odd errors and, if you
have reasonably-reliable¹ logs for what got installed, check if the
pc file did get installed (but has been lost since then), or if it
did not get installed.

Whatever, libxml-2 is needed and is supposed to install the pc file,
so I think you will need to reinstall it.

1. I say "reasonably reliable" because I've had a lot of issues with
my own logging over the years, e.g. files ignored because they were
installed as-shipped and therefore were older than the compile.

ĸen


Yes, I'd installed libxml2.  I'd checked the log before posting and 
found no errors.  However, I just reinstalled and checked for 
libxml-2.0.pc, running "find /usr -name libxml-2.0.pc" immediately after 
rebuilding.  Bupkis.


However, the log states "config status: creating libxml-2.0.pc." But the 
following line states "config status: creating 
libxml-2.0-uninstalled.pc" which I don't understand.  That's the sole 
occurence of uninstalled I see.


I'm apparently doing something wrong but am not seeing it.  I'm 
attaching my log.


checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... //bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether ln -s works... yes
checking how to run the C preprocessor... gcc -E
checking for mv... //bin/mv
checking for tar... //bin/tar
checking for perl... /usr/bin/perl
checking for wget... /usr/bin/wget
checking for xmllint... /usr/bin/xmllint
checking for xsltproc... /usr/bin/xsltproc
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking how to print strings... printf
checking for a sed that does not truncate output... //bin/sed
checking for grep that handles long lines and -e... //bin/grep
checking for egrep... //bin/grep -E
checking for fgrep... //bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to 
x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain 
format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a 

Re: [blfs-support] GConf-3.2.6 - No package 'libxml-2.0' found. BLFS 7.8

[rhubarbpieguy]

On 12/22/2015 02:59 PM, Ken Moffat wrote:

On Tue, Dec 22, 2015 at 01:36:49PM -0600, rhubarbpie...@gmail.com wrote:

I receive "No package 'libxml-2.0' found" when compiling GConf-3.2.6.  I
assume the problem lies with libxml2-2.9.2 but see neither errors during
compiling nor libxml-2.0 in the documentation.  Is libxml-development
necessary?

No, -development packages are provided by distros which do not
always install full packages, and typically contain headers.  We do
not split packages like that.

It looks like libxml2 is referenced in DEPENDENT_WITH_XML by GConf,
and that is a pkgconfig call for "DEPENDENT" (glib, gio, etc, etc)
and libxml-2.0.  Is libxml-2.0.pc not installed, or installed in an
unusual place (i.e. not /usr/lib/pkgconfig and not
/usr/share/pkgconfig) ?

ĸen
I have no libxml-2.0.pc.  I have glib-2.0.pc, gio-2.0.pc, 
gthread-2.0.pc, gmodule-2.0.pc, and gobject-2.0.pc, all in 
/usr/lib/pkgconfig.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-support] Python-2.7.10 requirement for Qt-5.5.0? BLFS 7.8

[rhubarbpieguy]

Should Python-2.7.10 be listed as a requirement for Qt-5.5.0? Compiling 
Qt-5.5.0 without Python-2.7.10 produces:


   Makefile:2492: recipe for target '.generated/RegExpJitTables.h' failed
   Makefile:49: recipe for target 'sub-qml-make_first-ordered' failed
   Makefile:45: recipe for target 'sub-src-make_first' failed
   Makefile:223: recipe for target 'module-qtdeclarative-make_first' failed

Compiling Python-2.7.10 eliminates the errors and Qt-5.5.0 compiles 
successfully.


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Python-2.7.10 requirement for Qt-5.5.0? BLFS 7.8

[rhubarbpieguy]

On 12/14/2015 02:27 PM, Pierre Labastie wrote:

On 14/12/2015 21:11, rhubarbpie...@gmail.com wrote:

Should Python-2.7.10 be listed as a requirement for Qt-5.5.0? Compiling
Qt-5.5.0 without Python-2.7.10 produces:

Makefile:2492: recipe for target '.generated/RegExpJitTables.h' failed
Makefile:49: recipe for target 'sub-qml-make_first-ordered' failed
Makefile:45: recipe for target 'sub-src-make_first' failed
Makefile:223: recipe for target 'module-qtdeclarative-make_first' failed

Compiling Python-2.7.10 eliminates the errors and Qt-5.5.0 compiles 
successfully.



Qt-5.5.0 requires libxcb, which requires xcb-proto, which requires python2 or
python3. Do you mean you have only python3, and that it is not enough?

Pierre


Yes, I compiled only Python 3.  Until BLFS 7.8 I compiled Python 2 and 
Python 3 and had no problem with QT.  With 7.8 I compiled only Python 3 
and encountered the problem.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page